Closed jmillan closed 8 years ago
Changing the remote DTMF payload value on re-negotiation makes Chrome fail on RTCPeerConnection.setLocalDescription()
Ie;
The remote peer negotiates a DTMF payload value of 126: a=rtpmap:126 telephone-event/8000
The remote peer later re-ngegotiates a DTMF payload value of 101: a=rtpmap:101 telephone-event/8000
This is a reported issue in Chrome: https://code.google.com/p/webrtc/issues/detail?id=2350
In order to avoid this Chrome failure, it's necessary and enough to remove the new DTMF payload from the 'm=audio' line.
Let me close this one. This should not be handled by rtcninja.js but by the code using it.
Changing the remote DTMF payload value on re-negotiation makes Chrome fail on RTCPeerConnection.setLocalDescription()
Ie;
The remote peer negotiates a DTMF payload value of 126: a=rtpmap:126 telephone-event/8000
The remote peer later re-ngegotiates a DTMF payload value of 101: a=rtpmap:101 telephone-event/8000
This is a reported issue in Chrome: https://code.google.com/p/webrtc/issues/detail?id=2350