[Jingle] Call forking

Florian Zeitz florian.zeitz at gmx.de
Thu Oct 8 22:26:02 CDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Olivier Crête schrieb:
> On Fri, 2009-10-09 at 10:35 +1000, Evgeniy Khramtsov wrote:
>> Olivier Crête wrote:
>>> If a contact I'm trying to call has multiple online resources. I want to
>>> call it, currently Gabble, our XMPP implementation, just picks one more
>>> or less randomly and tries to call it.
>> Why not just call to a high priority resource?
> 
> Ok, I have a phone that does XMPP and a computer on my desk.. which one
> should you call ? Any random one ?
> 
He answered that already. The one with the higher priority.
Normal use would be to set the phone to the higher priority, because
you'll only be online with that when you're not on your desktop I guess.

If what you're saying is that you want chat messages to go to your
desktop PC and calls to your phone, because the user-experience is
better we might have to find another solution for that indeed (the easy
one would be to just not advertise support from your desktop computer).

>>> I think the right approach is to do something like SIP forking
>> SIP forking sucks. We do not need it in XMPP: we have resources and 
>> priorities.
> 
> Forking is required because I have multiple devices.
> 
That's just not true as such.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrOrUoACgkQ0JXcdjR+9YT5IwCgtaCrTb/9HmKBcGb4KUOxe5Pf
8f8AnjE+o1ivwDwGviYqnPj/titPQjYx
=Wkge
-----END PGP SIGNATURE-----


More information about the Jingle mailing list