Vital uses WebRTC technology to allow video and audio calling between devices such as web browsers, smartphones, and smart glasses. Restrictive network configurations using firewalls and proxy servers may cause connectivity and performance issues. Use the below settings, troubleshooting tools and articles to diagnose and fix connectivity problems.
Host Names and Ports
The below hostnames and ports should be whitelisted to allow traffic through a firewall or proxy to Vital's servers and third-party servers:
- app.vital.enterprises TCP port 443
- api-prod.vital.enterprises TCP port 443
- file.api.vital.enterprises TCP port 443
- stun.l.google.com UDP port 19302
- *.xirsys.com TCP + UDP ports 443, 3478, 5349 and UDP ports 49152 - 65535
- psXX.pndsn.com (the value of XX ranges from 1 to 19) port 443
- clouderrorreporting.googleapis.com port 443
We strongly recommend that you do not use proxy servers for Vital network traffic. Proxying traffic adds latency and can cause Vital to automatically reduce the video and audio quality. Also, Vital provides the same benefits for video traffic that a proxy does, so a proxy isn’t needed. If proxy servers must be used in your network, please:
- Understand that proxy servers can severely impact performance.
- Ensure that Vital traffic is whitelisted in the proxy configuration.
- Ensure that the network bypasses the proxy for Vital outbound ports.
The following are useful tools for troubleshooting WebRTC connectivity:
An article on troubleshooting WebRTC connection issues: