Routing to a SIP Client


Last Updated: 06/12/2018 Back to Topic All Articles

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.

1) Navigate to Numbers → Receiving Numbers.

2) Click New Receiving Number.

3) Click to enable the Dial SIP Client toggle.

4) 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.

5) Click Save & Continue.


Technical Specifications

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 exampple, if North America Virginia gateways are down, then North America Oregon gateways will be used).

North America Virginia Gateways:
Signalling IPs:

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

Media IPs:

54.172.60.0/23
34.203.250.0/23
Port Range: 10,000 to 20,000 (UDP)

North America Oregon Gateways:
Signalling IPs:

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

Media IPs:

54.244.51.0/24
Port Range: 10,000 to 20,000 (UDP)

Europe Ireland Gateways:
Signalling IPs:

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

Media IPs:

54.171.127.192/26
52.215.127.0/24 
Port Range: 10,000 to 20,000 (UDP)

Europe Frankfurt Gateways:
Signalling IPs:

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

Media IPs:

35.156.191.128/25 
Port Range: 10,000 to 20,000 (UDP)

Asia Pacific Tokyo Gateways:
Signalling IPs:

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

Media IPs:

54.65.63.192/26
Port Range: 10,000 to 20,000 (UDP)

Asia Pacific Singapore Gateways:
Signalling IPs:

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

Media IPs:

54.169.127.128/26
Port Range: 10,000 to 20,000 (UDP)

Asia Pacific Sydney Gateways:
Signalling IPs:

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

Media IPs:

54.252.254.64/26
Port Range: 10,000 to 20,000 (UDP)

South America Sao Paulo Gateways:
Signalling IPs:

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

Media IPs:

177.71.206.192/26
Port Range: 10,000 to 20,000 (UDP)

Was this article helpful?
1 0