jigar-joshi / libjingle

Automatically exported from code.google.com/p/libjingle
0 stars 0 forks source link

Vtok incompatibility #177

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I've developed a XMPP compatible client using libjingle and I'm having problems 
when receiving calls from vtok...I think I discovered the problem: their 
session-initate stanza is like this (only the relevant part):

<iq to="TEXT REMOVED" type="set" id="55" from="TEXT REMOVED/VtokiPh3D7C3BF86">
     <jingle action="session-initiate" id="75878218" initiator="TEXT REMOVED/VtokiPh3D7C3BF86" xmlns="urn:xmpp:jingle:1">
       <content name="audio" creator="initiator">
         <description media="audio" xmlns="urn:xmpp:jingle:apps:rtp:1">
           <payload-type id="0" name="PCMU" clockrate="8000">
             <parameter name="bitrate" value="64000"/>
           </payload-type>
         </description>
         <transport xmlns="http://www.google.com/transport/p2p"/>
       </content>

As you can see, inside the jingle element there is an id attribute but in 
accordance with the JINGLE definition 
(http://xmpp.org/extensions/xep-0166.html#def) it should have a sid attribute. 
I think an id is for GINGLE protocol but in this case the correct element is 
session, not jingle. Am I wrong? BTW, why are there GINGLE and JINGLE?

The weird think is that Gmail plugin can handle this call but my app doesn't 
(neither call example).
I appreciate any help. Thanks in advance.

Original issue reported on code.google.com by diego.cd...@gmail.com on 16 Jun 2011 at 7:55

GoogleCodeExporter commented 9 years ago
I found this in r61:

// TODO: This works around a bug in old jingle clients
// that set QN_ID instead of QN_SID.  Once we know there are no
// clients which have this bug, we can remove this code.
if (msg->sid.empty()) {
    msg->sid = jingle->Attr(buzz::QN_ID);
}

So I believe I'm rigth and vtok is one of those jingle clients with this bug. I 
have already sent an email to them

Original comment by diego.cd...@gmail.com on 16 Jun 2011 at 8:35

GoogleCodeExporter commented 9 years ago
Besides the "sid" issue, we've updated the server side which now requires the 
following 4 audio codecs have to be in the "session-initiate" message:

           <payload-type id="0" name="PCMU" clockrate="8000"/>
           <payload-type id="9" name="G722" clockrate="16000"/>
           <payload-type id="13" name="CN" clockrate="8000"/>
           <payload-type id="105" name="CN" clockrate="16000"/>

Original comment by jun...@google.com on 29 Jun 2011 at 12:45