The following table outlines the required network connections and associated descriptions. This details only the external ports/protocols/services needed for successful operation.

Network Connections Table

Source	Destination	Port/Protocol	Description
System Device Client/App Device	https://cms.example.com https://create.example.com https://dtool.example.com https://minio.example.com https://analytics.example.com https://worklink.example.com https://iot.example.com https://gwl.example.com https://analytics.example.com	TCP: 443	Web Requests - CMS, WorkLink Create, Diagnostic Tools
Client/App Device	zeus.example.com	TCP: 24000	Zeus “Presence” server communication. Displays contact list online/offline status.
Client/App Device	Client/App Device	UDP: 5060-5070	Peer-to-peer calling (most performant, not required) - (If remote assistance is configured)
Client/App Device	proxy.example.com	UDP: 3478, 49152-65535  Or TCP: 3478, 49152-65535	Relay server for peer-to-peer calling (If remote assistance is configured)
IoT Device	mqtt.example.com	TCP: 30883	Mosquitto broker endpoint (If IoT is enabled)

WorkLink Calling

• UDP port ranges will define how many concurrent remote assistance calls users can make. We recommend opening the suggestive range to avoid any performance issues. All traffic is bidirectional.

Debugging Calls

During a WorkLink Call, in the settings menu within the application itself is a “Diagnostics” window to help debug issues. However, in order to ensure all ports are correctly opened, we recommend using Netcat to send messages on the client as well as to receive messages on the server.

 

On-Prem Networking Requirements

Please refer to our on premises (on-prem) documentation for further details:

• Kubernetes - Networking Requirements
• VM Development - Networking Requirements
• VM Development - Calling