[Bug 21338] New: GTalk interop may be broken, and looks suspicious

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 22 15:14:20 CEST 2009


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

           Summary: GTalk interop may be broken, and looks suspicious
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk


Word on the street has it that we don't actually interop with GTalk for audio
calls any more. We should fix that.

Relatedly, from jingle/incoming-basics.py:

        # With gtalk4, apparently we have to send transport-accept immediately,
        # not even just before we send our transport-info.
        # FIXME: wjt thinks this is suspicious. It matches the Gabble
        #        implementation, so he moved it here to avoid the test being
        #        racy, but we should do some more interop testing.

And in outgoing-basics.py:

    if jp.dialect == 'gtalk-v0.4':
        node = jp.SetIq(jt2.peer, jt2.jid, [
            jp.Jingle(jt2.sid, jt2.peer, 'transport-accept', [
                jp.TransportGoogleP2P() ]) ])
        stream.send(jp.xml(node))

    # FIXME: expect transport-info, then if we're gtalk3, send
    # candidates, and check that gabble resends transport-info as
    # candidates


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



More information about the telepathy-bugs mailing list