Enterprise - Network Configuration Requirements (US clients)

This article outlines configuration changes that may be required on your corporate network to allow Coviu to work. Typically, your IT Network Administrator or Cyber Security Manager would undertake these activities.

Last updated: Mar 2022

NOTES:

  • This article only applies to our clients in the United States.
  • Click here for firewall information for Australia and other countries.

On this page:

  1. Who is this help article for?

  2. Firewall port requirements for making a Coviu video call 
  3. Network Administrators: Test as you go!
  4. Troubleshooting Issue 1: Cannot get to coviu.us
  5. Troubleshooting Issue 2: When trying to connect to another person, they never appear in your Coviu video room
  6. Troubleshooting Issue 3: When trying to connect to another person, it just says "is being connected" but it never connects
  7. More support options

Who is this article for?

This article is aimed at your IT Network Administrator, IT Security Manager, Cyber Security Manager or similar titles.

You may need to log a ticket with your IT Service Desk to have them action the below.


Firewall port requirements needed to make a Coviu video call

The table below lists the ports related protocols and hosts that are required.

Port

Protocol

Hosts

Description

443

tcp

coviu.us

Required - Allows you to use the Coviu platform. This must also include subdomains.

443

tcp

coviu.com

Required - Allows you to use the Coviu platform. This must also include subdomains.

443

tcp

covi.io

Required - Call connection on the Coviu platform. This must also include subdomains.

49152-65535

udp

any

Recommended - Allows for peer to peer connections between guests on a call. If you are unable to allow this, you MUST allow the TURN servers listed below.

3478,19302

tcp,udp

turn1.coviu.us

Recommended - TURN servers used to proxy call connections in the event a peer to peer connection cannot be established

443,3478

tcp,udp

global.turn.twilio.com

Recommended - TURN servers used to proxy call connections in the event a peer to peer connection cannot be established

443

tcp

use.typekit.net

Recommended - Used for loading correct fonts

443

tcp

www.google-analytics.com

Optional - Used for capturing usage analytics

 

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 above table and below scenarios to troubleshoot and make changes where necessary.

TIP: Network Administrators can use our pre-call test to test as they go.


Issue 1: You cannot get to coviu.us

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 never 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:

  • tcp/19302
  • udp/19302
  • tcp/3478
  • udp/3478

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. 

  1. 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.
  2. If you cannot open UDP ports, our platform 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):
    1. turn.coviu.com:3478
    2. turn.coviu.us:3478
    3. global.turn.twilio.com:443
  3. 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 the TURN IP addresses to the bypass list on your proxy:
    1. 13.236.71.37
    2. 52.63.56.4
    3. 100.26.78.135
    4. Twilio TURN IP ranges can be found here: https://www.twilio.com/docs/stun-turn/regions
    1. 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.

    More Support Options

    You have completed another Coviu help article. You now know the firewall requirements required to use Coviu.

    If this is not what you were looking for, explore our knowledge base and search for another article from here.

    If you still require any assistance, please do not hesitate to get in touch with our friendly Customer Success team using any of the contact methods available here.

     

    Author: KM