Connectivity Requirements
The Prevail Session Application requires an open connection between specific ports and destinations to support various tools and features. To ensure you can access the Prevail Sessions application and its features, you may need to configure your network firewall or log out of your VPN. Please contact your company’s IT department or Prevail Customer Success at CustomerSuccess@prevail.ai if you need further assistance.
To check your connection, please visit the Amazon Chime Readiness Check.
Connect from Outside a VPN
Most companies use Virtual Private Network (VPN) services to secure data accessed by employees working remotely. However, VPNs may block ports required by the application or significantly slow the data flow between Prevail’s servers and your computer. To ensure the best possible connection to the application, connect directly to the internet outside of a VPN.
You may lose access to your company email or files when you connect outside a VPN. To ensure access to your materials, you can upload your documents to your Prevail Briefcase before your Session.
General Firewall Configuration
The Prevail Session Application relies on Amazon Chime as its primary meeting service for most Sessions. Chime leverages AWS infrastructure, requiring AWS services and IPs to remain unblocked to avoid disrupting the application’s functionality.
Ports | Destination |
---|---|
TCP/443 | chime.aws |
TCP/443 | *.chime.aws |
TCP/443 | *.amazonaws.com |
TCP/8443 | *.amazonaws.com |
TCP/443 | 99.77.128.0/18 |
UDP/3478 | 99.77.128.0/18 |
TCP/443; 28080 | prevail.ai |
TCP/443 | help.prevail.ai |
TCP/443 | api.prevail.ai |
Agora Firewall Configuration
Prevail also integrates with Agora as an alternative meeting service for complex Session environments. While most Sessions utilize Chime due to its robust feature set, Agora is available for scenarios where additional capabilities may be required.
Ports | Destination |
---|---|
TCP/80; 443; 3433; 4700–5000; 5668; 5669; 6080; 6443; 8667; 9667; 30011–30013. UDP/3478; 4700–5000 | .agora.io |
TCP/80; 443; 3433; 4700–5000; 5668; 5669; 6080; 6443; 8667; 9591; 9593; 9601; 9667; 30011–30013. UDP/3478; 4700–5000 | .edge.agora.io |
TCP/80; 443; 3433; 4700–5000; 5668; 5669; 6080; 6443; 8667; 9591; 9593; 9601; 9667; 30011–30013. UDP/3478; 4700–5000 | .edge.sd-rtn.com |
TCP/80; 443; 3433; 4700–5000; 5668; 5669; 6080; 6443; 8667; 9667; 30011–30013. UDP/3478; 4700–5000 | .sd-rtn.com |
TCP/443; 6443; 9591; 9593; 9601 | .edge.agora.io |
TCP/443; 6443; 9591; 9593; 9601 | .edge.sd-rtn.com |
TCP/443; 6443; 9591; 9593; 9601 | web-1.ap.sd-rtn.com |
TCP/443; 6443; 9591; 9593; 9601 | web-2.ap.sd-rtn.com |
TCP/443; 6443; 9591; 9593; 9601 | ap-web-1.agora.io |
TCP/443; 6443; 9591; 9593; 9601 | ap-web-2.agora.io |
TCP/443; 6443; 9591; 9593; 9601 | webcollector-rtm.agora.io |
TCP/443; 6443; 9591; 9593; 9601 | logservice-rtm.agora.io |
TCP/443; 6443; 9591; 9593; 9601 | rtm.statscollector.sd-rtn.com |
TCP/443; 6443; 9591; 9593; 9601 | rtm.logservice.sd-rtn.com |