Ports used by VIP (internal use at the moment)

It is a bit difficult to provide a precise list of ports used by Infinity VIP. The ports required depend on what STUN and TURN service(s) are used as well as what, and how, third party device’s audio streams are connected to and from VIP. Below are some of the most common requirements for VIP. These are described as they would be entered in an AWS Security Group.

Typically we allow ALL TCP and ALL UDP ports to leave the subnet.  Here are the incoming rules:

1. Add Rule:

   1. Protocol = UDP

   2. Type = Custom UDP

   3. Port range = 7000-7031

   4. Source = Custom 0.0.0.0/0

   5. Description = Link audio ports

1. Add Rule

   1. Type = HTTP (port 80)

   2. Protocol = HTTP

   3. Leave autofilled entries

1. Add Rule

   1. Type = HTTPS  (port 443)      

   2. Protocol = HTTPS

   3. Leave autofilled entries

1. Add Rule

   1. Type = Custom TCP

   2. Protocol = TCP

   3. Port Range 35797

   4. Source = Custom 0.0.0.0/0

   5. Using a License Server on the AWS subnet with the VIP instance this port does not have to be allowed from the outside, only within the subnet.

   6. Description = License Server

1. Add Rule

   1. Type = Custom UDP & Custom TCP

   2. Protocol = UDP & TCP

   3. Port Range 3478

   4. Source = Custom 0.0.0.0/0

   5. Description = WebRTC/STUN/TURN

1. Add Rules

   1. Type = Custom UDP

   2. Protocol = UDP

   3. Ports: 20000-24000

   4. Source = Custom 0.0.0.0/0

   5. Description = WebRTC media ports