Skip to content
WFCC
Open WFCC

Network requirements for IT teams

This guide outlines the network configuration, domains, protocols, and ports required for WFCC desktop and mobile clients to operate reliably across enterprise firewalls and corporate networks.

ProtocolDestination PortHost / DomainPurpose
TCP443wfcc.pro (and *.wfcc.pro)HTTPS API, authentication, WebSocket sync, file transfer, and Web client
UDP4443wfcc.proReal-time media relay: QUIC and WebTransport (MoQ) audio and video streams
TCP50051wfcc.proCall signaling (gRPC MediaSignaling; fallback via HTTPS on port 443)

WFCC voice and video calls use Media over QUIC (MoQ) running on top of UDP:

  • Native apps (Windows and Android): communicate over raw QUIC (ALPN moqt-16) to UDP port 4443.
  • Browser web clients: communicate over WebTransport HTTP/3 to UDP port 4443.

To ensure uninterrupted calling and messaging across corporate networks:

  1. Allow outbound UDP to destination port 4443:
    • Destination: wfcc.pro (IP resolved dynamically or whitelisted)
    • Protocol: UDP
    • Port: 4443
  2. Allow outbound TCP to destination port 443:
    • Destination: wfcc.pro
    • Protocol: TCP
    • Port: 4443 (HTTPS)
  3. Deep Packet Inspection (DPI) & TLS Inspection:
    • WFCC enforces certificate pinning and strict TLS verification on all QUIC and HTTPS traffic.
    • Do not perform TLS proxying / MITM inspection on wfcc.pro:4443 or wfcc.pro:443, as clients will reject non-canonical certificates to prevent data interception.
Media typeRecommended bandwidth per user
Voice call (Opus)32–64 kbps (bidirectional)
Standard video call (HEVC 720p)350–700 kbps (bidirectional)
Screen sharing (HEVC 1080p)500–1200 kbps (bidirectional)

WFCC’s adaptive bitrate control automatically scales down stream resolution and framerate when network congestion or packet loss is detected, ensuring clear audio even on constrained connections.