Firewall and Port guidelines for IT Administrators

Introduction #

Zoapi Innovations is a leading provider of intelligent solutions for modern workspaces. Our flagship products, Zoapi Hub and Zoapi Scheduler, have been widely recognized for their robust features and ease of usage, making it the preferred choice for enterprises looking to improve their meeting room collaboration capabilities.

This document covers the firewall and port requirements of all Zoapi Products.

With the 10.95xx version, we have made significant changes to the screenshare protocol. There are firewall and port changes.

1. Zoapi Hub Products Requirements #

These cover the Zoapi Hub Products which include:

• Zoapi Hub Meet
• Zoapi Hub Share
• Zoapi Hub Play
• Zoapi Hub Connect

Additionally, these also cover the corresponding Clients:

• Zoapi Controller
• Zoapi Desktop Apps
• Zoapi Mobile Apps
• Zoapi Browser Client

1.1. Internet Access Requirements for Global Server (share.zoapi.com) #

Site	Port/Protocol	Applies To	Reason
share.zoapi.com	443 TCP (HTTPS)	Hub, All Clients	Client & Signaling Server. Allow Websockets
turn01.zoapi.com turn02.zoapi.com	48600-49600 UDP	Hub, All Clients	(Optional) Ephemeral ports – Required when Connect from Any Network Feature is enabled
google.com/reCAPTCHA	443 TCP (HTTPS)	All Clients	Google Recaptcha
recaptcha.net	443 TCP (HTTPS)	All Clients	Google Recaptcha
msftconnecttest.com	80 TCP (HTTP)	Hub Meet, Share & Connect	Microsoft’s internet reachability test site
connectivitytest.gstatic.com	80 TCP (HTTP)	Hub Play	Google internet reachability test site

 

1.2. General Port Requirements (10.9500 & above) #

Clients include Controller and all apps unless wherever mentioned explicitly Hub includes all Hub products unless wherever mentioned explicitly

Port	Protocol	Direction	Reason
443	TCP	Client –> Hub	To connect to Local HTTPS Server on the hub, if internet is not accessible. Allow Websockets
56793	TCP	Client –> Hub	For VNC connections (Admin only) (EXCEPT CONTROLLER)
60000 – 60010	TCP	Client –> Hub	Control & Interop Protocols Allow Websockets
8443	TCP	Client –> Hub Play	For Local configuration and management site on device (Admin only) (EXCEPT CONTROLLER)
56790 – 56860	UDP	Client –> Hub	Zoapi Screen Share & Conferencing Signaling and Media for Browser, Desktop & Mobile Apps

 

1.3. Airplay Port Requirements #

Airplay can be optionally enabled/disabled.

Port	Protocol	Direction	Reason
5353	UDP	Client <–> Hub	mDNS/Bonjour discovery
56861 – 56872	TCP	Client <–> Hub	Airplay media/session ports
60011 – 60022	TCP	Client –> Hub	Airplay receiver control/media listener ports

 

1.4. Miracast (MICE) Port Requirements #

Miracast can be optionally enabled/disabled. Zoapi supports Miracast with these 2 modes of operation:

• Wifi Direct – the connection does not use the network backbone and will typically not depend on firewall restrictions
• Infrastructure Mode (MICE) – Uses the network infrastructure and firewall filters will apply For windows laptops – MICE is supported on Windows 10 1809 and above.

Port	Protocol	Direction	Reason
5353	UDP	Client <–> Hub	mDNS/Bonjour discovery
7236	TCP	Hub –> Client	Miracast Control
7250	TCP	Client –> Hub	MICE Connection/Control
1028 – 1035*	UDP	Client –> Hub	Media
50000	TCP	Hub –> Client	UIBC

*This is not an officially documented port range for Windows devices but the typical port range that is exposed. If you face issues – a wider range might need to be opened. This range should work on Hub Play devices without issues

 

1.5. Legacy General Port Requirements for Desktop Apps (10.9499 & below) #

Port	Protocol	Direction	Reason
443	TCP	Client –> Hub	To connect to Local HTTPS Server on the hub, if internet is not accessible Allow Websockets
80	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
60000	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
56789	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
56791	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
9050	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
9051	TCP	Client –> Hub	Zoapi Desktop App Share Protocol
56790	UDP	Client –> Hub	Zoapi Browser Share

 

1.6. Additional Notes #

• Calendars like iCal, Zimbra, CalDAV and Zoho can operate with on-premise Please review the port requirements provided by the Calendar Server vendor

–  The hub can run multiple UCC applications like Zoom, Microsoft Teams, Google Meet, Cisco Webex etc. Please review the firewall requirements for these apps, as provided by the UCC vendor

• The controller always needs to be paired to a It requires internet access for provisioning and discovery

 

1.7. Port Forwarding #

To allow hubs behind NATs to be discoverable, a port forwarding setting is available on the hub (Under Settings > Network). The Gateway/Router IP can be added here, and the device will advertise itself with this IP along with the IPs it detects on the system.

Actual port forwarding from the Gateway/Router to the device needs to be configured on the router itself.

 

2.   Zoapi Scheduler #

Site	Port/Protocol	Reason
share.zoapi.com	443 TCP (HTTPS)	Zoapi Server for syncing content & settings
clients3.google.com/generate_204	443 TCP(HTTPS)	Internet reachability test site

 

Calendars like iCal, Zimbra, CalDAV and Zoho can operate with on-premise deployments. Please review the port requirements provided by the Calendar Server vendor

 

3.   Zoapi Signage Core and Sync #

3.1. Internet Access Requirements for Global Server (share.zoapi.com) #

Site	Port/Protocol	Reason
zoapi.com	443 TCP (HTTPS)	Zoapi Server to manage access, settings and updates
share.zoapi.com	443 TCP (HTTPS)	Signaling and Management
connectivitytest.gstatic.com	80 TCP (HTTP)	Google internet reachability test site

 

3.2. General Port Requirements #

Port	Protocol	Direction	Reason
8443	TCP	Incoming	For Local configuration and management site on device (Admin Only)

 

The applications only make outgoing connections. The outgoing connections will be restricted to these ports:

Click here for Zoapi Usage Instruction/Standard Operating Procedure

Click here for a list of all Zoapi Hub configurable settings.

Please reach out to support@zoapi.com if you have any queries.