Third Party Exchange is yet another way of creating an Interconnect with Twilio. By utilizing the Third Party Exchange option, our customers can connect to Twilio's infrastructure from a 3rd party provider (Currently supported: Equinix Fabric, Megaport, and Packet Fabric) to create a virtual Cross Connect. 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.
Your IP routes must be globally unique ("public IPs") rather than RFC 1918 address ranges. In other words, your IP addresses have to be outside of the following ranges :
You will need to add Twilio's IP routes 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 Twilio's IP routes on your firewall.
Submit a request via the third party exchange portal (i.e. Equinix Fabric, Megaport). To prevent any delays in provisioning, it is important to complete this step before proceeding to step 2.
You will need to provide the following information to submit a request:
Twilio will proceed to set up the connection and allocate a BGP interface (point-to-point) IP along with a private ASN if necessary. You will be notified once the connection has been configured by Twilio. At this point your configuration details will be viewable in Console.
Advertise your IP routes via the Third Party Exchange. The routes for your devices must be announce via BGP to Twilio over the connection.