Firewall configuration: What network ports are required for using SecureVideo?

Support Center > Troubleshooting Connection Issues

Published 12/18/2013 at 6:51pm UTC

Page viewed 3847 times

Symptom

If you are on a business network (or other network using a firewall), your network may be blocking ports that are needed for a smooth video conference, or to be able to connect at all.

 

Some firewalls have a UDP default timeout. If your calls are consistently being dropped after a specific period of time, this may be happening on your network, and the UDP timeout must be removed or greatly increased for the UDP ports noted below. 

 

VSee users: if your videoconference user statistics are showing that you are using a TCP relay, some of the necessary ports are being blocked. 

 

You may also be interested in these articles:

Possible Causes

 

Zoom firewall requirements

Configure your firewall rules the following way:

  • allow outbound TCP 80 and TCP 443 to (hub.securevideo.com, zoom.us, *.zoom.us, and your SecureVideo branded subdomain)
  • allow outbound (TCP 443, TCP 8801-8802, UDP 3478-3479, and UDP 8801-8810) to (8.5.128.0/23, 52.202.62.192/26, 64.211.144.0/24, 69.174.57.0/24, 115.114.131.0/26, 162.12.232.0/22, 162.255.36.0/22, 192.204.12.0/22, 202.177.207.128/27, 202.177.213.96/27, 204.141.28.0/22, 209.9.211.0/24, 209.9.215.0/24, 213.19.144.0/24, 213.19.153.0/24, 221.122.88.128/25, 221.122.89.128/25)

 

 

VSee firewall requirements

Configure your firewall rules the following way: 

  • allow outbound (TCP 5222 and TCP 443) to (talk.vsee.com, xmpp01.vsee.com, xmpp02.vsee.com, and xmpp03.vsee.com)
  • allow outbound (UDP 6000 and TCP 443 and TCP 80) to (cl-relay.vsee.com, usw01-rel.vsee.com, usw02-rel.vsee.com, use01-rel.vsee.com, use02-rel.vsee.com, jp01-rel.vsee.com, euw01-rel.vsee.com, and euw02-rel.vsee.com)
  • allow outbound (UDP 6000 and UDP 3478) to (stun01.vsee.com, stun02.vsee.com, stun-map01.vsee.com, stun-map02.vsee.com)
  • allow outbound (TCP 443 and TCP 80) to (hub.securevideo.com, your SecureVideo branded subdomain, vsee.com, api.vsee.com, client.vsee.com, my.vsee.com, *.pubnub.com, cloudfront.vsee.com, vseeactiveapi.firebaseio.com, mq-aws-us-east-1.iron.io, s3.amazonaws.com, bw.vsee.com
  • For best performance, allow inbound UDP 6000 from all hosts

 

 

VSee firewall tests

1. Attempt to reach: https://talk.vsee.com/http-bind

If you are UNsuccessful, the page will refuse to load (and just "spin" in place), and your network firewall is likely blocking peer-to-peer communications (or instant messaging/XMPP services, or video conferencing software). An exception should be made for "talk.vsee.com"

However, if you are successful, the page will look something like the screencap below. (Your firewall may still be blocking access to necessary servers; see the next section.)

Jabber screencap

 

2. Ping the VSee servers. If any pings fail, please refer your IT team to this web page for necessary ports: http://vsee.com/firewall

 

Pinging VSee servers on Windows 

1. Search for "Command Prompt" from your Start Menu, and click on the program to open it. (Screencap below is for Windows 7. If you are on a Windows 8.1 machine, click on the Windows key on your keyboard, and then click on the magnifying glass icon in the upper right-hand corner to search your computer.)

Screencap showing Command Prompt

 

 

2. Type "ping talk.vsee.com"

Screencap showing ping command

 


3. Press the Enter or Return key.

If the results show "Ping request could not find host talk.vsee.com", then this server is being blocked. 

A successful ping will look like this:

Screencap showing a successful ping

 

You may also want to ping other servers listed on this firewall information page, to ensure that all connections are allowed.

 

 

Pinging VSee servers on Mac

1. Open Network Utility. (To find it, click on the magnifying glass icon in the upper right-hand corner of your computer screen, and type in "Network Utility". Click on the application that appears.)

Screencap showing how to use Spotlight to find Network Utility

 

2. Click on the Ping tab at the top, and then enter talk.vsee.com. Then click on the Ping button in the lower right-hand corner.

Screencap showing the Network Utility program

 

 

3. If the results show "ping: cannot resolve talk.vsee.com: Unknown host", then this server is being blocked. 

A successful ping will look like this:

Screencap showing

 

You may also want to ping other servers listed for VSee on this firewall information page, to ensure that all connections are allowed.

Resolution

If any of your pings were unsuccessful, please refer your IT team to this web page for necessary ports.

 

If you have any questions concerning these ports, please contact the SecureVideo support team at support@securevideo.com

 

This article was last reviewed by our Support team on February 23, 2018.