Below are the recommended firewall requirements for WorkLink:

Service	URL/Ports	Connection Type	Failure Symptom
Authentication Server	cms.scopear.comTCP:443	Client to Server and Server to Client for web traffic.	User will be unable to log-in.
Master Server	master.scopear.comUDP:24000TCP:24000	Client to Server and Server to Client for call brokering and presence registration.	Expert list not shown.
WorkLink App (Calling functionality)	UDP:11690-11700, UDP, TCP:5060- 5070 UDP, TCP 5060 - 5070: Audio and Video communication (WebRTC Peer to Peer)UDP 11693-11698: (Client to Zeus)UDP 11699-11700: (Client to Tunnel)	Client to Client	- Failure to connect calls. - No audio in calls. - Contact list issues.
Proxy Servers	proxy.scopear.com,proxy-de.scopear.com,proxy-sg.scopear.comUDP:3478, 49152-65535TCP:3478, 80, 443	Client to Server and Server to Client on port 3478 for initial STUN communications. Client (WL app) to Client (WL app) through relay.	- Failure to connect calls. - No audio in calls.
External Proxy Servers / Twilio(highly recommended)	Global URL:global.turn.twilio.comRegion-specific url: <regionID>.turn.twilio.comPorts: 443 (TCP and UDP), 3478 (TCP and UDP),  5349 TCP, 10,000-60,000 UDPTCP 3478: relay connectivityUDP 3478: relay connectivity Additional Info: You can find IP addresses for regional access on this link: https://www.twilio.com/docs/stun-turn/regions	Client to Server and Server to Client on port 3478 for initial STUN communications. Client (WL app) to Client (WL app) through relay.	- Failure to connect calls.- Poor Audio/Video - No audio in calls.
Guest invite Routing/ Resource Catalog	getworklink.com TCP: 443	Client to Server and Server to Client for web traffic	- Guest email links are not working - Can’t connect to resource catalog

Please note that:

• 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.

Note: 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.