There’s a lot of talk about SIP v WebRTC – maybe too much talk. It’s questionable to what extent I can add to the debate. But for those of you who haven’t read thoroughly around the subject I thought it might be useful to dance some quick fandangos over the various arguments. Then I can leave you to come to your own conclusions.
Here’s the deal. SIP is all about signalling and session control and emerged from the world of Telco and the so-called SS7 stack. That’s a terrible definition but it’ll do.
WebRTC has emerged from the webby world and has been less concerned about signalling and more about making audio and video work for real-time communications via standard web browsers.
The reason why the debate has become so intense is that several people are jumping on the WebRTC bandwagon. And the technology is evolving from an OTT direction – rather than from a telco direction. The big switch and telco vendors want a slice of the action. But, by the same token, the WebRTC new kids on the block want to be seen to control their own destinies.
You could do a lot worse than visit Tsahi Levent-Levi’s ‘BlogGeek’ site to hear the arguments from the WebRTC perspective. His view is that WebRTC will ultimately paddle its own canoe and that signalling protocols will be made on the fly to create the new wave of native solutions built around WebRTC.
The reason, according to Lawrence Byrd, is that ‘lightness’ is the keyword in webRTC signalling and the telco world doesn’t yet fully appreciate this.
But the debate will, no doubt, continue to rage.