Understanding WebRTC and Network/Firewall Requirements

Skreen utilizes WebRTC (Web Real-Time Communication) to establish direct, peer-to-peer data streams between the customer's browser and the agent's browser whenever possible. This ensures the highest quality and lowest latency.

How the Connection Works

1. Signaling: Both browsers connect to Skreen's secure websocket servers over standard HTTPS (Port 443) to exchange connection details securely.
2. ICE Negotiation: Browsers attempt to find the best possible route to connect to each other. They use STUN servers to discover their public IP addresses.
3. Direct Connection: If network topologies allow, a direct peer-to-peer UDP connection is established for the video stream.
4. TURN Relay (Fallback): If both parties are behind strict NATs or corporate firewalls that block direct UDP traffic, the traffic falls back to secure TURN servers routing over TCP (Port 443).

Corporate Firewall Allowlisting

If an enterprise customer is entirely unable to connect a session, their IT department may be blocking necessary protocols. Ensure the following are permitted on outbound connections:

• TCP Port 443 (HTTPS/WSS): Required for application loading, signaling, and TURN fallback.
• UDP Ports (Dynamic Range): Permitting outbound UDP traffic significantly improves video latency and quality compared to TCP fallback.

Skreen currently utilizes Cloudflare's global edge network for STUN routing.