RTC@Scale 2024 – an event summary
RTC@Scale is Facebook’s virtual WebRTC event, covering current and future topics. Here’s the summary for RTC@Scale 2024 so you can pick and choose the relevant ones for you.
Read MoreWebRTC doesn't need SIP. SIP needs WebRTC.
I think it would be fair to say that WebRTC doesn't really need SIP. You can use SIP if you tweeWebRTC – just pick it up as a signaling protocol choice – one of many.
We can probably split a WebRTC deployment into 3 parts:
My own view?
-
There were no SIP signaling solutions in JavaScript a year ago, and why should there be? There was no point in doing that. But now there are a few.
SIP started adding WebSockets support only after the introduction of WebRTC.
But then, companies are using other solutions than SIP on the browser side – just check out some of my interviews. AddLive and TenHands went proprietary for signaling. Drum uses Jingle on the browser and then translates it to SIP for their backend.
And why is that? People use the tool that is best suitable for them: either because this is what they already know, or that what made sense.
interesting response; Justin on SIP's relevance to #WebRTC-SIP dev cycle has been in years whereas cadence of web is weeks,days, even hours
— trentjohnsen (@trentjohnsen) November 27, 2012
The tweet above makes a lot of sense to me: SIP and WebRTC have a different vibe to them. As more web developers adopt WebRTC (as opposed to VoIP developers who are the majority still), we will see less use of SIP as the signaling protocol and a lot more proprietary solutions for it.
RTC@Scale is Facebook’s virtual WebRTC event, covering current and future topics. Here’s the summary for RTC@Scale 2024 so you can pick and choose the relevant ones for you.
Read MoreNeed WebRTC recording in your application? Check out the various requirements and architectural decisions you’ll have to make when implementing it.
Read More