Partners Blog Contact Us

VidyoCloud Firewall Information for Connecting Clients/Endpoints


The below table shows a setup for stateful connections to VidyoCloud. 

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, this information may be needed to control and to perform changes that allow VidyoCloud to work. 

Production Subnets


Staging Subnets




17990 TCP Vidyo Signaling
17992 TCP Vidyo Signaling
1024-2048 TCP H245, Gatekeeper Discovery and Q.931 Call Setup
5060-5061 TCP SIP 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?
6 out of 6 found this helpful



Article is closed for comments.