Created attachment 24084 [details]
Gabble -> google talk log

Created attachment 24085 [details]
Google talk -> Gabble log

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

*** Bug 21338 has been marked as a duplicate of this bug. ***

I just called a friend who was using the gtalk desktop client with Gabble 0.7.27 and that worked fine. 

Don't know if that matters but he installed gtalk 2 days ago so that's probably the last release.

** (telepathy-gabble:10963): DEBUG: gabble_media_stream_error: Media.StreamHandler::Error called, error 0 (Codec negotiation failed: The codec ISAC must have a non-0 clock rate) -- emitting signal

Olivier, any thoughts:

That was fixed in fs2 .0.8.... last february, upgrade.

.