Menu

Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Configure your Trunk using Twilio Interconnect

Twilio Interconnect allows you to connect your SIP infrastructure using a private connection (e.g. MPLS, cross-connect) to a Twilio Elastic SIP Trunk.

Configure your Trunk using Twilio Interconnect

Termination settings for Twilo Interconnect

To connect over Twilio Interconnect, point your communications infrastructure to the following localized Termination SIP URIs:

Termination SIP URI Interconnect Exchange
{example}.pstn.us1-ix.twilio.com Ashburn, Virginia, United States
{example}.pstn.us2-ix.twilio.com San Jose, California, United States
{example}.pstn.ie1-ix.twilio.com London, United Kingdom
{example}.pstn.sg1-ix.twilio.com Singapore

Origination settings for Twilio Interconnect

Configure your origination SIP URI, which identifies the network element entry point into your communications infrastructure (e.g. IP-PBX, SBC). To ensure your calls go over your private connection include the tnx parameter in the URI with the value of the desired Twilio Interconnect connection, for example:

  • sip:172.56.42.132;tnx={TNX_SID}
  • sip:mysbc.com;tnx={TNX_SID}

You can use multiple origination URIs for failover where you can have a primary URI send traffic over Twilio Interconnect, and a secondary URI send traffic over the public internet in the case of failure.

IP whitelist using Twilio Interconnect

We strongly encourage you to Whitelist all of Twilio's following IP address ranges and ports on your firewall for SIP signalling and RTP media traffic. This is important if you have Numbers in different regions and for resilience purposes (e.g. if North America Virginia gateways are down, then North America Oregon gateways will be used).

North America Virginia Interconnect Gateways:

Signalling IPs:

    208.78.112.64
    208.78.112.65
    208.78.112.66
    Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
    208.78.112.64/26
    Port Range: 10,000 to 20,000 (UDP)

North America Oregon Interconnect Gateways:

Signalling IPs:

    67.213.136.64
    67.213.136.65
    67.213.136.66
    Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
    67.213.136.64/26
    Port Range: 10,000 to 20,000 (UDP)

Europe London Interconnect Gateways:

Signalling IPs:

    185.187.132.68
    185.187.132.69
    185.187.132.70
    Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
    185.187.132.64/26
    Port Range: 10,000 to 20,000 (UDP)

Asia Pacific Singapore Interconnect Gateways:

Signalling IPs:

    103.75.151.68
    103.75.151.69
    103.75.151.70
    Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
    103.75.151.64/26
    Port Range: 10,000 to 20,000 (UDP)

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.