Allow Outdoo on Your Company Network

Allow the web domains Outdoo needs on your company network

Outdoo’s live AI roleplays run on two partners: LiveKit carries the real-time audio between your browser and the AI buyer, and ElevenLabs generates the buyer’s voice. If your organization filters web traffic, ask your IT team to allow the domains and ports below so reps can start roleplays, hear the AI buyer and get their scorecards. With the wildcard list, it’s a one-time change.

All traffic is outbound from your network and encrypted (TLS for web traffic, DTLS for media). Nothing needs to be opened for inbound connections.

Domains to allow

If you company allow wildcard list (Recommended)

LiveKit and ElevenLabs route each session to the nearest of many regional servers, and they add new ones over time. Wildcards keep Outdoo working through those changes without another request to IT.

Domain	Port	Used for
`*.livekit.cloud`	TCP 443	Live roleplay connection (secure WebSocket signaling)
`*.turn.livekit.cloud`	TCP 443	Relay fallback when UDP is blocked (TURN over TLS)
`*.host.livekit.cloud`	UDP 3478	Relay servers that help set up the audio connection (TURN/UDP)
`*.elevenlabs.io`	TCP 443	AI buyer voice: API, streaming WebSockets and real-time voice

Some firewalls match a wildcard to one subdomain level only. If yours does, also allow *.rtc.elevenlabs.io and *.residency.elevenlabs.io.

The firewall or proxy must let WebSocket connections through on port 443, including the Upgrade: websocket header.

Recommended ports for the best audio

Roleplays still connect with only the domains above, using the TCP 443 relay. For the clearest, lowest-delay audio, LiveKit recommends also allowing these outbound ports:

Destination	Port	Used for
All hosts	UDP 50000–60000	Direct WebRTC audio
All hosts	TCP 7881	WebRTC over TCP when UDP isn’t available

LiveKit also recommends enabling UDP hole-punching (or turning off symmetric NAT) so devices can connect directly to its media servers.

If your network can’t use wildcards

Allow each of these instead, all on TCP 443. LiveKit and ElevenLabs change these lists from time to time, and a missing host stops roleplays in that region, so use the wildcard list when you can.

Host	Used for
`prodoutdoo-gq8or4ok.livekit.cloud`	LiveKit signaling
`prodoutdoo-gq8or4ok.turn.livekit.cloud`	LiveKit relay (TURN/TLS)
`api.elevenlabs.io`	ElevenLabs API and streaming WebSockets
`livekit.rtc.elevenlabs.io`	ElevenLabs real-time voice

LiveKit’s regional media servers (all TCP 443):

