Audience: Client IT and networking teams.
If your organisation tightly controls internet traffic through firewalls, pass this information to your IT or networking team.
Askable uses WebSocket and WebRTC connections through our provider LiveKit to transmit data and media content. All transmissions are encrypted using TLS and DTLS protocols. To ensure proper connectivity, configure your corporate firewall to allow outbound traffic to the following addresses and ports.
Required firewall rules
Host | Port | Purpose |
*.livekit.cloud | TCP 443 | Secure WebSocket signaling connection |
*.turn.livekit.cloud | TCP 443 | TURN over TLS (fallback when UDP unavailable) |
*.host.livekit.cloud | UDP 3478 | TURN/UDP servers for connectivity establishment |
All hosts (optional) | UDP 50000-60000 | Direct UDP connections for WebRTC media |
All hosts (optional) | TCP 7881 | TCP connections for WebRTC media |
Optimisation recommendations
For optimal audio and video quality, we strongly recommend allowing access to the UDP port ranges listed above. Additionally, ensure UDP hole-punching is enabled (or disable symmetric NAT if applicable).
This configuration allows devices behind your firewall to establish direct connections to our media servers, resulting in improved performance and reduced latency.
Advanced troubleshooting
Navigate to sessions.askable.com.
Click Sign in in the top right corner and sign in with an Askable account.
Once redirected back to Sessions, right click on the page and select Inspect.
In the dev tools, select the Network tab.
Inside the Network tab, select the WS filter.
Click New call to start a new session.
Click Join call.
Find the item starting with rtc in the network view and click on it.
In the request URL section, copy the URL up to /rtc (for example wss://sessions-xxxxxx.livekit.cloud).
Select the Payload tab and copy the item marked access token.
Navigate to livekit.io/connection-test, enter the URL and access token, and click Start test.
A successful test shows all checks passing.