Why Does a Small Conference Room Need Enterprise-Grade Networking?

A small conference room needs enterprise-grade networking because its traffic is real-time, not because it is large. A four-seat room running Microsoft Teams or Zoom sends live audio and video that cannot be resent later, and its touch panel, video bar and display often depend on the network for power and pairing as well as data. A cheap unmanaged switch and a shared office VLAN can turn a well-chosen video bar into a stuttering one.

This post explains which network features matter for a small room, what Microsoft and Zoom actually recommend for QoS and ports, and how PoE and VLANs fit in. For the security side of room equipment, see our earlier post Your Video Conference Is Confidential. But What About the Room Equipment?

Why is meeting room traffic different from normal office traffic?

Email and file transfers tolerate delay; a call does not. Microsoft's QoS guidance for Teams describes jitter as media packets arriving at different rates, which can result in missing words or syllables. Bandwidth alone does not fix that. Microsoft says Teams can deliver HD video in under 1.5 Mbps and prioritises audio over video when bandwidth runs short, yet still recommends QoS because, in its words, QoS provides risk mitigation even when a network has enough bandwidth.

In other words, the problem in a small room is usually contention, not capacity. A large upload on the same switch, or a backup job across the same uplink, competes with the call. Our post Your Internet Is 10Gbps. So Why Is Your Office Network Still Slow? covers the wider bottlenecks.

Should a meeting room be wired or on Wi-Fi?

Wired, wherever possible. Microsoft strongly recommends a wired connection for Teams Rooms devices for stability and performance. Where Wi-Fi is unavoidable, its Teams Rooms preparation guide asks for 5 GHz coverage, wireless channel utilisation below 50%, a signal of -60 dBm or better between the device and at least one access point, and QoS where possible. It also recommends about 10 Mbps up and down per Teams Room.

Zoom's network guidance points the same way for wireless: it recommends the 5 GHz band and Wi-Fi Multimedia (WMM) so real-time traffic gets priority. The room system should be on a cable; the guests' laptops can use Wi-Fi. Our sibling post Is Your Office Ready for Laptops That Have No Ethernet Port? deals with the laptop side of that equation.

What QoS and DSCP settings do Teams and Zoom recommend?

Both platforms publish DSCP values so that switches and routers can prioritise media. They do not use identical schemes, which matters if your rooms run both.

The Teams figures come from Microsoft's QoS guidance for Teams and for Teams Rooms devices; the Zoom figures come from Zoom's own DSCP marking explainer, which notes that its values can be customised.

Two details are easy to miss. Microsoft states QoS "works as expected only when implemented on all links between callers", so a single unmanaged switch in the path undoes it. And Zoom lists Zoom Rooms Appliances among products that do not support DSCP marking through its web portal or Group Policy, so for appliance-based rooms you may need to classify traffic on the network instead. Zoom also warns that tags can be stripped crossing the internet and recommends marking inbound Zoom traffic at the edge.

Which ports and paths need to be open?

Microsoft lists UDP 3478 to 3481, towards its Teams media IP ranges, in the Optimize category of its Microsoft 365 endpoints list, and asks firewalls not to alter the mapped NAT addresses or ports for UDP. Zoom recommends UDP for the best media experience, with TCP supported for proxy traversal only.

Both vendors advise keeping media away from proxies and inspection. Microsoft says Teams Rooms do not support proxy authentication and recommends media bypass proxies and network security devices. Zoom recommends against routing media through proxy infrastructure and suggests exempting Zoom traffic from deep packet inspection.

Why does PoE matter in a room with only a few devices?

Because the few devices are often the ones that keep the room usable. Logitech lists its Tap IP touch controller (Price on request) as an IEEE 802.3af Class 3 PoE device on a 10/100 Mbps Ethernet port. Yealink describes the MeetingBar A40 with CTP25 (Price on request) as using a single Cat5e cable from the bar to the touch console for power and network.

Budget is the risk. Small PoE switches have a fixed total power budget, and adding a camera, panel and access point to the same switch can exceed it. Our post PoE Everything: Smart Office Upgrade or Power Disaster Waiting to Happen? explains how to calculate headroom.

Should meeting rooms have their own VLAN?

Usually yes. Microsoft's Teams Rooms security guidance notes that the devices do not need to connect to an internal LAN and suggests placing them in a secure, isolated network segment with direct internet access, which reduces the attack surface if the internal network is compromised. A room VLAN also makes QoS policies and troubleshooting cleaner, because all the room traffic is in one place.

If you use 802.1X on switch ports, Microsoft says Teams Rooms devices work with most 802.1X configurations, but adds that it cannot test every configuration and you may need to disable such protocols if they cause performance issues. Test before you enforce.

What switch features should a small room network have?

The checklist is short: PoE with enough budget, 802.1p and DSCP-based QoS with strict-priority queuing, 802.1Q VLANs, IGMP snooping if any AV-over-IP is involved, 802.1X, and central management.

• The TP-Link Omada SG2210MP (Price on request) lists eight PoE+ ports with a 150 W budget, 802.1p and DSCP priority with eight queues and strict priority scheduling, voice VLAN, IGMP snooping and 802.1X, with cloud management through an Omada controller.
• The NETGEAR M4250-9G1F-PoE+ (GSM4210PD) (Price on request) is a fanless AV Line switch with a 110 W PoE+ budget; NETGEAR says the M4250 family ships with pre-configured profiles for protocols such as Dante, AES67 and NDI, plus its IGMP Plus multicast handling.
• The HPE Networking Instant On 1930 8-port Class 4 PoE (S$410.40, as listed on 25 Oct 2026) is described by HPE as a cloud-managed Layer 2+ switch that can be run from the Instant On mobile app or a local web interface.

A plain unmanaged switch can power devices but cannot honour QoS markings or separate VLANs. That is the gap our sibling post Why Your Network Switch Is Quietly Becoming a Computer explores further.

What should you check before the next room goes live?

1. Cable the room system, video bar and touch panel; reserve Wi-Fi for guests.
2. Confirm the switch PoE budget covers every powered device with headroom.
3. Put room devices in a dedicated VLAN with direct internet access, as Microsoft suggests.
4. Enable QoS in the Teams admin center and apply DSCP markings on Teams Rooms on Windows via Intune or Group Policy; set Zoom markings in the web portal where supported.
5. Configure switches and routers to trust or classify those markings on every link.
6. Open UDP 3478-3481 to Microsoft's Teams media ranges and the rules Zoom publishes for Zoom, and keep media away from proxies and inspection.
7. Pilot 802.1X on room ports before enforcing it.
8. Add the room to your management platform; our sibling post Can Your IT Team Manage 100 Different Conference Room Devices? covers that step.

Frequently asked questions

How much bandwidth does a small Teams Room need? Microsoft recommends about 10 Mbps up and down per Teams Room, while noting Teams can deliver HD video in under 1.5 Mbps. QoS matters as much as raw bandwidth.

Can a meeting room run on Wi-Fi? It can, but Microsoft strongly recommends a wired connection for Teams Rooms. If Wi-Fi is unavoidable, it suggests 5 GHz coverage, channel utilisation below 50% and a signal of -60 dBm or better.

Do Teams and Zoom use the same DSCP values? Not entirely. Both use EF (46) for audio, but Teams marks video AF41 (34) while Zoom's four-class model uses CS5 (40) for video and screen sharing.

Is an unmanaged PoE switch good enough for one room? It can power devices, but it cannot apply QoS or VLANs. Microsoft notes that QoS only works when implemented on all links between callers.

Should room devices be on the corporate LAN? Microsoft says Teams Rooms devices do not need the internal LAN and suggests an isolated segment with direct internet access to reduce attack opportunities.