sdp error: Failed to parse audio codecs correctly

[GoogleCodeExporter]

a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (Wireshark) or Javascript console log
if you want quick response

What steps will reproduce the problem?
1.Make a call from chrome to chrome
2.Error message shown at caller console: "Failed to parse SessionDescription. 
Failed to parse audio codecs correctly". when received 200 OK

What is the expected output? What do you see instead?
No audio/video is present
What version of the product are you using? On what operating system?

This is occurring after the sipml update to r217. 
Browser:Version 34.0.1847.116 m
Using Native APIs

Please provide any additional information below.

The issue id due to the fix of Issue 169. SIP INVITE is going with m attribute 
RTP/SAVPF along with crypto and fingerprint. But the 200OK has 
"UDP/TLS/RTP/SAVPF" with fingerprint(NO crypto)

Original issue reported on code.google.com by reshmasu...@gmail.com on 10 Apr 2014 at 10:43

[GoogleCodeExporter]

I see this issue with Canary only. Stable is working fine.
"UDP/TLS/RTP/SAVPF" is not expected to have crypto. The issue is in chrome 
itself as it expect "RTP/SAVPF" for DTLS (fingerprint is present).
There is a hack for Firefox but not for Chrome. To fix is it: at 
https://code.google.com/p/sipml5/source/browse/trunk/src/tinyMEDIA/src/tmedia_se
ssion_jsep.js?r=217#277 remove tmedia_session_jsep01.mozThis.
Anyways I'll commit the hack soon.

Original comment by boss...@yahoo.fr on 18 Apr 2014 at 7:52

• Changed state: Accepted

[GoogleCodeExporter]

Fixed by r220: https://code.google.com/p/sipml5/source/detail?r=220

Original comment by boss...@yahoo.fr on 18 Apr 2014 at 8:24

• Changed state: Fixed