I found the bug!

I deleted the log because it had sensitive private stuff in it. But
here's the two important lines:

wocky-DEBUG: 04/02/2012 11:31:13.986948: _end_element_ns: Received stanza
* iq xmlns='jabber:client' 
from='+19202151...@voice.google.com/srvres-MTAuMjI5LjU4Ljk2Ojk4OTQ=' 
to='roothor...@gmail.com/9aedac01' id='jingle:10.229.58.96-4524775:1:6155422E' 
type='set'
    * session xmlns='http://www.google.com/session' type='initiate' 
id='SIP2144872714@10.220.203.77' 
initiator='+19202151...@voice.google.com/srvres-MTAuMjI5LjU4Ljk2Ojk4OTQ='
        * description xmlns='http://www.google.com/session/phone'
            * payload-type id='0' name='PCMU' clockrate='8000'
            * payload-type id='101' name='telephone-event'
        * transport xmlns='http://www.google.com/transport/raw-udp' 
behind-symmetric-nat='false' can-receive-from-symmetric-nat='false'
        * transport xmlns='http://www.google.com/transport/p2p'
<...>
gabble/media-channel-DEBUG: 04/02/2012 11:31:13.988025: jingle_cb 
(jingle-factory.c:780): NAKing with error: unsupported content transport

(Yes, I am aware that my email and google voice temporary number are in
that stanza. That much is public information already.)

Note that the stanza received from Google has TWO transport tags, one
for a raw-udp transport not supported by Empathy, and one for the
standard p2p transport that IS supported. I don't know what standard is
at play here, but it seems to imply to me that the client has a choice.
Therein lies the problem:

In telepathy-gabble, starting at jingle-content.c:499, function
gabble_jingle_content_parse_add assumes that there is only one transport
tag present. It parses only the first tag, sees that the transport is
unsupported, and errors immediately.

I'm working on a patch right now; waiting for things to install so I can
apply it to my system.

** Visibility changed to: Public

** Changed in: empathy (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/971272

Title:
  empathy doesn't receive audio calls over Google Talk

Status in “empathy” package in Ubuntu:
  New

Bug description:
  Try to initiate a call via the Google Voice website, selecting Google
  Talk for the phone. Double-checked there's no other IM clients or
  GMail instances open on my account. Hit Connect, the site goes
  "Calling you..." and no response from empathy whatsoever. Pidgin, at
  least, recognizes the incoming call and gives a popup.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: empathy 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 00:18:54 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20111129.1)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/971272/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to