This article outlines configuration changes that may be required on your corporate network to allow Coviu to work. Typically, your IT Network Administrator would undertake these activities.
Last updated: Mar 2021
NOTE: This article only applies to our clients in the United States.
For Network Administrators: Test as you go!
Anyone can use the below pre-call test to see if they are ready to use Coviu however Network Administrators can use the pre-call test to see if Coviu will work on their corporate network. If the test shows failures on UDP, TCP or STUN, then use the below scenarios to troubleshoot and make changes where necessary.
Pre-call test - https://tools.coviu.com/precall
Issue 1: You cannot get to coviu.com
If you are able to view other websites e.g. youtube.com without issue, then read on. If you cannot view any other websites, then you may wish to consult your IT Support staff.
Analysis: your network may have a very tight Web proxy which filters out Websites it does not know.
Remedy: ask your network administrator to allow access to the following domains.
- CUSTOMER-SUBDOMAIN.coviu.us:443 (required)
- coviu.us:443 (required)
- static.coviu.com:443 (required - provides static resources)
- app-images.coviu.com:443 (required - provides application images)
- burger.coviu.com:443 (required - provides the video calling rooms)
- plugins.coviu.com:443 (required - to load special in-call functionality)
- monitor.coviu.us:443 (advisable - we use this to debug any call issues you're reporting)
- use.typekit.net:443 (advised - this provides the right fonts)
- d37gvrvc0wt4s1.cloudfront.net:443 (optional - this allows us to capture application issues)
- www.google-analytics.com:443 (optional - this allows us to capture usage analytics)
- Make sure the Web proxy can do a Websocket upgrade on nexus-websocket-a.intercom.io and nexus-websocket-b.intercom.io port 443.
Issue 2: When trying to connect to another person, they don't appear in your Coviu video room
Analysis: you are not connecting to the Coviu signalling server, which is connecting up the endpoints to each other via Websockets.
Remedy: ask your network administrators to open up the following ports.
These ports are necessary so we get to our ICE/STUN servers to deal with the NAT:
Make sure you also have these accessible in your proxy server:
- witchcraft.covi.io:443 (required - to reach ICE/STUN servers)
- *.coviu.us:443 (required - to reach signalling servers)
- *.twilio.com:443 (required - to reach our backup TURN servers)
- The Web proxy will need to be able to do a Websocket upgrade on all of the above.
Issue 3: when trying to connect to another person, it just says "is being connected" but it never connects.
Analysis: you have decided to close all UDP ports and your firewall does deep packet inspection therefore a connection cannot be established.
Remedy: ask your network administrators to do one of two things: either open up some UDP ports or make sure you can connect to our TURN server even when your firewall requires authentication and does deep packet inspection.
- Open UDP ports in the media range 49152 to 65535. This will often reduce audio/video latency because it avoids the use of a forwarding server and enables direct peer to peer connections.
- If you cannot open UDP ports, our app will try to connect to our TURN servers on port 443 (not unlike a VPN). These domains need to be added to your proxy (required - to reach TURN servers):
- If adding the TURN servers to the proxy is not sufficient, you are likely using deep packet inspections and throwing away the video packets on port 443. Therefore, you will need to add a couple of IP addresses to the bypass list on your proxy:
- This list may need to be refreshed if the TURN servers change IP addresses. But at least you don't have to open up the UDP ports.