---
title: "How to Connect Your SBC"
canonical: "https://help.callroute.com/space/CKB/698908724/How%20to%20Connect%20Your%20SBC"
format: markdown
---
The following guide will explain how to connect your SBC to Callroute.

### Networking Requirements

Your SBC must be connected to the internet with a public static IPv4 address. Where your SBC is connected via a NAT firewall, the public IP address must be used in SDP and SIP Signalling. Not the private IP address.

Please ensure that your firewall has been configured to allow the following IPs inbound to your SBC  


| **IP Source** | **Port** | **Protocol** | **Destination** | **Type** |
| --- | --- | --- | --- | --- |
| 45.146.156.0/24 | 5060 | UDP | SBC | SIP Signalling |
| 45.146.156.0/24 | 5061 | TLS | SBC | SIP Signalling |
| 45.146.157.0/24 | 5060 | UDP | SBC | SIP Signalling |
| 45.146.157.0/24 | 5061 | TLS | SBC | SIP Signalling |
| 45.146.156.0/24 | 16384:32767 | UDP | SBC | Media |
| 45.146.157.0/24 | 16384:32767 | UDP | SBC | Media |
| 54.233.188.84/32 | 16384:32767 | UDP | SBC | Media |
| 44.212.156.59/32 | 16384:32767 | UDP | SBC | Media |

Please ensure that if you have outbound port restrictions, you must allow traffic from your SBC source address and ports for SIP and Media to our addresses above.

### Secure SIP / Encrypted Media

Callroute supports TLS based SIP and SRTP using public signed certificates. The use of self-signed or internal certificate authority issued certificates **is not supported**. 

We accept TLS SIP traffic on port 5061 only. We support only TLS 1.2 protocol. Any connections using TLS 1.0 or 1.1 **will be denied.**

When using TLS, ensure that your SBC has a publicly routable FQDN e.g. [sbc1.mydomain.com](http://sbc1.mydomain.com) and that the certificate common name matches the FQDN of the SBC. Wildcard certificates are also supported.

> ⚠️ Please ensure that you have created a DNS A record for your SBC FQDN in your public DNS zone.

When encrypting media, ensure that the following cipher suite is offered

| **Crypto Suite** |
| --- |
| AES_CM_128_HMAC_SHA1_80 |

### DTMF

Callroute supports DTMF RFC-2833 only. We do not support SIP INFO or in-band DTMF transmission. Our default payload is set to 101.

### T.38 FAX

We do not support the T.38 protocol or fax over VoIP.

### SIP OPTIONS

We do support SIP OPTIONS if enabled. SIP OPTIONS allow the trunk between your SBC and Callroute to be constantly tested for active status. Our default ping interval is 30 seconds.

### Audio Codecs

Callroute supports the following audio codecs

| **Codec** |
| --- |
| G.711a |
| G.711u |

### Number Format / Dial Patterns

Please note that Callroute requires the calling number and called number to be presented in E.164 format **with a leading + (plus)**. 

`Example: +441234567890`

It is expected all transformations are to be handled by your SBC to accomodate this.

## Creating a BYOC Connection

Login to Callroute and click on **Carriers > Connect a SBC**

![Screenshot 2026-01-26 at 12.05.37.png](media://5a7e8185-06ad-40c3-b443-03ed217a4ff6)

Enter your SBC public connection details and then click “Add SBC”

![Screenshot 2026-01-26 at 12.09.04.png](media://cae0340c-7822-4d2b-87b5-51259a3d251a)

Once you have entered the settings, the trunk will build on Callroute and display under the section **My SBCs**

![image](media://fd27354a-df0d-4108-a3a1-e1d9d3a1ffdf)

Click on **Configure** to retrieve the settings you’ll need to establish a connection to Callroute. Click on **View Configuration**

![image](media://9c20deb9-b4b5-490d-b283-03ad2656fccd)

Please make a note of the **Server Address** as this will be the FQDN generated for your SBC SIP Trunk

![Screenshot 2024-06-15 at 09.48.27.png](media://313b0669-bb80-4739-ae60-98828f93155a)

Once you have these settings, you can configure your SBC to create the connection.

> ⚠️ IMPORTANT: Please remember we are a global service. Traffic needs to be sent to us in **E164** format. You cannot configure (manipulate) numbers within Callroute.
> ⚠️ 
> ⚠️  **[+] [country code] [subscriber number including area code]**
> ⚠️ 
> ⚠️ For example, for the UK, this would be **+44 20 7123 4567**