The below table shows a setup for stateful connections to Vidyo.io.

With Vidyo.io, the connection will be initiated from the client/endpoint side. This means that in most network environments, Vidyo.io 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 Vidyo.io to work.

 

Subnets

206.191.153.64/27
107.6.79.0/26
173.231.176.192/26
74.201.173.128/26
206.191.157.0/26
216.52.1.160/28
107.6.118.192/28
35.154.42.114/32
35.154.231.225/32
13.55.62.3/32
13.54.155.67/32
184.73.112.49/32
54.65.238.40/32
13.113.197.212/32

120.133.9.6/32

120.133.9.7/32

Please note we also use AWS Services which do not guarantee static IPs, their subnets can be found here

https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html

 

 Ports

443 TCP/UDP HTTPS
50000-65535 UDP Media

 

 

 

  • Media ports are negotiated between the endpoint and the Vidyo.io servers.
  • 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?
0 out of 0 found this helpful

0 Comments

Follow
Please sign in to leave a comment.