Firewall Configuration
- An Nguyen
- Anton Tolkachiov
- Hoa Le Quang
- Kirby Avendula
Overview
VSee services will attempt to navigate network architecture to the best of their 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 that VSee is not able to provide fixed IP addresses for these servers and they may be switched without prior notification. However, these IP addresses are relatively stationary and any changes will be updated here if they occur.
All firewall rules are subject to change with at least 1 month of prior notice.
Network Security Diagram
Simplified Rules
If *.vsee.com can be whitelisted, please add this 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. Measure bandwidth for video quality adjustment |
|
|
Call presence and reporting Update VSee user’s status, e.g. Offline, Online, In a call, Busy, etc. |
|
|
Cloud recording service (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. |
|
|
Detailed Rules (US Customers)
Please note the servers listed below are for calls within the United States only.
If *.vsee.com cannot be whitelisted, the following subdomains and ports are required.
Purpose | Protocol: Port | Servers | IP Addresses | |
|---|---|---|---|---|
MESSENGER SERVICE | ||||
VSee Directory |
|
|
|
|
US TURN Servers |
|
|
|
|
Region Identification Service |
|
|
|
|
Video Bridge |
|
|
|
|
Messenger update service Automated check for new versions of VSee Messenger |
|
|
|
|
Profile management Managing VSee user profile, changing password, etc. |
|
|
|
|
|
|
| ||
Messenger diagnostics Diagnostic information gathered by VSee Messenger |
|
|
|
|
CLINIC SERVICE |
|
| ||
Clinic web and API cluster Basic Clinic functionality |
|
|
|
|
Call presence and reporting Update VSee users' presence status. |
|
|
|
|
|
|
| ||
|
|
| ||
|
|
|
|
|
OPTIONAL FIREWALL RULES |
|
| ||
MFA / SSO (Depends on contract) Enables login with MFA or using an SSO identity provider. | TCP: 443 |
|
| |
Cloud recording (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. |
|
|
|
|
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. |
|
|
|
|
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
|
|
|
|
|
Video Bridge |
|
|
|
|
Proxy Servers
Many organizations utilize proxy servers with their networks. However, as VSee network traffic is already encrypted, passing this traffic through a proxy server does not make it any more secure. On the other hand, proxy servers can introduce performance problems. Proxy servers can introduce latency and packet loss, which can degrade audio and video quality where real-time streams are essential. Thus, bypassing proxies for VSee traffic is recommended as routing through all traffic through a proxy server might impact connectivity and A/V performance.
If proxy servers can not be bypassed, VSee services can connect to the above hosts via a proxy server. We recommend the following for better performance with a proxy server:
Proxy servers should allow persistent TCP connections.
Proxy servers should be configured to allow UDP traffic to the VSee TURN Servers at port 3478 and the Video Bridges at port 10000 to proceed directly.
Testing VSee Connectivity
VSee provides a suite of tools to help test that firewall rules are configured appropriately. Please note that only a subset of the requirements listed above are tested by these tools. It is important to ensure that the firewall rules listed above are followed, even if these tests pass. Failing to follow the firewall configuration requirements may cause issues such as intermittent bad call quality or dropped calls.
Test | URL |
|---|---|
Basic VSee connectivity | |
TURN connectivity | |
Other tools |
Outbound Connections
VSee services may occasionally need to connect with your systems for webhooks and callbacks, or to securely transfer patient / encounter data through SFTP, etc. Here are the lists of IP addresses that should be whitelisted.
Messenger Service
13.52.171.113
52.9.150.124
184.72.21.195
184.72.47.83
54.241.101.173
Clinic Service
13.52.7.6
13.56.46.159
52.52.174.230
54.177.111.163
13.52.58.237
18.144.134.162
54.241.243.156
54.176.136.131
13.56.219.50
13.56.202.120
13.56.70.155
50.18.137.251
13.52.25.116
Updates
Update on 1 Aug 2023
Updated correct list of Clinic Service IPs.
The following IPs are no longer valid
54.153.119.24, 18.144.69.7, 52.53.171.200, 54.176.88.134, 18.144.8.250, 52.53.190.38, 54.177.38.2, 54.215.4.54, 54.193.243.179, 184.72.50.250
Update on 13 July 2023
Relayout content, separate out IP addresses for easy copy & paste
Removed legacy relay servers
Added in Singapore Video bridge
Added dedicated section for Testing VSee Connectivity
Added Outbound Connections section