Different WebRTC flavours from a server/platform point of view

WebRTC is a complex component with many optional features.  Because of that there are different ways to use it, specially when your solution includes a media server in the middle, and not everybody is using it the same way.

In some cases because of the use case requires some specific features, in others because of the background/history of the solution and in others maybe because of lack of development resources the fact is that today it is difficult to find two platforms/servers using WebRTC exactly with the same configuration/features.

In this post we are trying to present how some of the most popular platforms/servers are using it.  The goal is not to compare them or decide who is the best one (because as we said it depends on many factors) but to give an overview of the different options you have.

This table has been made with help from many contributors, mostly the main developers of some of those media servers / platforms and the idea is to keep it updated and extend it.  Feel free to reach out to me in Twitter or email address if you want to add/change something.

This is the link to the document if you want to read it better: Spreadsheet link .  You can find the explanation for the different features in the comments of the column headers.



You can follow me in Twitter if you are interested in Real Time Communications.

Comments

  1. UnknownJune 19, 2017 at 4:53 AM

    What then does it mean to be an educator? Does it signify something different than the assigned job title? What I have learned through my work in higher education is that becoming an educator is not an automatic process. Everyone who is teaching adult students is not functioning as an engaging and highly effective educator. However, it is possible to learn how to educate rather than teach and that requires making a commitment to the profession.http://www.writingdesk.pw/

    ReplyDelete
  2. Oliver MauriceJuly 17, 2017 at 4:29 AM

    Maybe you also would be interested in this article about essay writing

    ReplyDelete

Post a Comment

Popular posts from this blog

Bandwidth Estimation in WebRTC (and the new Sender Side BWE)

Image
Bandwidth estimation is probably the most critical component in the video engine of WebRTC. The bandwidth estimation (BWE) module is responsible for deciding how much video* traffic you can send without congesting the network to prevent degradation of the video quality. In the past bandwidth estimation algorithms used to be very rudimentary and based mostly on packet loss. Basically we used to start increasing slowly the video bitrate until we detected packets being lost.  To detect the packet loss you use the standard RTCP feedback mechanisms where the receiver side reports packet loss periodically using RTCP Receiver Report (RR) messages. Modern bandwidth estimation algorithms are more advanced and try to detect congestion before it is bad enough to make routers discard packets. These algorithms predicts congestion analyzing the delay between packets. The idea is that when you start having some congestion, the buffers in the routers will start filling and the delay wil...
Read more

Improving Real Time Communications with Machine Learning

Image
When we talk about the applications of Artificial Intelligence / Machine Learning (AI/ML) for Real Time Communications (RTC) we can group them in two different planes: Service Level : There are many features that can be added to a videoconference service, for example identification of the participants, augmented reality, emotion detection, speech transcription or audio translation .  These features are usually based on image and speech recognition and language processing. Infrastructure Level : There are many ways to apply ML that do not provide new features but improve the quality and/or reliability of the audio/video transmission. Service level applications are fun, but they are more for Product Managers and I like technology more, so in the next sections I will try to describe possible applications of AI/ML for Real Time Communications at Infrastructure Level organizing those ideas in five different categories. Optimizing video quality Some of the ML algorithms use...
Read more

Controlling bandwidth usage in WebRTC (and how googSuspendBelowMinBitrate works)

Image
There are cases when we would like to limit the maximum bitrate being transmitted by WebRTC to avoid wasting resources in the user endpoints or save money reducing the bandwidth usage in our servers.   This is because the maximum bitrate by default in Chrome is around 2Mbps and for many use cases a much lower bitrate provides still pretty good quality.   BTW using a lower bitrate can also help with stability of quality in multiparty scenarios by reducing the amount of competition among different streams. There is no simple API to configure the maximum bitrate in WebRTC (although there is one in ORTC) but there are 3 ways to do this by mangling the SDP. 1. U se the standard  b=AS:BITRATE (Chrome) or b=TIAS:BITRATE  (Firefox) attributes in the SDP for the audio or video channel[1] 2. Use codec specific attributes (this work at least for opus audio codec with maxaveragebitrate property) [2] 3. Use the proprietary x-max-bitrate attribute in the video channel of the...
Read more