Ring.io is a networked app - it communicates back and forth between your computer and our servers in order to deliver phone calls and real-time info to users. This article describes network requirements that Ring.io relies on to operate smoothly.
For the Ring.io Web Phone
The Ring.io Web Phone is a Google Chrome extension that uses the Twilio Client which uses Chrome's WebRTC stack.
Top section: - Twilio Client WebRTC 1.x (Twilio.js) Port Requirements
IP address ranges to traffic shape - We use the us1 region ID for the most part but not exclusively.
Firewall configuration. See section at top of this page
As of this writing:
Twilio Client WebRTC 1.x (Twilio.js) Port Requirements
Component | Address | Server-side port used † | Protocol |
Signaling - GLL | chunderw-gll.twilio.com | 443 | TCP |
Signaling - | chunderw-vpc-gll-{region}.twilio.com | 443 | TCP |
RTP | Static IP range * | 10,000 - 20,000 | UDP |
Insights | eventgw.twilio.com | 443 | TCP |
† 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.
* 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.