[Bug 907739] Re: empathy cannot call to android phones

Wed Jan 18 16:41:38 UTC 2012

Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=44855.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2012-01-17T11:38:24+00:00 Guillaume-desmottes wrote:

Original bug: https://bugzilla.gnome.org/show_bug.cgi?id=667472

Looks like Google has its own echo bot: echo at bot.talk.google.com
Calling it from the gmail web interface works just fine but Telepathy claims it doesn't support audio/video.

Capabilities:
{49L: [({u'org.freedesktop.Telepathy.Channel.ChannelType': u'org.freedesktop.Telepathy.Channel.Type.Text',
         u'org.freedesktop.Telepathy.Channel.TargetHandleType': 1L},
        [u'org.freedesktop.Telepathy.Channel.TargetHandle'])]}

On the XMPP front:

<presence from="echo at bot.talk.google.com/bot"
to="guillaume.desmottes at gmail.com/cb11d944"><caps:c
node="http://talk.google.com/xmpp/bot/caps" ver="1.0" ext="voice-v1
video-v1 camera-v1"
xmlns:caps="http://jabber.org/protocol/caps"/></presence>

<iq type="error" to="guillaume.desmottes at gmail.com/cb11d944" id="282844807664" from="echo at bot.talk.google.com/bot"><query node="http://talk.google.com/xmpp/bot/caps#camera-v1" xmlns="http://jabber.org/protocol/disco#info"/><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>
wocky-DEBUG: _end_element_ns: Received stanza
* iq xmlns='jabber:client' type='error' to='guillaume.desmottes at gmail.com/cb11d944' id='282844807664' from='echo at bot.talk.google.com/bot'
    * query xmlns='http://jabber.org/protocol/disco#info' node='http://talk.google.com/xmpp/bot/caps#camera-v1'
    * error code='501' type='cancel'
        * feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'

* iq xmlns='jabber:client' type='error' to='guillaume.desmottes at gmail.com/cb11d944' id='283092808390' from='echo at bot.talk.google.com/bot'
    * query xmlns='http://jabber.org/protocol/disco#info' node='http://talk.google.com/xmpp/bot/caps#voice-v1'
    * error code='501' type='cancel'
        * feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'

I guess that's because the bot doesn't reply to our disco query so probably a GTalk bug. I still open this bug to double check with XMPP experts and so we have a better place to discuss it.

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/3

------------------------------------------------------------------------
On 2012-01-18T09:59:15+00:00 Simon McVittie wrote:

As far as I can see, that's a bug in the bot: it really ought to
implement disco#info.

If this bot works with GTalk, that probably means that GTalk is *still*
mis-implementing caps by looking at the names of bundles ("voice-v1",
etc.) and inferring what the capabilities are from the bundle name,
which is meant to be opaque
(http://talk.google.com/xmpp/bot/caps#voice-v1 is not necessarily the
same thing as http://example.com/#voice-v1, but I suspect GTalk would
treat it as if it was).

We could work around this by hard-coding the caps of the bot's URI in
the same place we hard-code the caps of known GTalk client versions.

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/4

------------------------------------------------------------------------
On 2012-01-18T11:15:10+00:00 Guillaume-desmottes wrote:

(In reply to comment #1)
> We could work around this by hard-coding the caps of the bot's URI in the same
> place we hard-code the caps of known GTalk client versions.

Which caps is that? Don't know if it's related but Gabble claims that
Android contacts connected using the official gtalk client don't support
A/V either.

<presence from="xxxxx at gmail.com/android_talke745182aa103"
to="guillaume.desmottes at gmail.com/cb11d944"><status/><priority>24</priority><caps:c
node="http://www.android.com/gtalk/client/caps" ext="pmuc-v1 voice-v1
video-v1 camera-v1" ver="1.1"
xmlns:caps="http://jabber.org/protocol/caps"/><show>away</show><x xmlns
="vcard-
temp:x:update"><photo>3fa9e0d462810bf05513c2b701fddacd97e919a1</photo></x></presence>

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/5

------------------------------------------------------------------------
On 2012-01-18T13:01:42+00:00 Guillaume-desmottes wrote:

(In reply to comment #2)
> (In reply to comment #1)
> > We could work around this by hard-coding the caps of the bot's URI in the same
> > place we hard-code the caps of known GTalk client versions.

I opened bug #44897 about this issue.

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/6

------------------------------------------------------------------------
On 2012-01-18T14:23:51+00:00 Guillaume-desmottes wrote:

Created attachment 55736
presence-cache: hardcode gtalk's bot caps

Thanks Google for not implementing disco query on the bot...

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/7

------------------------------------------------------------------------
On 2012-01-18T14:24:59+00:00 Guillaume-desmottes wrote:

With the above patch, the bot is callable but for some reason my
audio/video is not echoed back. This patch is the first step to debug
this so worth merging anyway.

Reply at: https://bugs.launchpad.net/telepathy-
gabble/+bug/907739/comments/8

** Changed in: telepathy-gabble
       Status: Unknown => Confirmed

** Bug watch added: GNOME Bug Tracker #667472
   https://bugzilla.gnome.org/show_bug.cgi?id=667472

-- 
You received this bug notification because you are a member of
Telepathy, which is subscribed to telepathy-gabble in Ubuntu.
https://bugs.launchpad.net/bugs/907739

Title:
  empathy cannot call to android phones

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/907739/+subscriptions