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.

  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:
    • 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 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 Port Range: 10,000 to 60,000 (UDP)
San Jose, California, USA
16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Ashburn, Virginia, USA
16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Frankfurt, Germany
16384-32768 (UDP)10000 - 30000 (UDP/TCP)
São Paulo, Brazil
16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Sydney, Australia
16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Singapore 16384-32768 (UDP)10000 - 30000 (UDP/TCP)
Mumbai, India 16384-32768 (UDP)


Signaling IPs:

North America
South America
Southeast Asia

RTP ports used: 10000–20000

North America Virginia Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

North America Oregon Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe Ireland Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe Frankfurt Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Tokyo Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Singapore Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Sydney Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)

South America Sao Paulo Gateways:
Signaling IPs:
Ports: 5060 (UDP/TCP), 5061 (TLS)
Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.