Video calls on a school or work network
Check a device before a lesson or meeting, and the addresses a school or office IT team needs to allow so video calls work.
Updated 28 October 2026
Why this exists
Online lessons and staff meetings run in the portal's own video classroom. Most home networks need nothing set up. Some school, library and office networks block video calls with a firewall or web filter, and the call then never connects, or connects without picture or sound.
Check a device first
Open Check this device from the waiting room of a lesson or meeting, or from the guest page of a meeting link. It checks, on that device:
- the camera, microphone and speakers;
- that the device can reach the portal;
- that the device can reach the video server;
- that the browser can make video calls.
It says plainly what is blocked and what to do. Nothing is recorded or sent anywhere: the picture and the sound stay on the device.
If the video server is blocked, try another network first. A phone's hotspot usually works. If the call has to work on that network, send the list below to the IT team.
What an IT team needs to allow
All traffic is encrypted (TLS and DTLS). Allow outbound traffic to:
| Address | Port | What it is for |
|---|---|---|
| Your centre's portal address (the one in your browser's address bar) | TCP 443 | The portal itself |
*.supabase.co | TCP 443 (HTTPS and secure WebSocket) | The portal's data, files and live updates |
*.livekit.cloud | TCP 443 | The video server's signal connection (secure WebSocket) |
*.turn.livekit.cloud | TCP 443 | Video over TLS when UDP is blocked |
*.host.livekit.cloud | UDP 3478 | Helps a call find its way through the network |
| Any host (recommended) | UDP 50000 to 60000 | Video and sound, best quality |
| Any host (recommended) | TCP 7881 | Video and sound over TCP |
The ports marked recommended give the best picture and sound. Without them, video still works through TCP 443, but it may be softer.
These are also used by parts of the portal, and are safe to allow:
fonts.googleapis.comandfonts.gstatic.com(fonts);cdn.jsdelivr.net(background blur in calls);*.sentry.io(error reports, so problems can be fixed).
A web filter that inspects secure traffic can break the video's secure WebSocket. If calls still fail after allowing the addresses above, ask the IT team to leave *.livekit.cloud out of that inspection.
If something still does not work
- Run Check this device again after the change, on the same network.
- Make sure the browser is up to date: the latest Chrome, Edge, Safari or Firefox.
- Some school-managed browsers or devices turn the camera, microphone or video calls off. The IT team can switch them back on for the portal's address.
- Contact your centre if the check passes but a call still fails.
Was this article useful?