--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/voice/api/sip-interconnect#article headline: SIP Interface over Twilio Interconnect description: Connect your SIP infrastructure to Twilio using a private connection with Twilio Interconnect for secure PSTN connectivity and SIP interface use cases. url: https://www.twilio.com/docs/voice/api/sip-interconnect inLanguage: en dateModified: 2026-06-22T10:15:32.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # SIP Interface over Twilio Interconnect > \[!WARNING] > > **On February 21, 2024, Twilio updated the media IPs and port ranges for calls in all regions to 168.86.128.0/18 and expanded the UDP port range to 10000-60000.** Old IP and port ranges no longer accept or send traffic after this date. Connect your SIP infrastructure to Twilio over a private connection by pointing your equipment to localized SIP Domain URIs and using the `edge` parameter in TwiML or API requests. You can use this guide to create inbound or outbound contact centers and enable PSTN connectivity. See [Related reference documentation](#related-reference-documentation) to learn more about the SIP and API elements used in this guide. ## Configure your SIP Interface over Twilio Interconnect ### Sending SIP to Twilio \[#sip-out] 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}.sip.sao-paulo-ix.twilio.com` | São Paulo, Brazil | > \[!NOTE] > > `{example}` will be replaced by the unique part of the SIP Domain that you previously configured. Refer to the SIP Domains page in [Twilio Console](https://1console.twilio.com/go?to=/account/__account__/us1/voice/sip-domains/sip-domains) or the [legacy Console](https://www.twilio.com/console/voice/sip/endpoints) 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). > \[!NOTE] > > If you are looking for the [legacy Interconnect SIP Domain URI list, visit here](/docs/global-infrastructure/localized-uris/interconnect-sip-uris#legacy-interconnect-sip-uris). eg: `{example}.sip.de1.twilio.com` ### Receiving SIP from Twilio over Twilio Interconnect \[#sip-in] 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](/docs/global-infrastructure/edge-locations#private-interconnect) where your private connection is configured, for example: ```xml sip:yourusername@example.com;edge={EDGE_LOCATION} ``` 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: ```xml sip:yourusername@example.com;tnx={TNX_SID} ``` ### Media IP addresses using Twilio Interconnect \[#IPwhitelist-tnx] **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. ### SIGNALLING IP addresses using Twilio Interconnect \[#IPwhitelist-tnx] 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 ```bash 208.78.112.64 208.78.112.65 208.78.112.66 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### North America Oregon Interconnect Gateways ```bash 67.213.136.64 67.213.136.65 67.213.136.66 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### Europe London Interconnect Gateways ```bash 185.187.132.68 185.187.132.69 185.187.132.70 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### Europe Frankfurt Interconnect Gateways ```bash 185.194.136.64 185.194.136.65 185.194.136.66 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### Asia Pacific Singapore Interconnect Gateways ```bash 103.75.151.68 103.75.151.69 103.75.151.70 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### Asia Pacific Tokyo Interconnect Gateways ```bash 103.144.142.68 103.144.142.69 103.144.142.70 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### Asia Pacific Sydney Interconnect Gateways ```bash 103.146.214.68 103.146.214.69 103.146.214.70 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` #### South America São Paulo Interconnect Gateways ```bash 159.183.255.68 159.183.255.69 159.183.255.70 Ports: 5060 (UDP/TCP), 5061 (TLS) ``` ## Use cases for SIP Interface over Twilio Interconnect with Twilio Programmable Voice This guide teaches the basics required for the following use cases: ### Create an inbound contact center with Twilio Programmable Voice You can use this guide to securely route incoming calls from the PSTN to your private SIP infrastructure for inbound contact center agents. To learn more advanced features that you can use with inbound contact centers, see [Voice inbound call center](/docs/voice/guides/inbound-call-center). ### Create an outbound call center with Twilio Programmable Voice You can use this guide to send SIP traffic from your private infrastructure to Twilio's SIP Interface to place outbound calls to the PSTN. To learn more advanced features that you can use with outbound call centers, see [Voice outbound call center](/docs/voice/guides/outbound-call-center). ### Enable PSTN connectivity with Twilio Programmable Voice You can use this guide to bridge your private SIP network with the public switched telephone network (PSTN) using a dedicated, private connection. To learn more advanced features that you can use with PSTN connectivity, see [Voice PSTN connectivity](/docs/voice/guides/pstn-connectivity). ## Result After following this guide, you have established a private, secure path for SIP signaling and media between your infrastructure and Twilio. You can confirm it worked by placing a test call and verifying that the traffic traverses your Interconnect connection rather than the public internet, and by checking that signaling reaches the correct localized SIP URI. ## Next steps Explore the following guides to build on what you've learned in this guide: * [Emergency calling for SIP interfaces](/docs/voice/sip/emergency-calling): Configure emergency call routing and address validation for your SIP infrastructure. * [SIP](/docs/voice/sip): Explore the foundational concepts and configuration options for Twilio SIP Interfaces. * [How to add programmability to your existing SIP network](/docs/voice/tutorials/how-to-add-programmability-to-your-existing-sip-network): Learn how to wrap your SIP calls in TwiML to add features like recording and IVRs. * [SIP API](/docs/voice/sip/api): Manage your SIP Domains, IP access control lists, and credentials programmatically. * [Secure media](/docs/voice/api/secure-media): Implement SRTP to encrypt your media streams for enhanced security. ## Related reference documentation Find reference documentation for the topics on this page. * [SIP Domain resource](/docs/voice/sip/api/sip-domain-resource) * [SIP Credential resource](/docs/voice/sip/api/sip-credential-resource) * [SIP IpAddress resource](/docs/voice/sip/api/sip-ipaddress-resource) * [TwiML™ Voice: ``](/docs/voice/twiml/sip) * [Understanding Twilio media edges](/docs/voice/voice-insights/api/call/understanding-edges)