Media Services Features

Explore the technical features of our mediaservice API.

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

PCMA, PCMU, G729, GSM and OPUS.
iotcomms.io – communication APIs tailored for developers

APIs tailored for developers​​

We package telecom complexity and protocol fragmentation in easy-to-use APIs for you to save time and cost, and offer superior performance.
iotcomms.io – communication APIs tailored for developers

APIs tailored for developers​​

We package telecom complexity and protocol fragmentation in easy-to-use APIs for you to save time and cost, and offer superior performance.

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 feature-rich communication APIs!