[Pidgin] #15245: Can't Jingle-call to Gajim users. Pidgin blamed.

[Pidgin]

#15245: Can't Jingle-call to Gajim users. Pidgin blamed.
--------------------+-------------------------------------------------------
 Reporter:  mmlosh  |        Owner:  Maiku          
     Type:  defect  |       Status:  new            
Milestone:          |    Component:  Voice and Video
  Version:  2.10.5  |   Resolution:                 
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by dustin):

 Looking at your log files, Gajim sends a number of transport candidates,
 but their 'id' attribute is missing.
 From your `outgoing` log file:
 {{{
 <iq xmlns="jabber:client" to="friend at other.tld/resource"
 from="me at domain.tld/gajim n" id="44" type="set">
 <jingle xmlns="urn:xmpp:jingle:1" action="session-initiate"
 initiator="me at domain.tld/gajim n" sid="43">
 <content name="voice" creator="initiator">
 [..]
 <transport xmlns="urn:xmpp:jingle:transports:ice-udp:1"
 pwd="9hKjKL4puXiOHR8/ch3VYu" ufrag="frUX">
 <candidate foundation="1" protocol="udp" network="0" generation="0"
 ip="88.102.10.88" component="1" priority="1677721855" type="srflx"
 port="58789" />
 <candidate foundation="1" protocol="udp" network="0" generation="0"
 ip="88.102.10.88" component="2" priority="1677721854" type="srflx"
 port="38182" />
 <candidate foundation="1" protocol="udp" network="0" generation="0"
 ip="10.0.0.142" component="2" priority="2013266430" type="host"
 port="38182" />
 <candidate foundation="1" protocol="udp" network="0" generation="0"
 ip="10.0.0.142" component="1" priority="2013266431" type="host"
 port="58789" />
 [..]
 </transport>
 </content>
 </jingle>
 </iq>
 }}}


 Pidgin ignores these incomplete entries (IMHO), and therefore responds
 with an empty list of transport remote-candidates (which causes the
 confusion).

 {{{
 <iq id='purplefc7c3a6e' type='set' to='me at domain.tld/gajim n'
 from='friend at other.tld/resource'>
 <jingle action='session-accept' initiator='me at domain.tld/gajim n'
 responder='friend at other.tld/resource' xmlns='urn:xmpp:jingle:1' sid='43'>
 <content name='voice' senders='both' creator='initiator'>
 [..]
 <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'/>
 </content>
 </jingle>
 </iq>
 }}}


 According to [http://xmpp.org/extensions/xep-0176.html#schema XEP-0176],
 candidate ids are required, so I'd put the blame on Gajim. ;-)

 Some time ago, Pidgin <-> Jitsi connections didn't work for the same
 reason:
 [http://java.net/nonav/projects/jitsi/lists/dev/archive/2011-09/message/0]


 Regarding the number of entries inside a 'session-accept':
 AFAIK the responder has some liberties in what payload types may be sent
 back (at least that's the case for SIP), so there shouldn't be a problem
 here.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/15245#comment:2>
Pidgin <http://pidgin.im>
Pidgin