Skip to main content

BYOC – Bring Your Own Carrier

Already have a voice partner and would like to integrate your own SIP trunk? No problem we got you covered!

Written by Christoffer

Adversus supports integrating your own SIP trunk into our web application. This means that all voice traffic will be terminated to a SIP trunk of you preference with any voice partner.

To be able to set up your SIP trunk we need the following information from you:

Trunk details

  • Hostname / IP

  • Authentication method (Basic or IP)

Termination

There's a variety of options we can support for outbound termination and these options should be provided from your SIP trunk provider.

Number format

There are multiple formats used for telephone numbers within SIP communication. For us to be able to deliver calls successfully to your trunk you need to tell us what format your SIP trunk supports.

E.164

The most used format and we support both with and without the optional plus (+) sign.

  • 4586300086@sip.your-trunk.com

  • +4586300086@sip.your-trunk.com

Breakout

Also widely used and probably the format most used when dialing internationally on your mobile phone!

  • 004586300086@sip.your-trunk.com

Limitations

To make sure our application is not doing anything not supported by your SIP trunk we also need the following information from your SIP trunk provider:

Tech prefix

With SIP trunks, providers often have different tech prefixes to prepend to a SIP URI. If your trunk has a tech prefix we need to know to place calls successfully.

CPS Limit

If your trunk has any limitations on the number of Calls Per Second ("CPS") we can add these limitations in our systems so that e.g. our Predictive Dialer will not place more calls than what's allowed by the trunk.

Origination

If an inbound call is placed to a number in your trunk the calls should be sent to our origination endpoint with the format outlined below:

+e164@dk-sip1.adversus-server.dk+458600086@dk-sip1.adversus-server.dk

The above format is the only format supported.

Did this answer your question?