[Jingle] Call forking

Olivier Crête olivier.crete at collabora.co.uk
Thu Oct 15 10:44:40 CDT 2009


Hi,

On Thu, 2009-10-15 at 18:38 +0300, Diana Cionoiu wrote:
> Hello Olivier,
> 
> But you don't need support in protocol for that.
> You can do it anyway.

If user A calls user B who has resources B1 and B2 and B1 picks up, it
has to close the stream to B2 which an appropriate error message so that
B2 knows that it is not a missed call. That error message is what's
missing.

Olivier

> Regards,
> Diana
> 
> Olivier Crête wrote:
> > Hello,
> >
> > Yes this is exactly what we had in mind!
> >
> > Olivier
> >
> > On Thu, 2009-10-15 at 12:34 +0300, Diana Cionoiu wrote:
> >   
> >> Hello,
> >>
> >> I have a proposal on how to implement call forking in the jabber way 
> >> instead of the SIP way.
> >>
> >> A jingle client wants to call B jingle client
> >>
> >> A jingle server probes the B jingle user to find B's resources where B 
> >> can setup his voice priorities.
> >>
> >> A jingle client calls all the B jingle client resources
> >>
> >> I don't have an exact protocol proposal, but that's the basic concept.
> >>
> >> This doesn't work in SIP because SIP doesn't have the concept of 
> >> resource, but in Jabber resource exists, so we should use it wisely.
> >>
> >> Regards,
> >> Diana
> >>     
> 
-- 
Olivier Crête
olivier.crete at collabora.co.uk
Collabora Ltd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://mail.jabber.org/pipermail/jingle/attachments/20091015/d5ef82dd/attachment.pgp>


More information about the Jingle mailing list