prodoutdoo-gq8or4ok.osaopaulo1a.production.livekit.cloud
prodoutdoo-gq8or4ok.osaopaulo1b.production.livekit.cloud
prodoutdoo-gq8or4ok.oashburn1a.production.livekit.cloud
prodoutdoo-gq8or4ok.oashburn1b.production.livekit.cloud
prodoutdoo-gq8or4ok.omarseille1a.production.livekit.cloud
prodoutdoo-gq8or4ok.omarseille1b.production.livekit.cloud
prodoutdoo-gq8or4ok.otokyo1a.production.livekit.cloud
prodoutdoo-gq8or4ok.otokyo1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ophoenix1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ophoenix1b.production.livekit.cloud
prodoutdoo-gq8or4ok.olondon1a.production.livekit.cloud
prodoutdoo-gq8or4ok.olondon1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ochicago1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ochicago1b.production.livekit.cloud
prodoutdoo-gq8or4ok.osingapore1a.production.livekit.cloud
prodoutdoo-gq8or4ok.osingapore1b.production.livekit.cloud
prodoutdoo-gq8or4ok.odubai1a.production.livekit.cloud
prodoutdoo-gq8or4ok.odubai1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ohyderabad1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ohyderabad1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ojohannesburg1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ojohannesburg1b.production.livekit.cloud
prodoutdoo-gq8or4ok.omumbai1a.production.livekit.cloud
prodoutdoo-gq8or4ok.omumbai1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ofrankfurt1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ofrankfurt1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ojerusalem1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ojerusalem1b.production.livekit.cloud
prodoutdoo-gq8or4ok.osydney1a.production.livekit.cloud
prodoutdoo-gq8or4ok.osydney1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ozurich1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ozurich1b.production.livekit.cloud
prodoutdoo-gq8or4ok.osanjose1a.production.livekit.cloud
prodoutdoo-gq8or4ok.osanjose1b.production.livekit.cloud
prodoutdoo-gq8or4ok.ojeddah1a.production.livekit.cloud
prodoutdoo-gq8or4ok.ojeddah1b.production.livekit.cloud
prodoutdoo-gq8or4ok.oosaka1a.production.livekit.cloud
prodoutdoo-gq8or4ok.oosaka1b.production.livekit.cloud
prodoutdoo-gq8or4ok.omontreal1a.production.livekit.cloud
prodoutdoo-gq8or4ok.omontreal1b.production.livekit.cloud
prodoutdoo-gq8or4ok.otoronto1a.production.livekit.cloud
prodoutdoo-gq8or4ok.otoronto1b.production.livekit.cloud
prodoutdoo-gq8or4ok.oqueretaro1a.production.livekit.cloud
prodoutdoo-gq8or4ok.oqueretaro1b.production.livekit.cloud

This LiveKit list matches LiveKit’s documentation as last updated 2026-07-21. Keep *.host.livekit.cloud on UDP 3478 if you can; it has no fixed-host equivalent.

Regional voice environments. If Outdoo tells you your workspace runs in an ElevenLabs regional environment, allow that region’s hosts instead of the two ElevenLabs hosts above:

Region	Hosts
EU	`api.eu.residency.elevenlabs.io`, `livekit.rtc.eu.residency.elevenlabs.io`
India	`api.in.residency.elevenlabs.io`, `livekit.rtc.in.residency.elevenlabs.io`
Singapore	`api.sg.residency.elevenlabs.io`, `livekit.rtc.sg.residency.elevenlabs.io`

Check that it works

From a computer on your company network, in Chrome, Edge or Safari:

Sign in to Outdoo and start any AI roleplay.
Allow microphone access when the browser asks.
Speak for at least 30 seconds. The AI buyer should answer out loud within a second or two.
End the roleplay. The scorecard should load.

If all four work, your network is set up. If the roleplay never connects, the AI buyer stays silent, or the audio is choppy or drops, a network restriction is the likely cause.

IT teams can also run LiveKit’s connection test from the same network to check signaling, TURN and UDP reachability.

Troubleshooting

Roleplays work at home but not at work

Something on the company network is blocking them. Check the domains above with your IT team.

The roleplay connects, but the AI buyer is silent

ElevenLabs traffic is likely blocked. Confirm *.elevenlabs.io is allowed and that WebSocket upgrades on port 443 pass through your proxy.

Audio is choppy, delayed or drops partway through

UDP is probably blocked, so audio is falling back to the TCP relay. Open UDP 3478 to *.host.livekit.cloud and the recommended UDP 50000–60000 range.

The roleplay disconnects after a few seconds

If your firewall inspects encrypted traffic (SSL/TLS inspection), exclude *.livekit.cloud and *.elevenlabs.io from inspection. Inspection breaks long-lived WebSocket and WebRTC connections.

It fails only on VPN

Some VPNs block UDP or route all traffic through a proxy. Apply the same rules to the VPN, or split-tunnel the domains above.

The browser can’t hear you

Check that the browser has microphone permission for Outdoo and that no device policy blocks microphone access.

Still need help?

Contact Outdoo support on support@outdoo.ai or your customer success manager. Include the time it happened, your browser, whether you were on VPN, and a screenshot of what you saw.