Run the built-in connectivity checker first:
app.wejam.ai/check. Microphone access is
required for a full test.
Symptoms
- You can log in and use text chat normally.
- Tapping the voice button fails immediately, or the call ends itself within a few seconds with an error such as “could not establish connection”.
- The problem is consistent - it happens every time, not just occasionally.
Likely cause
WebRTC voice traffic is not allowed on your company network, or the network blocks the signaling connection that starts the call.Background: how Jam Assistant uses the network
To load and use text chat, only TCP port 443 (HTTPS) is required. To create low-latency voice-to-voice interactions, Jam Assistant uses WebRTC through the ElevenLabs EU residency network. The browser must be able to complete WebRTC signaling on TCP/443 and send media traffic over UDP.- ElevenLabs powers the real-time voice AI. Jam Assistant connects to the ElevenLabs EU residency region for voice calls.
- Signaling uses HTTPS/WebSocket traffic on TCP/443.
- Real-time media uses WebRTC UDP traffic, including the standard dynamic UDP port range 49152-65535. Restricting UDP to only
40000-49999can prevent calls from starting.
Debugging steps
- Run the connectivity checker. Direct the user to app.wejam.ai/check (microphone access required). This tests the connection end-to-end and reports whether it’s the WebRTC/media path or the signaling path that’s blocked.
- Whitelist the required domains and ports on the corporate firewall or proxy:
Network requirements (for IT teams)
Jam Assistant’s voice calls use low-latency WebRTC connections, facilitated through ElevenLabs EU residency infrastructure. To ensure reliable operation, the following must be supported in the customer’s network environment: Port accessibility- TCP port 443 is required for HTTPS and WebSocket signaling.
- UDP ports 49152-65535 must be allowed for WebRTC media traffic to ElevenLabs. This is the standard dynamic UDP port range used by WebRTC; observed calls may use ports such as
50674or53396.
link.wejam.ai- Jam Assistant web appapp.wejam.ai- Connectivity checker (/check)api.wejam.ai- REST APIeu.residency.elevenlabs.io- ElevenLabs EU residency servicertc.eu.residency.elevenlabs.io- ElevenLabs WebRTC medialivekit.rtc.eu.residency.elevenlabs.io- ElevenLabs SDK WebRTC mediaturn.rtc.eu.residency.elevenlabs.io- ElevenLabs WebRTC relayapi.eu.residency.elevenlabs.io- ElevenLabs API/signaling
Running voice calls without UDP (WebSocket mode)
If your firewall cannot allow UDP media traffic, ask your JAM contact to switch your organization to WebSocket mode. Every Jam Assistant voice call and every roleplay in your organization then runs over a single encrypted connection on TCP port 443. There is no UDP, no STUN/TURN and no fallback to WebRTC. If the WebSocket test on the connectivity checker passes, WebSocket mode will work on that network. Allow these domains on TCP/443 (HTTPS and WSS):
The
rtc, livekit and turn ElevenLabs domains and the UDP port range above are not needed in WebSocket mode.
Optional: eu.i.posthog.com (product analytics) and *.sentry.io (error reporting). Jam Assistant works without them.
If your proxy inspects encrypted traffic (TLS inspection), exempt api.eu.residency.elevenlabs.io or make sure the proxy passes WebSocket upgrades through. A voice call is one long-lived WebSocket connection that can last up to 30 minutes, so the proxy must not close it after a short idle timeout.
A short network drop of a few seconds does not end a WebSocket call. If the connection stays lost for longer than about 15 seconds, the call ends with an error, and you can start a new call.
Related articles
- Voice Calls - how a normal call works, including other troubleshooting tips
- Frequently Asked Questions - including microphone and audio troubleshooting
Last updated: November 2026

