WebRTC 2.0 Overview

WebRTC 2.0 key features:

1. Using completely new infrastructure a new signaling server with new web pages that optimized for different platforms, including the iOS and MacOS and ability to use authenticated logic with tokens.

2. The WebRTC core has been updated to the latest version.

3. We are compatible with an older version of WebRTC. The existing API still works, with just a few adjustments needed.

4. We also have added the new API that gives the new abilities:

- mix-minus;

- many-to-many connections in duplex mode;

- improved video and audio connection logic. TURN server is now required less frequently.

Update Signaling Server:

Replace the old signaling server with one that incorporates the new logic and web clients, moving away from the deprecated SimpleWebRTC tool.

You can use our public signaling server for testing purposes. 

HKEY_CURRENT_USER\SOFTWARE\Medialooks\WebRTC
https://videosdk.medialooks.com:8080

or use your own based on Medialooks Signaling Docker Image with the new TURN docker image

Enable WebRTC 2.0 to activate the new features with existing code

HKEY_CURRENT_USER\Software\Medialooks\WebRTC
webrtc20.enabled = true
signaling_server = https://videosdk.medialooks.com:8080

One minor change in the source code will be required for the web link, i.e., in WebRTC 2.0 mode, we are not able to use the same access link for the web receiver.

If you are using WebRTC API 1.0 and webrtc20.enabled = true, the access links should be get from WebRTC statistics

m_objWebRTC.PropsGet("stat::path", webconnectionString) // link for web receivers
m_objWebRTC.PropsGet("stat::my_upi", connectionString) // link for native app receivers

MFormats Streamer Sample API 1.0 WebRTC 2.0 mode

MPlatform Streamer Sample API 1.0 WebRTC 2.0 mode

With these changes, you can utilize WebRTC 2.0 while leveraging the old API, ensuring that your current application continues operating as expected.

• The legacy API will remain operational but will now utilize new WebRTC source code under the hood.

• For users interested in new features, such as one-to-many connections, the new MConnect object and a new API will be required.

The latest WebRTC 2.0 uses the most current WebRTC source code and needs to be tested with your existing solutions before production.