SIP Interface over Twilio Interconnect
Twilio Interconnect allows you to connect your SIP infrastructure using a private connection (e.g. VPN, cross-connect) to a Twilio SIP Interface.
Configure your SIP Interface over Twilio Interconnect
Sending SIP to Twilio
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
Receiving SIP from Twilio over Twilio Interconnect
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 tnx
parameter in the URI with the value of the desired Twilio Interconnect connection, for example:
<Response> <Dial> <Sip> sip:yourusername@yourdomain.com;tnx={TNX_SID} </Sip> </Dial> </Response>
IP addresses using Twilio Interconnect
We strongly encourage you to allow 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)
Europe Frankfurt Interconnect Gateways:
Signalling IPs:
185.194.136.64 185.194.136.65 185.194.136.66 Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
185.194.136.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)
Asia Pacific Tokyo Interconnect Gateways:
Signalling IPs:
103.144.142.68 103.144.142.69 103.144.142.70 Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
103.144.142.64/26 Port Range: 10,000 to 20,000 (UDP)
Asia Pacific Sydney Interconnect Gateways:
Signalling IPs:
- 103.146.214.68 - 103.146.214.69 - 103.146.214.70 Ports: 5060 (UDP/TCP), 5061 (TLS)
Media IPs:
- 103.146.214.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 by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.