Network Security Diagram
Rules for vsee.qa
Purpose | Protocol: Port | Servers | IP Addresses | |
---|---|---|---|---|
MESSENGER SERVICE | ||||
VSee Directory |
|
|
|
|
Qatar TURN Servers |
|
|
|
|
Video Bridge |
|
|
| |
Reserved IP Addresses |
|
| ||
Region Identification Service |
|
|
| |
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 | ||||
SSO / AD |
|
| ||
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. |
|
|
Rules for vseebeta.qa
Purpose | Protocol: Port | Servers | IP Addresses | |
---|---|---|---|---|
MESSENGER SERVICE | ||||
VSee Directory |
|
|
|
|
Qatar TURN Servers |
|
|
|
|
Video Bridge |
|
|
| |
Reserved IP Addresses |
|
| ||
Region Identification Service |
|
|
| |
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 | ||||
SSO / AD |
|
| ||
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. |
|
|
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.
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 & Clinic Service
Code Block |
---|
20.21.208.105 |