Effective Date: 9/4/2021
Note: If you want to be informed when this information changes, please sign up here.
This page provides information on how to connect to evercast.us using firewall access rules. It's intended for networking and IT professionals in your organization.
Evercast is a modern, dynamic application that leverages our own servers as well as a range of services to enable a secure and stable end-to-end connection. We leverage WebRTC as well as the STUN and TURN protocols across a range of ports and from our providers at Google, and as necessary, Twilio.
The majority of our traffic will originate from these IP ranges, though occasionally we leverage other AWS-based IP ranges outside of these.
TCP for ports: 80,443 for traffic to app.evercast.us
TCP and UPD for ports: 3478,20000-25000 for traffic to *.evercast-webrtc.com and occasionally other AWS-based IP ranges
TCP and UDP port 19302 for traffic to stun.l.google.com
If the above firewall access rules aren't possible, we can relay traffic via Twilio. This will add a small amount of latency.
TCP port 443, TCP and UDP port 3478, TCP port 5349, UDP ports 10000 - 60000 for traffic to Twilio
Twilio lists STUN/TURN IP address ranges here.
P2P is required for WebRTC to function.
Path MTU discovery (PMTUD) is required to determine packet MTU size.
If access is still blocked after adding these values to the firewall, we recommend testing by allowing all traffic to the MAC address of the connecting device.