WebRTC Gateway connects between WebRTC and an established VoIP technology such as SIP. WebRTC (Web Real-Time Communication) is an API definition drafted by the World Wide Web Consortium (W3C) that supports browser-to-browser applications for voice calling, video chat, and messaging without the need of either internal or external plugins.
To enable browsers using different application providers to communicate with each other (e.g. a user logged into application providers X wants to call someone that is logged into application provider Y) a so-called WebRTC trapezoid can be used. In this case the two providers use a widely used VoIP signalling protocol such as SIP to federate between them. However, each of their respective browser-based clients signals to its server using proprietary application protocols built on top of HTTP and WebSocket.
This component that mediates between WebRTC and SIP is referred to as a WebRTC Gateway. Beside connecting different WebRTC applications, a WebRTC gateway also enables the communication between a WebRTC phone and a VoIP or even a PSTN phone. Thereby, a WebRTC gateway extends the scope of WebRTC applications and enables much wider reach and usage scenarios.
- Signalling: There is no standardised signalling protocol for WebRTC applications. However, SIP over WebSockets (RFC 7118) is often used partially due to the applicability of SIP to most of the envisaged communication scenarios as well as the availability of open source software such as JsSIP. In such a case, the gateway would only need to repackage the SIP packets from the WebSocket layer into UDP, TCP or TLS.
- Media transport: The WebRTC specifications indicate that for security reasons WebRTC applications must use SRTP for transporting media content. While some VoIP applications support SRTP as well, this is optional and hence not always the case. If the callee does not support SRTP then the WebRTC gateway will have to map between SRTP and RTP.
- Media content: The WebRTC specifications indicate that WebRTC applications must use for audio communication either G.711 or OPUS as the Audio codec. Applications using SIP for establishing audio session are free to choose any type of codec. If the callee does not support OPUS or G.711 then the WebRTC gateway will have to transcode between the WebRTC and SIP sides of the communication.
- Media address negotiation: In order to be able to traverse all kinds of NAT, the WebRTC specifications indicate that WebRTC applications must use STUN and ICE in order to detect the addresses under which two end points can exchange media packets. While these technologies are also implemented by some SIP user agents, this is not mandatory. If the callee does not support ICE or in case media transport layer needs mapping or media transcoding is required then the WebRTC gateway will have to act as an ICE end point and route the media packets between the caller and callee.
There are already a number of open source and commercial solutions available for providing the WebRTC gateway functionality. As a lot of required functionality of a WebRTC gateway such as media handling, signalling mapping is supported by SBC the function of WebRTC gateway is often integrated into SBCs or provided by SBC vendors.
Open-source WebRTC gateways
- reSIProcate and repro
- AudioCodes WebRTC enabled SBC, WebRTC GW
- Cisco Meeting Server (previously Acano)
- Video RTC Gateway (WebRTC)
- FRAFOS ABC WebRTC Gateway
- Frozen Mountain - LiveSwitch
- IVèS Audio Video and Text WebRTC to SIP GW
- Pexip Infinity Platform
- PortSIP WebRTC Gateway
- REVE WebRTC-SIP Gateway
- Ribbon's Kandy Link Gateway (previously GENBAND & Sonus)
- TeleFinity WebRTC-SIP Gateway
- WIT Software
- "WebRTC 1.0: Real-time Communication Between Browsers". Dev.w3.org. Retrieved 2012-09-12.
- "WebRTC:How and Why?" (PDF). FRAFOS. 2015-01-12.
- "Video RTC".
- "Massively Flexible Video, Voice, & Messaging | Frozen Mountain Software".
- "WebRTC-SIP Gateway | Simplify WebRTC Implementation".