Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

The following table outlines the required network connections and associated descriptions. This details only the external ports/protocols/services needed for successful operation. If more details are required regarding inter-cluster communications, please contact support@scopear.com

Source

Destination

Port/Protocol

Description

System Device

https://cms.example.com

https://create.example.com

https://dtool.example.com

TCP: 443

Web Requests - CMS, Worklink Create, Diagnostic Tools

System Device

zeus.example.com

TCP: 24000

Zeus “Presence” server communication. Displays contact list online/offline status.

System Device

Client Device

UDP: 5060-5070

Peer-to-peer calling (most performant, not required) - (If remote assistance is configured)

System Device

proxy.example.com

UDP: 3478, 49152-65535

 

Or TCP: 3478

Relay server for peer-to-peer calling (If remote assistance is configured)

System Device

mqtt.example.com

TCP: 443

Mosquitto broker endpoint (If IoT is enabled)

Additional Network Configuration

For remote assistant functionality, we require an MTU of at least 1200 bytes.

Network Configuration Diagnostic Tools

WorkLink offers diagnostic tools for network troubleshooting. Once our platform is deployed into your environment, the following tool will help determine if the required networking access is configured.

Network Diagnostics Tool: https://dtool.yourdomain.com. Replace “yourdomain” with the name of the domain in your environment.

  • No labels