Twilio Interconnect allows you to connect your SIP infrastructure using a private connection (e.g. MPLS, cross-connect) to a Twilio Elastic SIP Trunk.
To connect over Twilio Interconnect, point your communications infrastructure to the following localized Termination SIP URIs:
|Termination SIP URI||Interconnect Exchange|
||Ashburn, Virginia, United States|
||San Jose, California, United States|
||London, United Kingdom|
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:
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.
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).
126.96.36.199 188.8.131.52 184.108.40.206 Ports: 5060 (UDP/TCP), 5061 (TLS)Media IPs:
220.127.116.11/26 Port Range: 10,000 to 20,000 (UDP)
18.104.22.168 22.214.171.124 126.96.36.199 Ports: 5060 (UDP/TCP), 5061 (TLS)Media IPs:
188.8.131.52/26 Port Range: 10,000 to 20,000 (UDP)
184.108.40.206 220.127.116.11 18.104.22.168 Ports: 5060 (UDP/TCP), 5061 (TLS)Media IPs:
22.214.171.124/26 Port Range: 10,000 to 20,000 (UDP)
126.96.36.199 188.8.131.52 184.108.40.206 Ports: 5060 (UDP/TCP), 5061 (TLS)Media IPs:
220.127.116.11/26 Port Range: 10,000 to 20,000 (UDP)