Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Getting Started with Third Party Exchanges

Third Party Exchange is yet another way of creating an interconnect connection with Twilio. By utilizing 3rd party Exchange option, our customers can connect to our AWS 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 communication/network 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.

Cross-connect

Your components

  • IP Addresses. 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 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:

10.0.0.0 - 10.255.255.255

172.16.0.0 - 172.31.255.255

192.168.0.0 - 192.168.255.255

  • Firewall. 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.

Twilio components

  • IP Routes. All services accessed over Cross Connect will come from known Twilio IP ranges. We encourage you to whitelist all of our IP ranges and ports on your firewall.

- SIP routes and ports

- Client routes and ports

  • Cross Connect Connection. Twilio will provision bandwidth for your connections at Twilio Interconnect Exchange location(s) selected by you. See connection bandwidth and location options listed below.
Location 10-Mbps 100-Mbps 500-Mbps 1-Gbps
US - Ashburn, Virginia 🚫
US - San Jose, California 🚫
UK - London
Frankfurt - Germany
Singapore
Tokyo - Japan
Sydney - Australia

Configuring your 3rd Party Exchange connection

Step 1:

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 Exchange location, - Desired bandwidth, - Your IP routes, - Twilio account SID.

Step 2: Twilio configures your 3rd Party Exchange connection

Your on-boarding contact will let you know when provisioning is complete.

Step 3: Allow traffic from Twilio to your network

- SIP routes and ports

- Client routes and ports

Next step

Rate this page:

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 browsing the Twilio tag on Stack Overflow.