<aside> ⚠️

Certain campus and corporate networks, VPNs, and firewalls may, by default, block traffic required for SoWork video calls. If you are using any of these and encounter access issues with SoWork, please try the following steps to resolve them:

Endpoints

Service Host Port / Protocol Explanation
SoWork Services wss://api.sowork.com
*.sowork.com WebSockets, HTTPS Several services on the SoWork domain are required for proper functionality.
Amazon Chime wss://*.chime.aws
chime.aws
*.chime.aws.com
*.amazonaws.com
99.77.128.0/18 WebSockets, HTTPS Required for maintaining connections with SoWork's global video servers.
LiveKit *.livekit.cloud
*.turn.livekit.cloud
*.host.livekit.cloud WebSockets, HTTPS, UDP Required for SoWork real-time audio and video. See the LiveKit section below for full details.
StreamChat wss://*.stream-io-api.com
*.stream-io-api.com WebSockets, HTTPS Used to facilitate SoWork's chat system.
Google Cloud Services *.googleapis.com HTTPS Core app functionality.
Sentry *.sentry.io HTTPS Error reporting.
Payments *.stripe.com
*.stripe.network HTTPS Required for the payment process to function correctly.
SoWork Analytics *.amplitude.com HTTPS Required for Analytics to function correctly.
Intercom wss://*.intercom.io
*.intercom.io
*.intercomcdn.com WebSockets, HTTPS Ensures you can reach our Customer Support.

LiveKit Firewall Configuration

<aside> ℹ️

SoWork uses LiveKit Cloud to power real-time audio and video. LiveKit transmits data over WebSocket (signalling) and WebRTC (media). All traffic is encrypted with TLS and DTLS.

</aside>

Option A - Wildcard Domains (Recommended)

Option B - Explicit Hostnames (Strict Firewalls)

Static IPs (EU, India & US Only)


🔙 Back to Help Center Home

Click here to return to the main Help Center hub