Hello, I'm using an extended SDP message which looks like this: v=0 [EMAIL PROTECTED] 1121941317127 1121941317127 IN IP4 140.93.25.47 s=- c=IN IP4 140.93.25.47 t=0 0 a=userqos:voip gold m=audio 53100 RTP/AVP 0 a=curr:qos e2e none a=des:qos optional e2e send a=des:qos mandatory e2e recv a=rtpmap:0 PCMU/8000 a=qos:info1 84 150 40 0.03 FT NC0 NC1 ------------------------- But when I receive it, it comes out as: v=0 [EMAIL PROTECTED] 1121941317127 1121941317127 IN IP4 140.93.25.47 s=- c=IN IP4 140.93.25.47 t=0 0 a=userqos:voip gold m=audio 53100 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=curr:qos e2e none a=des:qos optional e2e send a=des:qos mandatory e2e recv a=qos:info1 84 150 40 0.03 FT NC0 NC1 --------------------- As You see, the a=rtpmap:0 has 'wandered' up. The thing is, that all the a=curr and a=des lines describe the m= parameter, and a=qos:info describes just rtpmap, so that's how they need to be aligned in the structures. Is there any way to get the "raw" SDP, as it is in the packet? Otherwise - how to change the parsing so that it works OK? Greetings, Marcin
---------------------------------------------------------- Marcin Michalak Research Engineer Mobile: +41 79 330 83 51 Telscom AG ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
