Routing to a SIP Client
Routing your tracking numbers to a SIP Client enables your advanced voice applications to initiate SIP sessions from CallTrackingMetrics towards your existing SIP communications infrastructure, such as IP-PBX, SBC, and IP-phones.
Create a Receiving SIP Client in CTM
In your CallTrackingMetrics 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: email@example.com).
- If your SIP Client requires authentication, set a user and password in the SIP User and SIP Password fields provided.
- Click Save & Continue.
Media codec: CallTrackingMetrics uses G.711/μ-law CODEC for media. This is the most popular CODEC used by the carriers so transcoding is unnecessary.
DTMF: CallTrackingMetrics implements RFC-2833 for sending and receiving DTMF.
Securing SIP Traffic using TLS
Encryption ensures that the call media and associated signaling remains private during transmission. Transport Layer Security (TLS) provides encryption for SIP signaling. When receiving SIP from CallTrackingMetrics, 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 CallTrackingMetrics 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 of 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).
North America Virginia Gateways:
126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 Ports: 5060 (UDP/TCP), 5061 (TLS)
18.104.22.168/23 22.214.171.124/23 Port Range: 10,000 to 20,000 (UDP)
North America Oregon Gateways:
126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 Ports: 5060 (UDP/TCP), 5061 (TLS)
18.104.22.168/24 Port Range: 10,000 to 20,000 (UDP)
Europe Ireland Gateways:
22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 Ports: 5060 (UDP/TCP), 5061 (TLS)
220.127.116.11/26 18.104.22.168/24 Port Range: 10,000 to 20,000 (UDP)
Europe Frankfurt Gateways:
22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 Ports: 5060 (UDP/TCP), 5061 (TLS)
220.127.116.11/25 Port Range: 10,000 to 20,000 (UDP)
Asia Pacific Tokyo Gateways:
18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 Ports: 5060 (UDP/TCP), 5061 (TLS)
184.108.40.206/26 Port Range: 10,000 to 20,000 (UDP)
Asia Pacific Singapore Gateways:
220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 Ports: 5060 (UDP/TCP), 5061 (TLS)
188.8.131.52/26 Port Range: 10,000 to 20,000 (UDP)
Asia Pacific Sydney Gateways:
184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 Ports: 5060 (UDP/TCP), 5061 (TLS)
126.96.36.199/26 Port Range: 10,000 to 20,000 (UDP)
South America Sao Paulo Gateways:
188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 Ports: 5060 (UDP/TCP), 5061 (TLS)
22.214.171.124/26 Port Range: 10,000 to 20,000 (UDP)