Overview
VSee Messenger will attempt to navigate network architecture to its best ability. However, in order to guarantee the best results, please add the following port and firewall rules to your corporate firewall / router systems.
Please note VSee is generally not able to provide the fixed IP addresses for these servers because they may be switched without prior notification. However, other than the bandwidth server, most IPs are relatively stationary.
Simplified Rules
If *.vsee.com can be whitelisted, please add them into your firewall rules with the following ports:
| Purpose | Protocol: Port | Detail Servers |
| VSee Directory, Relay, Call management, Diagnostics etc Required for VSee Messenger authentication, address book services, establishing video calls, video packets relay, VSee Messenger chat communication. | UDP (STUN): 3478, 6000, 6001, 6256 UDP: 6000, 1853 UDP: 10000 TCP (XMPP) 5222 TCP: 3478 HTTPS – TLS 1.2: 443 TLS: 443 UDP: 49152 – 65535 (TURN allocated) |
|
| Network route for peer-to-peer UDP (Optional) For optimal performance: Allowing for VSee endpoints to directly communicate with each other. This will improve A/V performance and reduce load on firewalls and web proxies. | UDP |
|
| Call presence and reporting Update VSee user’s status, e.g. Offline, Online, In a call, Busy, etc.
| HTTPS: 443 |
|
| Cloud recording service Record video calls performed via VSee Messenger and/or in-browser calls. The calls will be recorded on the server side and will be available via a cloud link. | HTTPS – TLS: 443 |
|
| Measure bandwidth for video quality adjustment VSee Messenger will call this service to test user’s bandwidth upon launch. Used for choosing optimal call quality. | HTTP(S): 80, 443 |
|
Network Security Diagram
Detailed Rules (US Customers)
If *.vsee.com cannot be whitelisted, the following subdomains and ports are required. Please note the servers listed below are for calls within the United States only.
| Purpose | Protocol: Port | Detail Servers |
| VSee Directory Authentication and address book services for VSee Messenger and in-browser call and chat. | TCP (XMPP): 5222 HTTPS – TLS 1.2: 443 |
|
| Call management Establishing and managing VSee video call sessions. | HTTPS – TLS 1.2: 443 |
|
| Chat file transfer File transfer inside of VSee Messenger and in-browser chat sessions. | HTTPS – TLS 1.2: 443 |
|
| Call presence and reporting Update VSee user’s status, e.g. Offline, Online, In a call, Busy, etc. | HTTPS: 443 |
|
| Messenger diagnostics Various diagnostic messages in VSee Messenger. | HTTPS – TLS 1.2: 443 |
|
| Messenger update service Automated check for new versions of VSee Messenger. | HTTPS – TLS 1.2: 443 |
|
| Cloud recording (optional depends on contract) Record video calls performed via VSee Messenger and/or in-browser calls. The calls will be recorded on the server side and will be available via a cloud link. | HTTPS – TLS: 443 |
|
| Bandwidth Test Measure bandwidth for video quality adjustment | HTTP: 80 HTTPS: 443 |
|
| Profile management (optional) Managing VSee user profile – changing profile details, changing password, etc. | HTTPS – TLS 1.2: 443 |
|
| Network route for peer-to-peer UDP (recommended) For optimal performance: Allowing for VSee endpoints to directly communicate with each other. This will improve A/V performance and reduce load on firewalls and web proxies. VSee Messenger will attempt to bind local UDP port 6000-6255 but router might allocate other public port. | Inbound and outbound for UDP on any port |
|
| Discover network route for peer-to-peer UDP (optional) | UDP (STUN): 3478, 6000, 6001, 6256 |
|
| US TURN Servers ** Servers that relay packets during VSee video call in case no peer-to-peer connection can be established. | UDP: 3478 TCP: 3478 TLS: 443 UDP: 49152 – 65535 (TURN allocated) |
|
| Region Identification Service Used to detect the endpoint’s region, to choose the optimal video bridge server for better call performance. | TCP: 443 |
|
| Video Bridge ** During a VSee video call networking packets may pass through a video bridge server for best perfomance. | TCP: 443 UDP: 10000 |
|
| US Relays Relay packets in case no peer-to-peer connection and no TURN connection can be established. | UDP: 6000, 1853 HTTP:80 HTTPS: 443 |
|
Connectivity Testing Service A set of test tools to define if the VSee user’s network conditions are good enough for video calls, checking the reachability of critical VSee infrastructure. | HTTPS: 443 |
|
** Subject to change with at least 1 month of prior notice. We might be adding more video bridge / TURN servers for better performance
Performance Impact of Web Proxies: The VSee client can connect to all the above hosts via a Web Proxy. However, A/V performance will be dependent on the Web Proxy’s capacity. Some factors that might affect performance through a proxy are:
- Load on the Web Proxy
- Prioritization of persistent HTTP(S) connections through the proxy.
For optimal performance:
- The Web Proxy should allow persistent HTTP(S) connections.
- The Web Proxy should be configured to allow traffic to the VSee TURN Servers to proceed directly.
Detailed Rules (International Customers)
For international customers, please apply all rules in the US Customers section as well as the following:
| Purpose | Protocol: Port | Detail Servers |
| International TURN servers | UDP: 3478 TCP: 3478 TLS: 443 UDP: 49152 – 65535 (TURN allocated) |
|
Testing VSee Connectivity
- You can use the following page to test for basic VSee connectivity: VSee Network Test Page
- If any of the test above result in failure, you need to resolve it first.
- All tests pass might not mean you will have a successful call. It is important to ensure that the firewall rules are to follow.
Update on 21 Jun 2022:
Removed International Relays
sg01-rel.vsee.com, euw01-rel.vsee.com
Update on 15 Jun 2022:
- Removed US Relays
use01-rel.vsee.com, use02-rel.vsee.com
Update on 30 May 2022:
- Added TURN connectivity test URL – https://test.vsee.com/turn
- Added new TURN servers
- US EAST –
cl-coturn-use04.vsee.com, cl-coturn-use05.vsee.com, cl-coturn-use06.vsee.com, cl-coturn-use07.vsee.com, cl-coturn-use08.vsee.com - US WEST –
cl-coturn-usw03.vsee.com, cl-coturn-usw04.vsee.com, cl-coturn-usw05.vsee.com, cl-coturn-usw06.vsee.com, cl-coturn-usw07.vsee.com
- US EAST –
Update on 4 Jun 2021:
- Total of 20 video bridges will be available in Aug 1, 2021
- IP addresses are added for convenience
Update on 16 Feb 2021:
- Added 5 more video bridges jvb04-nvir.vsee.com, jvb01-ncal.vsee.com, jvb02-ncal.vsee.com, jvb03-ncal.vsee.com, jvb04-ncal.vsee.com
- Removed port 4443, 10001-20000 range for video bridge
- Removed US Relays usw03-rel.vsee.com, use03-rel.vsee.com, use04-rel.vsee.com, use05-rel.vsee.com
- Removed International Relays euw02-rel.vsee.com
- Removed International TURN server cl-coturn-sn01.vsee.com
Update on 13 July 2020:
- Updated network connectivity test URL
- Increase priority for Peer-to-peer UDP
- Added 6001, 6256 port for STUN
- Added note for new TURN, Video bridge will be added in with 1 month notice
- Added region.vsee.com
Update on 8 Jun 2020:
- Added cl-coturn-ohio01.vsee.com, cl-coturn-ohio02.vsee.com, cl-coturn-oregon01.vsee.com, cl-coturn-oregon02.vsee.com into TURN server list
Update on 1 Jun 2020:
- Added UDP: 49152 – 65535 (TURN allocated) to TURN protocol / port info