[Pidgin] #16509: Video call from jitsi over XMPP always fails

Pidgin trac at pidgin.im
Sun Jan 10 10:35:57 EST 2016

#16509: Video call from jitsi over XMPP always fails
 Reporter:  xuhdev   |       Owner:  deryni
     Type:  defect   |      Status:  new
Milestone:           |   Component:  XMPP
  Version:  2.10.11  |  Resolution:
 Keywords:           |

Comment (by mazhe):

 Hello, I've stumbled on this issue which I encountered recently. One of
 the roots of this problem is that when Pidgin send the initial jingle
 negociation stanza, it describe a few audio codecs having zero channels,
 like :

 <payload-type name='PCMU' id='0' clockrate='8000' channels='0'/>
 <payload-type name='PCMA' id='8' clockrate='8000' channels='0'/>

 If you try something crude and horrible like the following:

 --- libpurple/protocols/jabber/jingle/rtp.c.orig    2016-01-06
 18:07:20.250617000 +0100
 +++ libpurple/protocols/jabber/jingle/rtp.c 2016-01-06 18:12:02.832399000
 @@ -750,7 +750,7 @@
         xmlnode_set_attrib(payload, "name", name);
         xmlnode_set_attrib(payload, "id", id);
         xmlnode_set_attrib(payload, "clockrate", clockrate);
 -       xmlnode_set_attrib(payload, "channels", channels);
 +       if (channels != 0) xmlnode_set_attrib(payload, "channels",


 Audio will work. The real fix would be to understand where this
 information is coming from: maybe some NULL pointer or default value to
 describe "1 channel"? I did not go far enough to see whether it was from
 gstreamer or farstream/farsight...

 As for video, after that, I ran into more issues... But beware that you
 need some h264 codecs for gstreamer as jitsi only use this format for

Ticket URL: <https://developer.pidgin.im/ticket/16509#comment:2>
Pidgin <https://pidgin.im>

More information about the Tracker mailing list