Technical features

Explore the technical features of our Mediaservice API. Click each feature to read more.
Acting as a SIP UA capable of receiving and initiating SIP calls. Acting as a SIP B2BUA to connect participants in a call. The Call Control is performed using REST API call-backs for each state of the call.

Media Control

Acting as a multi-tenant RFC 3261 SIP Registrar and accepts customer SIP device registrations. SIP user accounts and registration state are maintained in a location service.

SIP/WebRTC Agnostic

Incoming or outgoing call legs may be any combination of SIP devices, WebRTC clients or calls using a SIP trunk.

REST API Call-backs

The call handling logic is controlled and managed by a number of REST call-backs and APIs.

Signaling Security

SIP signaling is encrypted using TLSv1.2 or later. SIP devices are recommended to support RFC 5626 and are responsible for keeping the TLS session established to allow inbound SIP signaling for NAT traversal.

Media Security

SIP devices must support SRTP (RFC 3711) together with appropriate key negotiation method to support end-to-end RTP encryption (SDES RFC 4568 or DTLS-SRTP RFC 5764).

Audio Codecs Supported

Our customers experience reduced cost, improved time to market and increased quality

Get Started

Talk to us today or visit our Developer Area to learn more about our Mediaservice API.

Talk to us today

Get in contact if you want to start building with our granular & feature rich communication APIs.

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.

Magnus Ladulåsgatan 13, 118 65 Stockholm, Sweden