New: Inconsistent in when it calls a contact capable of audio/ video

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

           Summary: Inconsistent in when it calls a contact
capable of
                    audio/video
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-gabble
        AssignedTo: telepathylists.freedesktop.org
        ReportedBy: sjoerdluon.net


The capabilities implementation of gabble indicates that a
contact is capable
of video if it just has
PRESENCE_CAP_JINGLE_DESCRIPTION_VIDEO and capable of
audio if it has PRESENCE_CAP_GOOGLE_VOICE or
PRESENCE_CAP_JINGLE_DESCRIPTION_AUDIO

But when making a call using RequestStreams, a contact is
only considered as
being capable of audio if it has:
  PRESENCE_CAP_JINGLE
  | PRESENCE_CAP_JINGLE_DESCRIPTION_AUDIO 
  | PRESENCE_CAP_GOOGLE_TRANSPORT_P2P;
or PRESENCE_CAP_GOOGLE_VOICE and a similar situation exists
for video. So why
is 
PRESENCE_CAP_GOOGLE_TRANSPORT_P2P suddenly needed and why
is
PRESENCE_CAP_JINGLE suddenly needed?


-- 
Configure bugmail: h
ttp://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Telepathy mailing list
Telepathylists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy

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





--- Comment #1 from Robert McQueen <robert.mcqueencollabora.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: h
ttp://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Telepathy mailing list
Telepathylists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy

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


Simon McVittie <simon.mcvittiecollabora.co.uk>
changed:

           What    |Removed                     |Added
------------------------------------------------------------
----------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Simon McVittie <simon.mcvittiecollabora.co.uk>  2008-05-16 03:39:30 PST ---
Fixed in 0.7.6.


-- 
Configure bugmail: h
ttp://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Telepathy mailing list
Telepathylists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy