Third Party Exchange is yet another way of creating an interconnect connection with Twilio. By utilizing the 3rd party Exchange option, our customers can connect to Twilio's infrastructure from a 3rd party provider (Currently supported: ECX, Megaport, Epsilon & Packet Fabric) to create a Cross Connect connection. This is extremely advantageous for customers that have their calling infrastructure hosted in the cloud and would like to maintain their existing provider. In order to do this, you/your provider and Twilio will have to configure our respective network components.
Your border devices (e.g. IP-PBX, SIP-PRI IAD, Session Border Controller, NAT gateway, etc.) will need to be assigned IPv4 addresses.
The addresses have to be public IPs - as opposed to [RFC 1918](https://tools.ietf.org/html/rfc1918) address ranges - to avoid conflicts with other networks that Twilio platform is peered with. In other words, your IP addresses have to be outside of the following ranges:
You will need to add Twilio's IP ranges to the access control list on your firewall (e.g. AWS Network ACL) to allow your and Twilio's platform elements to talk to each other.
All services accessed over the Third Party Exchange will come from known Twilio IP ranges. We encourage you to allow all of our IP ranges and ports on your firewall.
Assuming that your provider (Third Party) can extend a circuit for you from the location where you are connecting to them to an Equinix exchange location, this process is very similar to Cross Connect.
Let your Twilio on-boarding contact know your:
- Desired connection location
- Required bandwidth
- Your IP addresses
- Twilio account SID
Twilio configures your 3rd Party Exchange connection
Your on-boarding contact will let you know when provisioning is complete.
Allow traffic from Twilio to your network.