Configure your Trunk using Twilio Interconnect

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

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:

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

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