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
Successfully merging a pull request may close this issue.
According https://bugs.chromium.org/p/webrtc/issues/detail?id=9484 new versions of Chrome are sending new offer format and answer cannot be generated.
For example, for RemoteDescription with info m=application 54111 UDP/DTLS/SCTP webrtc-datachannel a=sctp-port:5000 pc.CreateAnswer does not produce any result - no error, no answer
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel a=sctp-port:5000
Similiar issue for node implementation - node-webrtc/node-webrtc#483
The text was updated successfully, but these errors were encountered:
Do you know, is this just a matter of using a newer version of Chromium to base libwebrtc off of?
Sorry, something went wrong.
This occurs when one client uses go-webrtc library and another client uses browser (or mobile app) with newer version of Chromium.
Yeah, looks like node-webrtc fixed this by bumping to branch-heads/70
branch-heads/70
According https://bugs.chromium.org/p/webrtc/issues/detail?id=9484 new versions of Chrome are sending new offer format and answer cannot be generated.
For example, for RemoteDescription with info
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel a=sctp-port:5000pc.CreateAnswer does not produce any result - no error, no answer
Similiar issue for node implementation - node-webrtc/node-webrtc#483
The text was updated successfully, but these errors were encountered: