Your conference room has great cameras and microphones. The displays are perfect. But video calls still lag, freeze, or drop randomly. Audio cuts in and out. Participants complain about echo and delays.
Here’s what most people miss: the network infrastructure powering your video conferencing equipment matters as much as the equipment itself. You can have the best Zoom Room hardware in the world, but if your network switch is a $30 unmanaged unit from Amazon and you’ve never configured Quality of Service, your calls will suffer.
I’ve designed networks for hundreds of conference rooms. The difference between properly configured infrastructure and default settings is night and day. Proper PoE switches deliver clean power and data simultaneously. QoS configuration ensures video traffic gets priority over file downloads. The result? Calls that actually work reliably.
This guide covers exactly how to build network infrastructure for professional video conferencing—Power over Ethernet fundamentals, choosing the right switches, QoS configuration for low latency, and the mistakes that create call quality issues.
Let’s make your conference room network actually support great video calls.
Understanding Power over Ethernet (PoE)
PoE delivers both power and data over a single Ethernet cable. Essential for modern conference rooms.
Why PoE Matters for Video Conferencing
Simplifies installation: One cable to each device instead of separate power and data cables.
Cleaner setup: No power adapters cluttering tables or visible on walls.
Flexibility: Place cameras anywhere without nearby power outlets.
Reliability: Centralized power from switch with UPS backup possible.
Cost savings: Electrician doesn’t need to run power to every camera and device location.
PoE Standards Explained
PoE (802.3af): Original standard. 15.4W per port. Enough for basic IP cameras, VoIP phones.
PoE+ (802.3at): 25.5W per port. Supports PTZ cameras, access points, many conference devices.
PoE++ (802.3bt) Type 3: 51W per port. Powers demanding devices like video bars.
PoE++ (802.3bt) Type 4: 71W per port. High-power devices, multiple concurrent devices per port.
What you need: PoE+ minimum for most conference room equipment. PoE++ for high-end video bars and displays.
Calculating PoE Power Budget
Each device draws power: Add up all connected devices’ power requirements.
Example conference room:
- PTZ camera: 20W (PoE+)
- Ceiling microphone array: 15W (PoE)
- Touchpanel controller: 12W (PoE)
- Wall-mounted tablet: 10W (PoE)
- Total: 57W
Switch power budget: Switch must supply total power needed.
Headroom: Don’t max out switch capacity. Leave 20-30% headroom.
Example: Room needs 57W. Choose switch with 80W+ PoE budget for that port count.
When planning complete conference room installations, PoE requirements drive switch selection.
Choosing Network Switches for Conference Rooms
Not all switches are created equal. Conference rooms need specific capabilities.
Managed vs Unmanaged Switches
Unmanaged switches: Plug and play. No configuration. Cheap ($20-100).
Limitations: Can’t configure VLANs, QoS, port priorities, or monitor traffic.
Managed switches: Fully configurable. VLAN support. QoS capabilities. Monitoring.
Cost: $100-$1,000+ depending on port count and features.
For conference rooms: Managed switches are non-negotiable. QoS alone justifies the cost.
Key Features to Look For
PoE support: PoE+ minimum, PoE++ preferred for flexibility.
Gigabit ports: 1000 Mbps minimum. 100 Mbps ports are obsolete for video.
QoS capabilities: Layer 2 or Layer 3 QoS. Essential for prioritizing video traffic.
VLAN support: Segregate conference room traffic from general network.
Port count: Enough ports for current needs plus 30% growth.
Uplink speed: 10 Gigabit uplink to core network ideal for multiple conference rooms.
Management interface: Web GUI for configuration. CLI optional but useful.
Switch Recommendations by Room Size
Small huddle room (4-6 people):
- 8-port PoE+ managed switch
- Example: Netgear GS108PP, TP-Link TL-SG108PE
- Cost: $100-200
- Powers: Camera, mic, touchpanel, with ports to spare
Medium conference room (6-14 people):
- 16-24 port PoE+ managed switch
- Example: Cisco SG250-10P, Netgear GS724TP
- Cost: $300-600
- Powers: Multiple cameras, mic arrays, displays, control systems
Large boardroom (15+ people):
- 24-48 port PoE++ managed switch or multiple switches
- Example: Cisco Catalyst 9200, HPE Aruba 2930F
- Cost: $1,000-$3,000+
- Powers: Everything plus redundancy
For executive meeting spaces, switch reliability and features are critical—failures aren’t acceptable.
Quality of Service (QoS) Fundamentals
QoS is the difference between reliable and frustrating video calls.
What QoS Actually Does
Traffic prioritization: Ensures video/audio packets get through before file transfers or web browsing.
Bandwidth allocation: Reserves bandwidth for critical applications.
Latency reduction: Minimizes delays in video and audio transmission.
Jitter control: Reduces variation in packet arrival times (smooths video).
Without QoS: All traffic treated equally. Background download can kill video call quality.
With QoS: Video call gets priority. Downloads slow down instead of call degrading.
Why Video Conferencing Needs QoS
Real-time requirement: Video and audio can’t buffer like Netflix. Delays are immediately noticeable.
Latency sensitivity: Over 150ms latency makes conversations awkward. QoS keeps latency low.
Packet loss intolerant: Lost video packets = frozen frames. Lost audio packets = garbled speech.
Bandwidth competition: Other network traffic can starve video if not prioritized.
Professional appearance: Laggy, choppy calls look unprofessional. QoS prevents this.
Understanding complete bandwidth planning shows how QoS fits into overall network design.
Configuring QoS for Video Conferencing
Actually setting this up properly.
Layer 2 vs Layer 3 QoS
Layer 2 QoS (802.1p):
- Works at switch level
- Uses Class of Service (CoS) values (0-7)
- Good for single-subnet environments
- Most conference room switches support this
Layer 3 QoS (DSCP):
- Works at network layer
- Uses Differentiated Services Code Point values
- Survives routing between subnets
- Better for enterprise networks
For most conference rooms: Layer 2 sufficient if room on same subnet as uplink.
DSCP Marking for Microsoft Teams
Microsoft Teams uses specific DSCP values:
- Audio: DSCP 46 (EF – Expedited Forwarding) – highest priority
- Video: DSCP 34 (AF41) – high priority
- Screen sharing: DSCP 18 (AF21) – medium priority
- Other traffic: DSCP 0 – best effort
Configure switch: Recognize these DSCP markings and prioritize accordingly.
Client-side marking: Windows and Mac Teams clients mark traffic if configured via Group Policy.
Network-side marking: Switch can also mark traffic based on port or application if clients don’t.
Port-Based QoS Configuration
Identify conference room ports: Which switch ports connect to video conferencing equipment?
Priority assignment: Set these ports to high priority.
Example configuration:
- Ports 1-4: Conference room devices (High priority, guaranteed 50% bandwidth)
- Ports 5-12: User devices (Medium priority, guaranteed 30% bandwidth)
- Ports 13-24: General use (Low priority, best effort)
Bandwidth reservation: Ensure high-priority ports get bandwidth even under load.
Trust Boundaries
What it means: Which device’s QoS markings does network trust?
Options:
- Trust endpoint (Teams client marks traffic, switch honors it)
- Trust switch (switch marks traffic based on port/application)
- Trust router (edge router handles all marking)
Best practice for conference rooms: Trust the switch. Conference room switch marks traffic from known video conferencing devices.
Why: Centralized control. Don’t rely on every endpoint to mark correctly.
Advanced QoS Strategies
Beyond basic configuration.
Queue Configuration
Switches have output queues: Packets wait in queues before transmission.
Priority queuing:
- Queue 1: Highest priority (audio, critical video)
- Queue 2: High priority (video, screen sharing)
- Queue 3: Medium priority (general traffic)
- Queue 4: Low priority (background transfers)
Scheduling algorithms:
- Strict priority: Higher queues always go first
- Weighted Round Robin: Each queue gets proportion of bandwidth
- Hybrid: Strict for highest queue, weighted for others
For video conferencing: Strict priority for audio queue, weighted for rest prevents audio issues.
Bandwidth Allocation
Guarantee minimums: Reserve bandwidth for critical applications.
Example allocation:
- Video conferencing: 40% minimum, 80% maximum
- General network: 20% minimum, 60% maximum
- Background transfers: No minimum, 40% maximum
Prevents starvation: Even low-priority traffic gets some bandwidth eventually.
Peak usage: High-priority traffic can burst up to maximum when available.
Rate Limiting
Prevent bandwidth hogging: Limit how much bandwidth any single application/user can consume.
Use cases:
- Limit file transfers to 50 Mbps (leaves bandwidth for video)
- Cap individual user downloads
- Restrict streaming video quality
Conference room application: Limit non-video traffic on conference room ports so it can’t interfere.
Network Segmentation and VLANs
Isolating conference room traffic improves performance and security.
Why Segment Conference Room Network
Performance isolation: Conference traffic doesn’t compete with general network traffic.
Security: Segregate video conferencing equipment from general user network.
Simplified management: All conference rooms on same VLAN, easy to apply policies.
Multicast efficiency: Video conferencing multicast traffic stays within VLAN.
VLAN Configuration Example
VLAN structure:
- VLAN 10: Conference room control systems
- VLAN 20: Conference room cameras and audio
- VLAN 30: User devices (laptops, phones)
- VLAN 40: General network resources
Benefits: QoS policies applied to entire VLAN. Conference equipment isolated from security threats on user VLAN.
Inter-VLAN routing: Controlled via firewall/router. Conference rooms can access internet and servers but not all user devices.
Trunk Ports and Access Ports
Access ports: Connect end devices (cameras, PCs). Assigned to single VLAN.
Trunk ports: Connect switches together. Carry multiple VLANs.
Configuration:
- Conference room devices: Access ports on VLAN 20
- Uplink to core switch: Trunk port carrying VLANs 10, 20, 30
- User laptops: Access ports on VLAN 30
Prevents confusion: Devices automatically on correct VLAN based on which port they connect to.
When building comprehensive AV infrastructure, VLAN design is foundational.
Monitoring and Troubleshooting
How to identify and fix network issues affecting video quality.
Network Monitoring Tools
Switch management interface: Most managed switches show per-port statistics.
What to monitor:
- Bandwidth utilization (is port saturated?)
- Packet errors (CRC errors, collisions)
- Queue depths (are packets waiting excessively?)
- PoE power consumption (devices getting enough power?)
SNMP monitoring: Advanced. Collect statistics over time, graph trends, set alerts.
Third-party tools: PRTG, Nagios, SolarWinds monitor switch health and performance.
Identifying QoS Issues
Symptoms of missing/misconfigured QoS:
- Video quality degrades during business hours
- Calls fine when network is quiet, terrible when busy
- File transfers cause video freezing
- Audio drops or distorts randomly
Testing:
- Schedule video call during quiet time (6am)
- Note quality (probably fine)
- Schedule call during peak (2pm)
- Start large file transfer during call
- If quality tanks = QoS not working
Verification: Check switch QoS statistics. Are packets actually being prioritized?
Common Configuration Mistakes
QoS enabled but not configured: Switch has QoS capability but all traffic same priority = useless.
Wrong DSCP/CoS values: Marking traffic incorrectly so switch doesn’t recognize it.
Asymmetric QoS: Configured on conference room switch but not on core switch = half the path unprioritized.
Insufficient bandwidth: QoS can’t create bandwidth. If link is saturated, even prioritized traffic suffers.
Mismatched trust boundaries: Endpoint marks traffic, switch ignores and remarks incorrectly.
For persistent issues, see troubleshooting conference systems.
PoE Switch Placement and Wiring
Physical location and cabling matter.
In-Room vs Centralized Switches
In-room switch:
- Located in conference room equipment rack
- Short cable runs to devices (cleaner, easier)
- One switch per room
- Accessible for troubleshooting
Centralized switch closet:
- All conference rooms connect to central switch
- Longer cable runs required
- Easier centralized management
- Better for large installations
Most common: In-room switch for medium/large conference rooms. Centralized for small huddle rooms.
Cable Run Best Practices
Use Cat6 or Cat6a: Cat5e works for gigabit but Cat6/6a provides future-proofing and better PoE performance.
Maximum length: 100 meters (328 feet) for Ethernet. Keep under 90 meters for headroom.
Avoid interference: Separate from power cables by 12+ inches. Cross at 90-degree angles when unavoidable.
Proper termination: Punch down or crimp correctly. Bad terminations cause packet errors and speed issues.
Test every run: Cable certifier or tester. Verify all pairs working, proper speeds achieved.
Labeling: Every cable labeled at both ends. Future troubleshooting depends on this.
Proper cable management and infrastructure prevents problems and simplifies maintenance.
Redundancy and Failover
For critical conference rooms, single points of failure aren’t acceptable.
Dual Network Connections
Primary and backup: Two network paths to conference room.
Automatic failover: Switch or equipment detects primary failure, switches to backup.
Implementation: Devices with dual network ports (some enterprise video codecs support this).
Cost: Doubles network infrastructure but provides reliability.
UPS for PoE Switches
Uninterruptible power supply: Battery backup keeps switch powered during outages.
Runtime: 15-30 minutes typical. Enough to finish current meeting or gracefully shut down.
PoE benefit: UPS powering switch also powers all PoE devices. Single UPS protects entire room.
Sizing: Calculate total PoE power draw plus switch consumption. UPS must handle full load.
Critical rooms: Boardrooms, executive offices, mission-critical spaces should have UPS.
Link Aggregation
Multiple uplinks bundled: Two or more cables to core switch act as one.
Benefits: Higher bandwidth, automatic failover if one link fails.
LACP (Link Aggregation Control Protocol): Standard protocol for link aggregation.
Example: Two 1 Gigabit uplinks = 2 Gigabit total bandwidth with redundancy.
Use case: Conference room switch supporting multiple rooms or very high-bandwidth requirements.
Real-World Deployment Scenarios
How this actually gets implemented.
Single Conference Room Setup
Equipment:
- 8-port PoE+ managed switch ($150)
- PTZ camera, ceiling mic, touchpanel, codec
- Uplink to building network
Configuration:
- PoE ports: Camera (PoE+), mic (PoE), touchpanel (PoE), codec (PoE+ or AC powered)
- QoS: DSCP-based, trusting codec markings
- VLAN: Conference room VLAN
- Monitoring: SNMP to IT monitoring system
Total cost: $150 switch + $100 configuration time + cables
Multi-Room Installation
Scenario: 5 conference rooms in building.
Option 1 – Individual switches: Switch per room. Easier installation, more switches to manage.
Option 2 – Centralized: One large PoE switch in IDF. Longer cable runs but centralized management.
Best practice: Depends on building layout. Centralized if rooms are clustered. Individual if spread out.
Management: VLAN per room or single conference VLAN for all. QoS applied uniformly.
Enterprise-Grade Deployment
Large organization: 50+ conference rooms across multiple buildings.
Infrastructure:
- Cisco Catalyst or similar enterprise switches
- Dedicated conference VLAN across organization
- Centralized QoS policies
- Network monitoring and alerting
- Redundant core networking
Management: Professional network team. Standardized configurations. Change control processes.
Support: NOC monitors conference room network health. Proactive issue resolution.
For commercial-scale installations, enterprise networking practices are essential.
Cost Analysis
What this actually costs to implement properly.
Budget Conference Room Network
Small huddle room:
- 8-port PoE managed switch: $100-150
- Cat6 cables: $50
- Configuration time: 2 hours
- Total: $150-250
Good enough for: Small rooms, non-critical use, tight budgets.
Mid-Range Conference Room Network
Medium conference room:
- 16-port PoE+ managed switch: $300-500
- Quality Cat6 cables and termination: $100-150
- Professional configuration: $300-500
- Total: $700-$1,150
Gets you: Proper QoS, adequate PoE budget, professional setup.
Enterprise Conference Room Network
Large boardroom:
- 24-48 port PoE++ enterprise switch: $1,500-3,000
- Structured cabling: $500-1,000
- Professional design and configuration: $1,000-2,000
- UPS backup: $300-600
- Monitoring integration: $200-500
- Total: $3,500-$7,100
Delivers: Maximum reliability, redundancy, professional support, no compromises.
Understanding complete installation costs helps budget appropriately for network infrastructure.
The Bottom Line
Network infrastructure isn’t the sexy part of video conferencing. Nobody walks into a conference room and says “wow, great PoE switch!”
But it’s the foundation everything else sits on. Proper PoE switches deliver clean power and data. Configured QoS ensures video traffic gets priority. The result is calls that work reliably instead of frustrating participants.
The investment isn’t huge—$150-500 for proper switch in most rooms, plus configuration time. But the impact is dramatic. Difference between “our video always works” and “our video is unreliable.”
Don’t cheap out on network infrastructure. It’s the one place where cutting corners guarantees problems. Invest in proper PoE switches, configure QoS correctly, and build network foundation that supports great video conferencing.
Your future meeting participants will thank you—even if they don’t know why calls suddenly work better.
