Our WebRTC solution started to face critical errors when our clients browsers updated to Chrome M97. It seems that M97 WebRTC changed the extmap values mapping in a way that it is not backward compatible. This affects part of our call scenarios which are slow start based (late offer).
The errors happen when one side is using M97 and the other side is using a lower chrome version or a Firefox browser.
Due to the mismatch of extmap values between the different chrome versions, when a re-invite occurs one of the sides is failing upon setting local/remote description (depends on which side initiate the offer)
An example of a change that breaks our solution is:
For reference, I’m attaching the following SDPs just before setting local/remote description on my client using M97, remote client is M96.
Once client is setting the re-invite answer remote description, the following error is received:
Failed to process answer: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Failed to set remote video description send parameters for m-section with mid='1'.
Note, if I remove the following extmap from the SDPs the scenario is successful
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/f210eab5-3a32-428f-9449-a52bb9fbd8d5n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/af7010b5-331f-45ae-93ac-77d37eb96300n%40googlegroups.com.