If your organizational firewall(s) implement egress (outbound request) filtering, your IT team will need to add whitelist rules: one set of rules in order to use the SecureVideo application, and then additional whitelist rules specific to the video engine(s) your organization will use with SecureVideo.
SecureVideo Application Firewall Settings
The below whitelist rules are required for all organizations using egress (outbound request) filtering regardless of the video engine(s) in use:
- Allow outbound TCP 443 to securevideo.com and *.securevideo.com
- Allow outbound TCP 443 to pubnub.com, *.pubnub.com, *.pndsn.com, *.pubnub.net and *.pubnub.io
Please also ensure that if your organization's browsers are configured to check certificate status online (using OCSP, Chrome CRLSet, or equivalent), that you allow outbound TCP 80 to *.digicert.com.
Video Engine Firewall Settings
SecureVideo supports 3 different video engines:
- Zoom (integrated in 2016)
- One-Click (integrated in 2020)
- VSee (integrated in 2013)
If your organization uses egress (outbound request) filtering, please ensure that the firewall settings applicable to the video engine(s) you are using with SecureVideo are implemented prior to testing/using SecureVideo.
Note: all video engines prefer to use UDP by default. While most engines can workaround using TCP, in all cases the call quality will be markedly suboptimal, and will impact the provider/patient experience. In addition to whitelisting the appropriate UDP ports, please be aware that 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 below UDP ports used by your video engine(s).
Zoom Firewall Settings
It is functionally mandatory to apply all rules to outbound connections. To avoid TURN relay latency, it is recommended to apply all rules to inbound connections.
- allow TCP 80 and TCP 443 to (zoom.us, *.zoom.us)
- allow (TCP 443, TCP 8801-8802, UDP 3478-3479, and UDP 8801-8810) to (184.108.40.206/25, 220.127.116.11/25, 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/25, 188.8.131.52/25, 184.108.40.206/24, 220.127.116.11/25, 18.104.22.168/24, 22.214.171.124/25, 126.96.36.199/25, 188.8.131.52/25, 184.108.40.206/25, 220.127.116.11/25, 18.104.22.168/25, 22.214.171.124/25, 126.96.36.199/25, 188.8.131.52/25, 184.108.40.206/25, 220.127.116.11/25, 18.104.22.168/23, 22.214.171.124/23, 126.96.36.199/25, 188.8.131.52/25, 184.108.40.206/23, 220.127.116.11/25, 18.104.22.168/25, 22.214.171.124/32, 126.96.36.199/24, 188.8.131.52/25, 184.108.40.206/23, 220.127.116.11/24, 18.104.22.168/25, 22.214.171.124/25, 126.96.36.199/24, 188.8.131.52/32, 184.108.40.206/26, 220.127.116.11/25, 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/24, 220.127.116.11/22, 18.104.22.168/25, 22.214.171.124/24, 126.96.36.199/23, 188.8.131.52/24, 184.108.40.206/25, 220.127.116.11/24, 18.104.22.168/25, 22.214.171.124/26, 126.96.36.199/26, 188.8.131.52/26, 184.108.40.206/26, 220.127.116.11/24, 18.104.22.168/19, 22.214.171.124/22, 126.96.36.199/20, 188.8.131.52/20, 184.108.40.206/19, 220.127.116.11/20, 18.104.22.168/22, 22.214.171.124/16, 126.96.36.199/24, 188.8.131.52/22, 184.108.40.206/16, 220.127.116.11/19, 18.104.22.168/17, 22.214.171.124/24, 126.96.36.199/24, 188.8.131.52/22, 184.108.40.206/24, 220.127.116.11/22, 18.104.22.168/21, 22.214.171.124/24, 126.96.36.199/22, 188.8.131.52/25, 184.108.40.206/22, 220.127.116.11/22, 18.104.22.168/22, 22.214.171.124/23, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/21, 220.127.116.11/24, 18.104.22.168/25, 22.214.171.124/21, 126.96.36.199/22, 188.8.131.52/22, 184.108.40.206/24, 220.127.116.11/16, 18.104.22.168/20, 22.214.171.124/22, 126.96.36.199/20, 188.8.131.52/20, 184.108.40.206/22, 220.127.116.11/20, 18.104.22.168/20, 22.214.171.124/20, 126.96.36.199/19, 188.8.131.52/21, 184.108.40.206/22, 220.127.116.11/19, 18.104.22.168/21, 22.214.171.124/19, 126.96.36.199/17, 188.8.131.52/22, 184.108.40.206/27, 220.127.116.11/27, 18.104.22.168/21, 22.214.171.124/22, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/24, 220.127.116.11/24, 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/24, 188.8.131.52/27, 184.108.40.206/25, 220.127.116.11/25, 18.104.22.168/27)
- allow (TCP 443, TCP 8801-8802, UDP 3478-3479, and UDP 8801-8810) to 2620:123:2000::/40
*If you would like to receive notifications when additional IP ranges are available, please sign up for our IP address changes announcement list.
One-Click Firewall Settings
For customers who have firewalls which filter outbound requests--generally hospitals, large practice groups, and other medium to large health care organizations--it is required to implement the below firewall settings prior to using One-Click in either a test or live patient environment. Without implementing these settings, a significant proportion of connections can be expected to fail (however, some connections may still succeed due to pre-existing firewall settings for other applications occurring in the very large Twilio UDP range).
Prior to testing or implementing One-Click, please first verify connectivity from all outbound-filtered client networks to Twilio by running the Twilio Network Test at https://networktest.twilio.com/, and confirm that all tests pass from all outbound-filtered networks. If all firewall settings have been implemented and all tests do not pass, please contact our support team.
Signaling (for all of the below hosts): TCP 443; note that these hosts resolve to both IPv4 and IPv6 addresses
Media (for all of the below hosts): UDP 3478, UDP 10,000-60,000, TCP 443, TCP 3478, and TCP 5349
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
The above list is sufficient for providers and patients based in the United States. For international endpoints, please see Twilio's IP addresses page.
Note for organizations using Next Generation Firewalls (NGFWs): even if you pass the Twilio Network Test you may need to implement additional settings depending on your network configuration. For example, some NGFWs may identify STUN application packets routing over the UDP port range 10,000-60,000, in which case the full UDP port range needs to be permitted for STUN. NGFWs may require permitting numerous applications over the UDP port range 10,000-60,000, including (depending on the firewall application definitions) twilio, stun, turn, ice, rtcp, rtp-audio, and rtp-base. To determine the correct application-layer configuration, it may be necessary to capture packets destined for the above address ranges, determine what application is identified by the NGFW, and then permit that application over the full UDP range; and, it may be necessary to do this several times as the NGFW may identify subsequent applications as each new one is permitted.
VSee Firewall Settings
Please see VSee's Firewall page for up-to-date firewall configuration. VSee has last changed their firewall requirements on June 4, 2021.
This article was last reviewed by our Support team on July 7, 2021.