3 ms·
It would have required much forethought to predict, in 2002, that realtime communications would be happening in the browser. Thus WebRTC was born. But a tragedy
by psim1 4y ago
It would have required much forethought to predict, in 2002, that realtime communications would be happening in the browser. Thus WebRTC was born. But a tragedy of WebRTC is that it is not by-default compatible with SIP. WebRTC authors could have specified SIP as the signaling protocol over websocket, but they left the spec open ended. I feel two ways about this: glad for choice, but disappointed that the choice most often made does not allow for interop with the "legacy" realtime communications protocol, SIP.
- kkielhofner 4y agoThere are libraries to do SIP signaling over WS/WSS with WebRTC from a browser (or whatever) that theoretically allow for interop with other SIP devices. In practice the fundamentals of WebRTC rely on things like ICE, STUN, and TURN for media so they're not going to be compatible with almost all existing SIP implementations - many of which can't even do interop with bog-standard vanilla SIP over UDP with standard codecs properly. As is often the case with SIP you're back to using some Session Border Controller or equivalent architectural component to make interop actually work reliably.