Opening Internal Ports
- Mark Fernie
- Ken Gordon
- Patrick H (Unlicensed)
These ports are internal to your LAN. You do not need to open these ports externally to the Internet.
If your network is divided into multiple subnets/VLANs, then you will need to open them between the relevant subnets/VLANs.
If using Multi-Display or Combined Rooms, ports will additionally need to be open in between Vivi Boxes (e.g. within the VLAN).
These terms are described in more detail in the definitions section.
Vivi requires these ports and the Return Traffic ports in order to operate. Below, you'll find a list of these ports along with descriptions of their respective purposes.
Port Details
Port | Protocol | Description |
Functional Ports: The following ports are all required to be opened between your end user devices (e.g. laptops) and Vivi Boxes for Vivi to work. | ||
6000 | TCP | Screen Sharing – Apple AirPlay negotiation, Video stream fallback |
7000 | TCP | Screen Sharing – Apple AirPlay negotiation |
7100 | TCP | Screen Sharing – Video stream |
8000 | TCP | Screen Sharing – Apple AirPlay negotiation |
8001 | UDP | Screen Sharing – Apple AirPlay timing channel |
8002 | UDP | Screen Sharing – Control messages |
8003 | UDP | Screen Sharing – Audio stream |
12800 | TCP | Vivi Client API (HTTP/S) – How the Vivi Client talks to the Box Touch input Data |
12801 | TCP | Vivi Client API (HTTP/S) – Static image serving |
12802 | TCP | Local files streamed to the Box |
Administration Ports: These ports are not required for users to access Vivi, but instead will be used by IT Admins. Some are optional (see details below). | ||
80 | TCP | Web Console (HTTP) – Also required for Bulk Configuration via Vivi Central |
161 | UDP | SNMP – Available for diagnostic monitoring, if desired |
443 | TCP | Web Console (HTTPS) – Also required for Bulk Configuration via Vivi Central |
5001 | TCP | iPerf 2 – Available for network bandwidth testing - may be requested by Vivi Support |
Video Announcements: These ports are also required to be opened in order to use the Video announcements feature. | ||
3001 | TCP | Video Announcements |
12819 | TCP | Video Announcements - WebRTC Signaling |
12821-12824 | UDP | Video Announcements - Video and Audio streams |
12820-13999 | UDP | Video Announcements - Video and Audio streams (This port range is required to be open inbound on the broadcasting device)* |
WebRTC Split Screen: This additional port range must also be opened in order to use WebRTC Split Screen functionality | ||
12820-12836 | UDP | WebRTC - Video / Audio streams (Split Screen) |
Our improved Video Announcements feature uses RTCP (Real-Time Transport Control Protocol) to monitor the performance of the audio and video streams and to quickly deal with problems like lost packets. This results in a much smoother and reliable experience when making a Video Announcement. To support RTCP, each Vivi box that is receiving the Video Announcement needs to make 2 UDP connections (1 for audio, 1 for video) to the client. This means if you are making a Video Announcement from your client to 10 boxes, your computer will receive a total of 20 inbound UDP connections. The large inbound UDP range here makes it possible to broadcast a Video Announcement to a large number of Vivi boxes simultaneously
🔄 Return Traffic (Ephemeral Ports)
Port Range: 32768–65535
Purpose: These ports are designated by the Internet Assigned Numbers Authority (IANA) for dynamic or private use. They are commonly utilized by client applications to establish temporary outbound connections and to receive return traffic from established sessions.
Usage Notes:
When a client initiates a connection to a server (e.g., accessing a web page over HTTPS on port 443), the client's operating system assigns a source port from this dynamic range.
These ports are ephemeral, meaning they are used for the duration of a session and then released for future use.
Most modern operating systems, including Windows Vista and later versions, default to this range for ephemeral ports.
Firewall Configuration:
Ensure that outbound traffic from this port range is permitted to allow client applications to establish connections.
Allow inbound return traffic associated with these ephemeral ports to enable proper response handling for client-initiated sessions.
Testing Ports
Once you have opened the necessary ports within your network, you can use the Vivi App to confirm these have been opened.
To run the check:
Log in to the Vivi App on an end user device and connect to a room.
Click on the Settings Icon > Room Settings > Port Check.
The results will be shown on the Display that the Vivi Box is connected to.
