Routing to a SIP Client

Rebecca

May 24, 2022 18:22

Overview

Routing your tracking numbers to a SIP Client enables your advanced voice applications to initiate SIP sessions from CTM to your existing SIP communications infrastructure, such as an IP-PBX, SBC, or IP phones.

Create a Receiving SIP Client in CTM

In your CTM account, you must create a SIP Client receiving number.

Navigate to Numbers → Receiving Numbers.
Click New Receiving Number.
Click to enable the Dial SIP Client toggle.
Enter your SIP Client in the field provided (example: your-sip-client@example.com).
- If your SIP Client requires authentication, set a user and password in the SIP User and SIP Password fields provided.
- Note: SIP Headers can be utilized to pass data such as caller_number to your SIP endpoint utilizing tokenized values for x-headers, as seen in the following example:
  +15555555555@127.0.0.01?X-Id={{id}}&X-ANI={{caller_number}}&X-Zip={{postal_code}}?
After saving the receiving number record, the SIP Refer toggle becomes available. Toggling this option to ON will allow the SIP endpoint for this receiving number record to send calls back into a CTM queue by utilizing the following parameters from your SIP endpoint:
- <sip:{route_id}@ctm.app>
  (Where route_id represents the identifier of the destination queue)
Click Save & Continue.

Technical Specifications

Media codec: CTM uses G.711/μ-law CODEC for media. This is the most popular CODEC used by the carriers, so transcoding is unnecessary.

DTMF: CTM implements RFC-2833 for sending and receiving DTMF.

Securing SIP Traffic using TLS
Encryption ensures that the call media and associated signaling remain private during transmission. Transport Layer Security (TLS) provides encryption for SIP signaling. When receiving SIP from CTM, only a single crypto suite will be advertised: AES_CM_128_HMAC_SHA1_80

IP Address Whitelist

Prepare your communications infrastructure to make sure that your SIP infrastructure has connectivity to CTM and vice versa. To ensure that your communications infrastructure doesn’t block communication, you must update your whitelist. We strongly encourage you to whitelist all the following IP address ranges and ports on your firewall for SIP signaling and RTP media traffic.

This is important if you have numbers in different regions as well as for availability purposes (for example, if North America Virginia gateways are down, then North America Oregon gateways will be used).

New IP Allow list effective October 10, 2023:

Media IPs:

Regions	IP Addresses	Ports
Global	168.86.128.0/18	Port Range: 10,000 to 60,000 (UDP)
San Jose, California, USA	52.9.254.64/26 216.120.187.64/26 13.52.9.0/25 216.120.187.128/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Ashburn, Virginia, USA	3.93.158.128/25 52.205.63.192/26 204.89.148.64/26 18.214.109.128/25 18.215.142.0/26 204.89.148.128/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Frankfurt, Germany	52.58.255.224/27 52.59.63.224/27 3.120.121.128/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
São Paulo, Brazil	54.233.255.192/27 54.233.191.0/27 18.228.70.64/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Sydney, Australia	52.65.191.160/27 52.65.127.160/27 13.238.202.192/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Singapore	52.220.63.128/26 18.136.1.128/26	16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Mumbai, India	15.207.90.0/24	16384-32768 (UDP)
US/CAN:	64.16.224.0/19
EU:	185.246.41.128/25
AUS:	103.115.244.128/25

Signaling IPs:

Europe	18.184.175.4/32 18.196.245.254/32 185.246.41.140 185.246.41.141
North America	34.194.41.43/32 34.197.97.9/32 192.76.120.10 64.16.250.10 192.76.120.31 64.16.250.13
South America	52.67.242.103/32 54.233.100.129/32
Southeast Asia	52.74.7.178/32 54.251.177.8/32
Australia	13.210.20.49/32 13.210.220.180/32 103.115.244.145 103.115.244.146

RTP ports used: 10000–20000

North America Virginia Gateways:
Signaling IPs:

54.172.60.0
54.172.60.1
54.172.60.2
54.172.60.3
Ports: 5060 (UDP/TCP), 5061 (TLS)

North America, Oregon Gateways:
Signaling IPs:

54.244.51.0
54.244.51.1
54.244.51.2
54.244.51.3
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe Ireland Gateways:
Signaling IPs:

54.171.127.192
54.171.127.193
54.171.127.194
54.171.127.195
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe Frankfurt Gateways:
Signaling IPs:

35.156.191.128
35.156.191.129
35.156.191.130
35.156.191.131
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Tokyo Gateways:
Signaling IPs:

54.65.63.192
54.65.63.193
54.65.63.194
54.65.63.195
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Singapore Gateways:
Signaling IPs:

54.169.127.128
54.169.127.129
54.169.127.130
54.169.127.131
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Sydney Gateways:
Signaling IPs:

54.252.254.64
54.252.254.65
54.252.254.66
54.252.254.67
Ports: 5060 (UDP/TCP), 5061 (TLS)

South America Sao Paulo Gateways:
Signaling IPs:

177.71.206.192
177.71.206.193
177.71.206.194
177.71.206.195
Ports: 5060 (UDP/TCP), 5061 (TLS)