Skip to contentSkip to navigationSkip to topbar
Rate this Page:

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

configure-your-trunk-using-twilio-interconnect page anchor

Termination settings for Twilio Interconnect

terminationuri-tnx page anchor

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

Termination SIP URIInterconnect Exchange
{example}.pstn.ashburn-ix.twilio.comAshburn, Virginia, United States
{example}.pstn.san-jose-ix.twilio.comSan Jose, California, United States
{example}.pstn.london-ix.twilio.comLondon, United Kingdom
{example}.pstn.frankfurt-ix.twilio.comFrankfurt, Germany
{example}.pstn.singapore-ix.twilio.comSingapore
{example}.pstn.tokyo-ix.twilio.comTokyo, Japan
{example}.pstn.sydney-ix.twilio.comSydney, Australia
(information)

Info

If you are looking for a list of legacy Interconnect localized URIs, visit here. eg: {example}.pstn.ie1-ix.twilio.com

Origination settings for Twilio Interconnect

originationuri-tnx page anchor

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 edge parameter in the URI with the value of the Twilio Interconnect Edge Location where your private connection is configured, for example:

  • sip:172.56.42.132;edge={EDGE_LOCATION}
  • sip:mysbc.com;edge={EDGE_LOCATION}

Note: without the {}, for example:

  • sip:172.56.42.132;edge=ashburn-ix
  • sip:mysbc.com;edge=ashburn-ix

You may also use the deprecated tnx parameter in the URI with the SID value of the desired Twilio Interconnect connection, however, it is preferred that you use the edge parameter as documented above. An example of using the tnx parameter:

  • 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.

Interconnect Connections - Global Media IP Range

The Interconnect Connections Destination IP Ranges and Port Ranges are now identical across all locations:

Secure Media (ICE/STUN/SRTP) Edge LocationsProtocolSource IPSource Port †Destination IP RangesDestination Port Range
sydney-ix (au1-ix)
sao-paulo-ix (br1-ix)
london-ix (ie1-ix)
frankfurt-ix (de1-ix)
tokyo-ix (jp1-ix)
singapore-ix (sg1-ix)
ashburn-ix (us1-ix)
san-jose-ix (us2-ix)
roaming (gll-ix)
UDPANYANY168.86.128.0/1810,000 - 60,000

† The SDK will select any available port from the ephemeral range. On most machines, this means the port range 1,024 to 65,535.

Signalling IP Addresses using Twilio Interconnect

ip-addresses-tnx page anchor

We strongly encourage you to allow all of Twilio's following IP address ranges and ports on your firewall for SIP signalling 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

north-america-virginia-interconnect-gateways page anchor

_10
208.78.112.64
_10
208.78.112.65
_10
208.78.112.66
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

North America San Jose Interconnect Gateways

north-america-san-jose-interconnect-gateways page anchor

_10
67.213.136.64
_10
67.213.136.65
_10
67.213.136.66
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe London Interconnect Gateways

europe-london-interconnect-gateways page anchor

_10
185.187.132.68
_10
185.187.132.69
_10
185.187.132.70
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

Europe Frankfurt Interconnect Gateways

europe-frankfurt-interconnect-gateways page anchor

_10
185.194.136.64
_10
185.194.136.65
_10
185.194.136.66
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Singapore Interconnect Gateways

asia-pacific-singapore-interconnect-gateways page anchor

_10
103.75.151.68
_10
103.75.151.69
_10
103.75.151.70
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Tokyo Interconnect Gateways

asia-pacific-tokyo-interconnect-gateways page anchor

_10
103.144.142.68
_10
103.144.142.69
_10
103.144.142.70
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)

Asia Pacific Sydney Interconnect Gateways

asia-pacific-sydney-interconnect-gateways page anchor

_10
103.146.214.68
_10
103.146.214.69
_10
103.146.214.70
_10
Ports: 5060 (UDP/TCP), 5061 (TLS)


Rate this Page: