PlayInfoBox

Home /Utilities /Video Conferencing Firewall & Port Troubleshooting Guide

Video Conferencing Firewall & Port Troubleshooting Guide

The order to check things in, from a firewall-and-ports angle, when video calls keep dropping or won't connect.

  1. Why firewalls can block video calls

    Video conferencing apps exchange screen and audio in real time, which requires a broad range of UDP ports in addition to standard web traffic (HTTPS, port 443). When a corporate, school, or government firewall blocks those ports for security, the app still opens, but audio and video keep cutting out or the call never connects at all.

  2. The baseline: HTTPS (443) and DNS (53)

    Every video conferencing app relies on the same TCP port 443 (HTTPS) as regular web traffic for basics like login, joining a meeting, and chat. If even this port, or DNS (port 53) which resolves domain names, is blocked, the app won't even launch β€” so this is the first thing to check.

  3. The ports Zoom typically uses

    Zoom mainly uses UDP 8801–8810 for screen and audio data, and falls back to TCP 443/8801–8810 if those are blocked. When asking your network administrator to open ports, it's most accurate to reference the current range listed in Zoom's own official support documentation.

  4. Ports used by Microsoft Teams and Google Meet

    Teams primarily uses UDP 3478–3481 for real-time audio and video, while Google Meet and other Google services built on WebRTC mainly use the UDP 19302–19309 range. Both will attempt to fall back to TCP 443 if those ports are blocked, but latency and video quality tend to suffer.

  5. Why blocking UDP hurts video quality

    Real-time video conferencing is optimized for UDP, which prioritizes speed over guaranteeing every packet arrives. When UDP is blocked and the app falls back to TCP, it has to wait for retransmissions of lost data, which actually increases lag β€” often showing up as "my internet is fine, but only video calls keep freezing."

  6. The order to check when a call won't connect

    First confirm whether other apps on the same network (like regular web browsing) work fine, to rule out a general internet problem. If those work, try switching to a different network β€” like a personal mobile hotspot β€” and see if the issue disappears; if it does, a firewall or proxy on your usual network is the likely cause.

  7. What to give your IT team when requesting an exception

    Share the exact video conferencing app and version you're using, the specific symptom (can't connect at all, versus connecting but with poor quality), and the exact port list from the app's official support documentation. Because port ranges can shift slightly with app updates, referencing the current official documentation rather than an old blog post gets a faster, more accurate fix.

A quick primer on how firewalls decide what to block

A firewall inspects traffic against a set of rules β€” by port number, protocol, or destination address β€” and only lets through what matches an allowed rule. Corporate and school networks often default to blocking a wide range of ports for security, which is exactly the kind of policy that can catch video conferencing's UDP traffic even when regular web browsing works fine.

Know the exact port numbers before you escalate

Beyond video conferencing, plenty of other everyday services rely on specific port numbers β€” email, remote access, file transfer, and more. Having a general sense of which ports map to which common services makes it much easier to describe a connectivity problem accurately when you're troubleshooting with an IT team or comparing notes with colleagues.

Frequently Asked Questions

It works fine at home but not at the office β€” does that always mean it's the firewall?

That's the most likely cause, but limited office Wi-Fi bandwidth or proxy server settings can also be the culprit. Trying a wired connection, or checking whether a coworker on the same network has the same issue, helps narrow it down.

I asked for a firewall exception and it still doesn't work β€” what now?

If your office network routes traffic through a proxy server, opening the port alone may not be enough β€” the proxy configuration also needs to allow it. In that case, it's worth asking your IT team to add the video conferencing domains to the proxy's exception list as well.