Bug 21338

Summary:	GTalk interop may be broken, and looks suspicious
Product:	Telepathy	Reporter:	Will Thompson <will>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Will Thompson 2009-04-22 06:14:19 UTC

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

Comment 1 Guillaume Desmottes 2009-04-23 02:19:11 UTC

I reported this problem in this bug (with logs):
http://bugs.freedesktop.org/show_bug.cgi?id=20767

Comment 2 Will Thompson 2009-04-23 03:20:27 UTC

So you did. I don't know why I didn't see that.

*** This bug has been marked as a duplicate of bug 20767 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.