|SDP audio RED cannot be parsed|
|Project Member Reported by email@example.com, Sep 30 2014||Back to list|
What steps will reproduce the problem? 1. Running chrome with logging enabled: chrome --enable-logging --v=1 --vmodule=*libjingle/source/talk/*=3 2. Visit http://googlechrome.github.io/webrtc/samples/web/content/munge-sdp/ then Get media -> Create peer connection -> Create offer 3. Add the following lines to the SDP and click on Set Offer a=rtpmap:127 red/8000 a=fmtp:127 103/103 What is the expected result? One should be able to go on with create answer and go on to make a call. What do you see instead? Cannot make call. Can find [44:44:0930/155638:VERBOSE1:webrtcsdp.cc(359)] Failed to parse: "". Reason: Failed to parse audio codecs correctly. in the log. According to https://tools.ietf.org/html/draft-ietf-mmusic-sdp-media-capabilities-17 such SDP should be valid. webrtcvoicengine.cc is also ready to accept parameter="" to set RED codecs. But it seems that libjingle SDP parser does not accept it. What version of the product are you using? On what operating system? Tested with Chrome 37, tot, can be other versions.
Oct 14 2014,
Oct 28 2014,
minyue@, let us know if this is blocking you on something. Otherwise we're treating this as P3.
Oct 28 2014,
Oct 29 2014,
This has been like so for a while. I don't know if anyone else reported it too. This is related to another issue: https://code.google.com/p/webrtc/issues/detail?id=3619 I cannot use our tool http://googlechrome.github.io/webrtc/samples/web/content/munge-sdp/ to debug it due to this SDP parsing error.
Nov 4 2015,
This bug hasn't been modified for more than a year, but it still repros for me with 48.0.2553.1. Note that the munge SDP test page has since moved to https://webrtc.github.io/samples/src/content/peerconnection/munge-sdp/.
|► Sign in to add a comment|