Twilio Voice SDK lets you select the specific Twilio data center used when your
Call connects to Twilio. Network communication to and from Twilio will originate/terminate from the fixed, static IP address ranges listed below for each region. Refer to these ranges if you need to configure your local network to allow communication or apply Quality of Service routing rules to communication with Twilio.
By default, Programmable Voice SDK will use Twilio's Global Low Latency routing capability to determine which data center is closest to your user, establishing a connection through Twilio's nearest point of presence. Global Low Latency uses latency-based DNS lookups to determine the nearest data center. You may want to override this in some cases, especially when your users are working from a fixed location and using a DNS server in another region.
Use any one of the following values as the
region parameter when calling
Voice.setRegion(). Leaving the value undefined will cause Twilio to default to its Global Low Latency routing, which cause the SDK to establish its connection to the Twilio region closest to the user.
|Region ID||Location||Media Server IP Address Range||CIDR notation|
||Australia||18.104.22.168 - 22.214.171.124||126.96.36.199/26|
||Brazil||188.8.131.52 - 184.108.40.206||220.127.116.11/26|
||Ireland||18.104.22.168 - 22.214.171.124, 126.96.36.199 - 188.8.131.52||184.108.40.206/26, 220.127.116.11/24|
||Frankfurt||18.104.22.168 - 22.214.171.124||126.96.36.199/25|
||Japan||188.8.131.52 - 184.108.40.206||220.127.116.11/26|
||Singapore||18.104.22.168 - 22.214.171.124||126.96.36.199/26|
||US East Coast (Virginia)||188.8.131.52 - 184.108.40.206 , 220.127.116.11 - 18.104.22.168||22.214.171.124/23, 126.96.36.199/23|
||Use Twilio's Global Low Latency routing to select the data center with the lowest-latency connection to your user.||Any of the above||Any of the above|
If you have access to private Interconnect connections you will also be able to use one of the following values as the
|Region ID||Location||Signaling and Media Server IP Address Range||CIDR notation||Port Range|
||US East Coast (Virginia) over Interconnect exchange in Virginia||188.8.131.52 - 184.108.40.206||220.127.116.11/26||443 (Signaling), 10,000 - 20,000 (Media)|
||US West Coast (Oregon) over Interconnect exchange in San Jose||18.104.22.168 - 22.214.171.124||126.96.36.199/26||443 (Signaling), 10,000 - 20,000 (Media)|
||Ireland over Interconnect exchange in London||188.8.131.52 - 184.108.40.206||220.127.116.11/26||443 (Signaling), 10,000 - 20,000 (Media)|
Global Low Latency uses latency-based DNS lookups to determine the nearest data center. We introduced setting a region in Voice SDK because there can be cases where the DNS address used by the App using Programmable Voice SDK may not represent their correct region. For example, if you are using a device in UK and the VPN server it is connected to is based in USA. If we relied on latency-based DNS lookups, the region Twilio will choose is going to be
"ie1" would have been preferred. Setting region on the caller side will guarantee the least latency in this scenario.
Force connections through Twilio Ireland:
Force connections through Twilio US East Coast region over your private Interconnect connection to that region:
Let Twilio choose the nearest region, skip setting the region.