Use Case -
RTP Transcoding
Use Case -
RTP Transcoding

VoIP Media transcoding expensive! Cloudonix transcodes industry standard codecs on-the-fly, at a fraction of the cost of traditional solutions.

RTP Transcoding

RTP (Audio/Video) Transcoding is a costly task. Your VoIP network’s capacity and performance losses approximately 20% of its capacity (or more) – when transcoding is required. Off loading your transcoding requirements to Cloudonix, ensures that your network’s performance is always optimal.

Engineering First

Use our command line tool to rapidly control your network, without needing to access any web UI or computer program. The ability to respond rapidly to a changing infrastructure is an advantage – CLI tools make sure you are to do so.

On-The-Fly Transcoding and Relaying

Our network of globally located media processors (RTP servers) enable us to bounce media packets dynamically across the globe, while at the same time transcode. Dynamically allocating a shortest path for a call’s RTP stream, based on analyzing the RTP stream in real-time.

Any Codec, Any Transport

Connect with any industry standard codec (g711u, g711a, g729, g723, gsmfr), web Codecs (opus, speex) and any transport method (udp, tcp, tls). You can easily process calls on any transport using any codec – and connect between them.

Start for FREE

Get up to 250 calls per month – FREE. There are no setup fees, no per-minute fees or other hidden fees. Enjoy our #slack channel for community support as you integrate Web-2-Call services.

Integration Workflow

Integrating Cloudonix Web Calling is a fairly simple process. We recommend using our command line tool to ease the operation. To do so, please follow the following steps:

Step 1: Install cloudonix-cli tool

$ npm install -g @cloudonix.io/cloudonix-cli

Additional information about the Cloudonix CLI tool can be found here.

Step 2: Setup your Cloudonix Credentials

$ cloudonix-cli config set --apikey=your_api_key --domain=your_cloudonix_default_domain

This step will configure your cloudonix-cli tool with your provided Cloudonix platform credentials.

Step 3: Setup SIP trunks to and from your network

$ cloudonix-cli trunks wizard

This step will allow you to configure outbound and inbound trunks to your existing network. Depending on the case, you can create the following:

  1. Inbound DID numbers to your network
    Setup an inbound trunk from your DID provider and an outbound trunk to your existing network
  2. Outbound termination to a remote network
    Setup an outbound trunk to your termination provider and an inbound trunk from your existing network

You can create more complex routing logic using our programmable APIs and build full LCR implementations as well.

Step 4: Allow your domain to setup Border-2-Border calls

$ cloudonix-cli domains config --set --pair=allowed-border --value=true

All external SIP trunk should be connected to the border.cloudonix.io border gateway. By default, Cloudonix will not allow calls to flow between border handled calls. By setting the allowed-border profile setting to true – your domain will allow calls to be routed between border connected SIP trunks.

Join our community #slack channel

Schedule your demo today!

Media optimization and transcoding is both complex and expensive. As your network grows and multiple vendors platforms connect, new codecs are introduced. Cloudonix can reduce your transcoding infrastructure, by off-loading your transcoding resources to the Cloudonix global network.

Use the calendar box to schedule your meeting with a telecom expert – and learn more about how Cloudonix can massively expand your network and reduce your costs.