Partners Blog Contact Us

VidyoCloud Firewall Information for Connecting Clients/Endpoints


This article lists the subnets for the following environments:

In addition, ports are listed in this section:

With VidyoCloud, the connection will be initiated from the client/endpoint side. This means that in most network environments, the VidyoCloud applications will work without requiring the network team to modify the configuration. Keep in mind, however, that in some environments which are more restrictive outbound, the network team may need to make changes that allow VidyoCloud to work.

If your organization blocks outbound traffic and your device is unable to reach certain services, you may need to add exceptions to your firewall. To do this, please refer to the How Do I Make Incoming and Outgoing Calls to Vidyo with My SIP/H.323 Endpoints?. This article provides the applicable network addresses and prefixes to include for inbound and outbound calls to Vidyo as it applies to your SIP/H.323 endpoint(s).


VidyoConnect (

Production Subnets (Current)

The following table lists the current VidyoConnect production subnets.  



VidyoCloud Staging ( and Subnets (Current)

The following table lists the current Staging subnets.  



VidyoConnect and VidyoPlatform EU ( and

Production Subnets (Current)

The following table lists the current EU production subnets.  



VidyoConnect Health Edition

( and

Production Subnets (Current)

The following table lists the current VidyoConnect Health Editions production subnets.  



VidyoPlatform ( and VidyoWorks ( PaaS systems


Production Subnets (Current)

The following table lists the current VidyoPlatform and VidyoWorks PaaS production subnets.  


For All VidyoCloud Environments:

We host client downloads on AWS CDN which does not guarantee static IPs. AWS subnets can be found here:



The following table lists the ports, IPs, and ranges.

17990 TCP Vidyo Signaling
17992  TCP Vidyo Signaling
1025-2048 TCP H245, Gatekeeper DIscovery and Q.931 Call Setup
5060-5061 TCP SIP Signaling
443 UDP DTLS Signaling
50000-65535 UDP Media


  • Media ports are negotiated between the endpoint and the VidyoCloud server.
  • VidyoGateway (H.323/SIP) negotiates media ports on UDP or TCP based on the offering from the incoming endpoint.
  • For Vidyo endpoints, if the ports listed above are not allowed, the endpoint will try falling back to VidyoProxy using only 443.
  • Some firewalls may misclassify the media traffic and apply a UDP default timeout. In these cases, calls will always drop at exactly the same time. To avoid call timeouts, change the default (0:02:00 – 2 minutes) to a time that is longer than the longest potential call.


Was this article helpful?
7 out of 7 found this helpful



Article is closed for comments.