Understanding how Pidgin handles XMPP jingle

Anurodh Pokharel monaltest at gmail.com
Thu Jun 21 11:59:30 EDT 2012

 I am trying to add Jingle audio support to Monal, my iOS XMPP client
(Monal.im). I am trying to understand how pidgin (and I assume libpurple
in general) identify  a client as being XMPP capable.

 When I send the following presence stanza to pidgin:

<presence from="xxx2 at gmail.com/MonalE97B8DDF" to="xxx at gmail.com">
<priority>24</priority> <c node="http://monal.im" ver="" ext="avatar
voice-v1" xmlns="http://jabber.org/protocol/caps"/>  <x

I see the following in the debug log:

jingle-rtp: Buddy doesn't support the same transport types

This is similar to the stanza that google talk sends:

<presence from="XXX2 at gmail.com/gmail.08D8A9D9"
to="XXX at gmail.com"><status/><priority>24</priority><caps:c
node="http://mail.google.com/xmpp/client/caps" ver="1.1" ext="pmuc-v1
sms-v1 video-v1 voice-v1" xmlns:caps="http://jabber.org/protocol/caps"/><x

Which is identified as an audio capable client (the audio menu shows up in
the contact list)

When i send the Monal stanza above to Gtalk, it does identify  Monal as
being capable of audio calls.  What is pidgin doing differently here?

This is what I send for disco#info earlier

<iq  type='result'  to='xxxxx' id='xxxxx' ><query
xmlns='http://jabber.org/protocol/disco#info'> <feature
var='http://jabber.org/protocol/disco#items'/> <feature
var='http://jabber.org/protocol/disco#info'/> <identity
category='client' type='phone' name='monal'/><feature
var='http://jabber.org/protocol/si/profile/file-transfer'/> <feature
var='http://jabber.org/protocol/si'/> <feature
var='jabber:iq:version'/> <feature
var='http://jabber.org/protocol/muc#user'/> <feature
var='urn:xmpp:jingle:1'/> <feature
var='urn:xmpp:jingle:apps:rtp:1'/> <feature
var='urn:xmpp:jingle:apps:rtp:audio'/> </query></iq>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/support/attachments/20120621/1837a790/attachment-0002.html>

More information about the Support mailing list