The latest Chrome version (96) brings a change in the way WebRTC calls are handled. This can have impacts for applications built on the Rainbow Web SDK, running in Google Chrome and using conferences and WebRTC Gateway calls.
Applications running in other browsers or Chrome version older than 96 are not concerned by these impacts.
Our Rainbow Web SDK uses the underlying web engine to handle WebRTC.
The WebRTC framework relies on the Session Description Protocol (SDP) to negociate session capabilities between the peers.
Google Chrome was using the "Plan B" SDP format implementation that was not the standards conformant format.
Since version 96 Google Chrome switched to the standards conformant format called "Unified Plan".
Full support of this new format requires some changes in the way we use SDP in our SDK.
A fix for conferences will be delivered very soon in a patched Rainbow Web SDK LTS version. The availability date will be published in this forum and on the Rainbow API Hub Information channel (you can subscribe to the channel from hub.openrainbow.com).
Full support of new Unified Plan in Rainbow Web SDK will be delivered in a future LTS version.
In the meantime, you can implement the following workaround. It will allow your application to use PlanB SDP format until we release official support of Unified Plan SDP format in Rainbow Web SDK.
Use any Google account to add new registrations (https://developer.chrome.com/origintrials/#/trials/my).
Add as many "trials" as needed for this type : "RTCPeerConnection Plan B SDP Semantics", each one for a given domain.
This will generate a token that you must add in your HTML head part :
<meta http-equiv="origin-trial" content="<HERE COPY THE TOKEN PROVIDED BY GOOGLE>">
You can have as many meta as you want to support this everywhere you want.
Please sign in to leave a comment.