[Bug 44897] Gabble sometimes claim that Android contacts does not support A/V

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=44897

--- Comment #2 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2012-01-18 05:33:47 PST ---
Full Gabble log is on http://people.collabora.com/~cassidy/gabble-44897.log

In my Wocky caps cache:


sqlite> select * from capabilities where node =
'http://www.android.com/gtalk/client/caps#voice-v1';
http://www.android.com/gtalk/client/caps#voice-v1|<?xml version="1.0"
encoding="UTF-8"?>
<query xmlns="http://jabber.org/protocol/disco#info"><identity
category="account" type="registered" name="Google Talk User Account"/><feature
var="http://jabber.org/protocol/disco#info"/><feature
var="http://jabber.org/protocol/disco#items"/></query>
|1326892667


Looks like we're facing the Google server bug described in
client_types_from_message():

     /* So, turns out if you disco a specific resource of a gtalk
      contact, the Google servers will reply with the identity node as
      if you disco'd the bare jid, so will get something like:

          <identity category='account' type='registered' name='Google Talk User
Account'/>

      which is just great. So, let's special case android phones as
      their resources will start with "android" and let's just say
      they're phones. */


Shouldn't we special case A/V caps as well?

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