-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
datachannel doesn't have rtcp-mux attribute #13
Comments
Thanks, I think you're right, sdp-interop needs to relax the rtcp-mux requirement on the application m-line. Could you please try to do the following and see if it works any better?
|
I saw the README. I've tested with your change and now sdp-introp can convert the first offer with the data channel to planB. The server sends back an answer with datachannel, I'm converting to unified plan and calling setLocalDescription.
SDP: |
Any plans to add the datachannel rtcp-mux fix? |
Hi, I'm sorry for the late response. I somehow missed your previous reply. I have created a branch that attempts to fix this issue here https://github.com/jitsi/sdp-interop/tree/issue-13. Could you please try it and let me know how it goes? |
Any chance that PR will get merged? |
I am pleased to confirm that the issue-13 branch resolves the problem with datachannels. |
I am trying to create a p2p communication over chrome and firefox. I got an error exception while us
options: {offerToReceiveVideo: 1, offerToReceiveAudio: 1, voiceActivityDetection: true, iceRestart: false} and got offer like this:
Error: Cannot convert to Unified Plan because m-lines without the rtcp-mux attribute were found.
|
When creating a pc with only a datachannel, Firefox 38 doesn't set the rcp-mux attribute and toPlanB fails with an error:
Is it a problem with FF or does the interop need to relax the rtcp-mux requirement on the application m-section?
The text was updated successfully, but these errors were encountered: