The SIP Server could act as a hosted Session Border Controller (SBC) by letting an internal service connect with SIP devices located on the public internet. Two modes are supported:
The hosted SBC functionality allows changing the transport protocols for SIP signaling and media. It would let a device, that connects using SIP/Websocket for signaling and RTP/DTLS for media, to connect with an internal system even though the internal system uses SIP/TCP and RTP/UDP.
The following transport protocols could be mixed and matched:
Since media is supposed to flow end-to-end between SIP devices, the SIP Server will not be part of the media flow at all in some cases. When media anchoring is required (e.g. to apply Hosted NAT traversal) the media streams are relayed without any intervention and media remains encrypted end-to-end.
SIP devices must support SRTP (RFC 3711) together with an appropriate key negotiation method to support end-to-end RTP encryption (SDES RFC 4568 or DTLS-SRTP RFC 5764).
Codecs supported:
Modern CPaaS built cloud-native from ground up – we run the operations for you so you can focus on your customers’ experience.
Built for mission critical alarm, voice & video services – delivering superior reliability, security and availability.
Built with serverless functions in AWS for unlimited scale, reach and global deployment – extend to new markets quick and easy.