View Categories

Enterprise Network Configuration Settings

Network Configuration Settings #

If you are unable to connect to Bilatreral Base from within an organisation’s network, then provide the following information to the network administrator:

The platform uses WebSocket and WebRTC to transmit data and media. All transmissions are encrypted with TLS and DTLS.

The platform requires access to a few domains in order to establish a connection. If you are behind a corporate firewall, please ensure outbound traffic is allowed to the following addresses and ports:

HOST PORT PURPOSE
*.livekit.cloud TCP: 443 Signal connection over secure WebSocket
*.turn.livekit.cloud TCP: 443 TURN/TLS. Used when UDP connection isn’t viable
*.host.livekit.cloud UDP: 3478 TURN/UDP servers that assist in establishing connectivity
all hosts (optional but highly recommended) UDP: 50000-60000 UDP connection for WebRTC
In order to obtain the best audio and video quality, we recommend allowing access to the UDP ports listed above. Additionally, please ensure UDP hole-punching is enabled (or disable symmetric NAT). This helps machines behind the firewall to establish a direct connection to a LiveKit Cloud media server.

Minimum requirements #

If wildcard hostnames are not allowed by your firewall or security policy, the following are the mimimum set of hostnames required to connect to LiveKit Cloud:

Host Port
bilateralbase-wyk2py65.livekit.cloud TCP 443
bilateralbase-wyk2py65.sfo3.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsfo3a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsfo3b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dfra1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dfra1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dblr1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dblr1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsgp1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsgp1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsyd1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.dsyd1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.osaopaulo1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.osaopaulo1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.oashburn1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.oashburn1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.omarseille1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.omarseille1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.otokyo1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.otokyo1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ophoenix1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ophoenix1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.olondon1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.olondon1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ochicago1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ochicago1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.osingapore1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.osingapore1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.odubai1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.odubai1b.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ojohannesburg1a.production.livekit.cloud TCP 443
bilateralbase-wyk2py65.ojohannesburg1b.production.livekit.cloud TCP 443
sfo3.turn.livekit.cloud TCP 443
dsfo3a.turn.livekit.cloud TCP 443
dsfo3b.turn.livekit.cloud TCP 443
dfra1a.turn.livekit.cloud TCP 443
dfra1b.turn.livekit.cloud TCP 443
dblr1a.turn.livekit.cloud TCP 443
dblr1b.turn.livekit.cloud TCP 443
dsgp1a.turn.livekit.cloud TCP 443
dsgp1b.turn.livekit.cloud TCP 443
dsyd1a.turn.livekit.cloud TCP 443
dsyd1b.turn.livekit.cloud TCP 443
osaopaulo1a.turn.livekit.cloud TCP 443
osaopaulo1b.turn.livekit.cloud TCP 443
oashburn1a.turn.livekit.cloud TCP 443
oashburn1b.turn.livekit.cloud TCP 443
omarseille1a.turn.livekit.cloud TCP 443
omarseille1b.turn.livekit.cloud TCP 443
otokyo1a.turn.livekit.cloud TCP 443
otokyo1b.turn.livekit.cloud TCP 443
ophoenix1a.turn.livekit.cloud TCP 443
ophoenix1b.turn.livekit.cloud TCP 443
olondon1a.turn.livekit.cloud TCP 443
olondon1b.turn.livekit.cloud TCP 443
ochicago1a.turn.livekit.cloud TCP 443
ochicago1b.turn.livekit.cloud TCP 443
osingapore1a.turn.livekit.cloud TCP 443
osingapore1b.turn.livekit.cloud TCP 443
odubai1a.turn.livekit.cloud TCP 443
odubai1b.turn.livekit.cloud TCP 443
ojohannesburg1a.turn.livekit.cloud TCP 443
ojohannesburg1b.turn.livekit.cloud TCP 443

 

last updated 12/9/24 – Check for updated list