[Telepathy] [Bug 15656] Inconsistent in when it calls a contact capable of audio/video

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=15656





--- Comment #1 from Robert McQueen <robert.mcqueen at collabora.co.uk>  2008-05-06 04:22:54 PST ---
The one in RequestStreams is correct. In real Jingle land, we need to know that
the client has support for Jingle itself, the appropriate content description
(audio or vidio), and a usable transport. Gabble only supports signalling the
GTalk-P2P transport, because its Jingle implementation isn't that far removed
from its original GTalk implementation.

In GTalk land, having the Google voice capability is sufficient, because GTalk
didn't used to have any concept of separate session, content and transport
signalling. You either have Google voice capability (implying Google Session,
and GTalk-P2P), or you don't.

In future if we'd added support for signalling Jingle ICE and Jingle Raw UDP,
then having one them would also make people callable, rather than requiring
them to have GTalk-P2P (in practice, I expect only us would ever use GTalk-P2P
as a transport with XEP-0166 Jingle). Although at this point, we should examine
our own channel-specific capabilities, and only consider people with raw UDP
callable if we have raw UDP available ourselves, for example.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.