On 21 February 2024 Twilio will be updating the media IPs and port ranges for calls in all regions to 168.86.128.0/18 and expanding the UDP port range to 10000-60000. Old IP and port ranges will no longer accept or send traffic after this date.
Twilio Interconnect allows you to connect your SIP infrastructure using a private connection (e.g. VPN, cross-connect) to a Twilio SIP Interface.
To connect over Twilio Interconnect, point your communications infrastructure to the following localized SIP Domain URIs:
SIP Domain URI | Interconnect Exchange |
---|---|
{example}.sip.ashburn-ix.twilio.com | Ashburn, Virginia, United States |
{example}.sip.san-jose-ix.twilio.com | San Jose, California, United States |
{example}.sip.london-ix.twilio.com | London, United Kingdom |
{example}.sip.frankfurt-ix.twilio.com | Frankfurt, Germany |
{example}.sip.singapore-ix.twilio.com | Singapore |
{example}.sip.tokyo-ix.twilio.com | Tokyo, Japan |
{example}.sip.sydney-ix.twilio.com | Sydney, Australia |
{example}
will be replaced by the unique part of the SIP Domain that you previously configured. Refer to Programmable SIP Domains for SIP Domain setup. For example, if your SIP Domain was example.sip.twilio.com
, then it would be example.sip.london-ix.twilio.com
(for the London IX).
If you are looking for the legacy Interconnect SIP Domain URI list, visit here. eg: {example}.sip.de1.twilio.com
In order for your SIP Endpoint to receive calls from Twilio, you will use the same TwiML or REST API calls you use today. The only difference is that you will now be specifying your Twilio Interconnect Connection, by including the edge
parameter in the URI with the value of the Twilio Interconnect Edge Location where your private connection is configured, for example:
1<Response>2<Dial>3<Sip>4sip:yourusername@yourdomain.com;edge={EDGE_LOCATION}5</Sip>6</Dial>7</Response>8
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:
1<Response>2<Dial>3<Sip>4sip:yourusername@yourdomain.com;tnx={TNX_SID}5</Sip>6</Dial>7</Response>8
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 Locations | Protocol | Source IP | Source Port † | Destination IP Ranges | Destination 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) | UDP | ANY | ANY | 168.86.128.0/18 | 10,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.
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).
1208.78.112.642208.78.112.653208.78.112.664Ports: 5060 (UDP/TCP), 5061 (TLS)5
167.213.136.64267.213.136.65367.213.136.664Ports: 5060 (UDP/TCP), 5061 (TLS)5
1185.187.132.682185.187.132.693185.187.132.704Ports: 5060 (UDP/TCP), 5061 (TLS)5
1185.194.136.642185.194.136.653185.194.136.664Ports: 5060 (UDP/TCP), 5061 (TLS)5
1103.75.151.682103.75.151.693103.75.151.704Ports: 5060 (UDP/TCP), 5061 (TLS)5
1103.144.142.682103.144.142.693103.144.142.704Ports: 5060 (UDP/TCP), 5061 (TLS)5
1- 103.146.214.682- 103.146.214.693- 103.146.214.704Ports: 5060 (UDP/TCP), 5061 (TLS)5