What are Twilio Client's Network Connectivity Requirements?

The following article outlines Twilio Client's requirements for network connectivity. For more Client requirements, please see our article What are Twilio Client's Deployment Best Practices.

Note: Programmable Video has its own network requirements and set of IP addresses.

Port Requirements

Ports used by Twilio Client WebRTC 1.x

The Twilio Client JavaScript SDK will establish a connection to Twilio as documented below:

Component Address Server-side port used  Protocol
Signaling
(Global Low Latency)
chunderw-gll.twilio.com
chunderw-vpc-gll.twilio.com
443 TCP
Signaling
(Regional)

chunderw-vpc-gll-{region}.twilio.com
(region: au1,br1,de1,ie1,jp1,sg1,us1)

443 TCP
Presence matrix.twilio.com 443 TCP
RTP Static IP range * 10,000 - 20,000 UDP
Insights eventgw.twilio.com 443 TCP

* Twilio Client 1.3 and higher lets you select the specific Twilio data center used when your Twilio Client Device connects to Twilio. Network communication to and from Twilio will originate/terminate from the fixed, static IP address ranges listed here for each region. For Client 1.2 and earlier Twilio's media servers are automatically selected based on location and the media service IP address is assigned from the static range of that region.

The client-side will select any available port from the ephemeral range. On most machines, this means the port range 1,024 to 65,535.

Ports used by Twilio Client Mobile 1.x

The Twilio Client iOS and Android SDKs will establish a connection to Twilio as documented below:

Component Address Server-side port used † Protocol
Signaling chunder.gll.twilio.com § 10194

TCP

Presence matrix.twilio.com 443 TCP
RTP Static IP range * 10,000 - 20,000 UDP

* Twilio's media servers are automatically selected based on the location of the mobile device and the media service IP address is assigned from the static range of that region. Note that region selection is not available using mobile Client.

The client-side will select any available port from the ephemeral range. On most machines, this means the port range 1,024 to 65,535.

§ Uses a DNS SRV lookup to resolve this name to _sips._tcp.chunderm.gll.twilio.com.

Ports used by Twilio Programmable Voice SDK 2.x

Component Address Server-side port used † Protocol
Signaling chunderm.gll.twilio.com § 10194

TCP

Signaling
(Regional)

chunderm.{region}.twilio.com

(region: au1,br1,de1,ie1,jp1,sg1,us1)

10194

 

TCP

RTP Static IP range * 10,000 - 20,000 UDP

* Twilio Programmable Voice SDK 2.0 and higher lets you select the specific Twilio data center used when your Twilio SDK Device connects to Twilio. Network communication to and from Twilio will originate/terminate from the fixed, static IP address ranges listed here for each region.

§ Uses a DNS SRV lookup to resolve this name to _sips._tcp.chunderm.gll.twilio.com.

Bandwidth Requirements

Product Codec used Bandwidth required (including overhead)
Twilio Client WebRTC PCMU 10 kilobytes/second
Twilio Client Mobile PCMU 10 kilobytes/second
 

Firewall Configuration

  • How should I configure my firewall to support Twilio Client? Your firewall should allow outgoing UDP to the public internet from the browsers that will be using Twilio Client and allow return traffic in response.
  • Using Twilio Client in heavily restricted networks: If you are operating a restricted network that requires whitelisting of media IPs, our recommendation is to specify the region in your application. Twilio will continue to expand our Global Low Latency footprint in the future by adding more regions with different IP ranges and leaving the region selection up to Global Low Latency could result in connections being established to regions that are not whitelisted by your infrastructure which may result in one-way audio or call set up failures.
    It is possible to use Twilio's Network Traversal Service to restrict media traffic to UDP port 3478 by using our TURN servers. The regional media IPs will still need to be whitelisted, as will the TCP signaling port and hosts listed above. For more information about using TURN, please click here.

Additional Resources

Have more questions? Submit a request
Powered by Zendesk