Fixing High Latency and Jitter on Staff WiFi

This authoritative technical reference guide examines the root causes of high latency and jitter on enterprise staff WiFi networks, providing network architects and IT directors with actionable strategies to diagnose and resolve performance degradation affecting real-time applications such as Microsoft Teams and Zoom. It covers RF environment optimisation, end-to-end QoS implementation, roaming mechanics, and client management techniques. Venue operators and IT teams will find concrete implementation guidance, real-world case studies, and measurable benchmarks to ensure their wireless infrastructure supports seamless staff mobility and collaboration.

📖 8 min read📝 1,839 words🔧 2 worked examples❓ 3 practice questions📚 9 key definitions

Listen to this guide

View podcast transcript

Welcome to the Purple Technical Briefing. I'm your host, and today we are tackling one of the most persistent challenges in enterprise networking: fixing high latency and jitter on staff WiFi.

If you're an IT director, a network architect, or managing operations at a large venue — whether that's a stadium, a retail chain, or a hospital — you know that WiFi is no longer just a convenience. It's a critical operational dependency. When your staff are using Microsoft Teams, Zoom, or Voice over WLAN devices, and they experience dropped calls, robotic audio, or freezing video, it directly impacts productivity and, ultimately, the bottom line.

So, today, we're going to dive into the technical root causes of high latency and jitter, and more importantly, give you actionable strategies to resolve them. This is a senior consultant briefing, not a textbook lecture, so we'll move at pace.

Let's start with a quick definition to set the scene. Latency is the time it takes for a data packet to travel from the source to the destination. Jitter is the variation in that delay — the inconsistency. Think of latency as the journey time, and jitter as the traffic jam. Voice and video applications can handle a bit of latency — up to about one hundred and fifty milliseconds one-way — but they absolutely hate jitter. If packets arrive out of order or with highly variable timing, the receiving buffer drops them, and you get that choppy, robotic audio that makes calls unusable. The industry benchmark you should be targeting is one-way latency below fifty milliseconds and jitter below twenty milliseconds for enterprise-grade VoIP and video conferencing. That's your target.

So, what causes this on a wireless network? Let's go through the primary root causes one by one.

The number one culprit is the RF environment itself. WiFi is a half-duplex medium. It uses a protocol called CSMA/CA — Carrier Sense Multiple Access with Collision Avoidance. In plain English, that means only one device can talk on a specific channel at a time. Everyone else has to wait their turn. Think of it like a conference call where only one person can speak at once, and everyone else is on mute waiting for a gap.

If you have a dense deployment — say in a retail store or a conference centre — and you have multiple Access Points operating on the same channel, you get Co-Channel Interference, or CCI. Those APs and their clients are all sharing the same airtime. The more devices waiting to talk, the higher the latency. The solution here is robust channel planning. You need to leverage the five gigahertz band, which has significantly more non-overlapping channels, and carefully tune your transmit power levels so APs aren't shouting over each other. Turning the power down and deploying more APs at lower power is almost always the right answer in high-density environments.

Another major issue is low data rates. If you allow legacy devices to connect at one or two megabits per second, they take a disproportionately long time to transmit their data. They are eating up a massive slice of the airtime pie, forcing faster devices to wait. Best practice? Disable those legacy rates. Force clients to use more efficient modulation schemes. Specifically, disable rates below twelve megabits per second on the five gigahertz band. It clears the airwaves and drops latency for everyone on that access point.

Now, let's talk about Quality of Service, or QoS. Without QoS, a large file download is treated exactly the same as a critical Teams call. That's a recipe for disaster in any enterprise environment. You must implement Wi-Fi Multimedia, or WMM, on your corporate SSIDs. This ensures voice and video traffic is placed into high-priority hardware queues on the access point, ahead of bulk data traffic.

But here's the critical point that many deployments get wrong: QoS must be end-to-end. Your wireless controller might be marking packets correctly with the right DSCP values — Differentiated Services Code Point — but if your wired switches aren't configured to trust those markings, the packets get re-classified back into the Best Effort queue the moment they hit the wire. You need to configure your switch ports connecting to the APs and the wireless LAN controller to explicitly trust DSCP markings. Without this, your wireless QoS configuration is essentially doing nothing beyond the AP.

Next up: Roaming. This is a huge source of jitter and delay, particularly in venues where staff are mobile — hospitals, warehouses, retail floors, conference centres. When a staff member walks down a corridor on a call, their device has to disconnect from one AP and connect to another. If you're using WPA3-Enterprise with 802.1X authentication — which you absolutely should be for security — that authentication process involves a full RADIUS exchange. Sometimes that takes over five hundred milliseconds. That's half a second. That's an eternity for a voice call, and your users will hear it.

To fix this, you need to enable 802.11r, also known as Fast BSS Transition. This is a standard that allows the client to securely pre-negotiate its credentials with the target AP before it actually roams. The result is that the transition time drops from potentially five hundred milliseconds to under fifty milliseconds. That's the difference between a dropped call and a seamless handover.

Combine 802.11r with 802.11k and 802.11v. 802.11k provides clients with a Neighbour Report — essentially a list of nearby APs and their channels — so the client doesn't have to scan every possible channel to find its next AP. 802.11v allows the network to actively suggest better APs to clients, which is particularly useful for dealing with sticky clients — those devices that stubbornly cling to a distant AP with a weak signal when a better AP is right next to them.

Speaking of sticky clients, this is worth addressing directly. A sticky client is a device that remains associated with an AP even when its signal has dropped to, say, minus eighty dBm, when there's an AP nearby at minus sixty-five dBm. The client is experiencing terrible performance, but it won't roam. The solution is to configure your wireless LAN controller to actively disassociate clients whose signal drops below a defined threshold — typically minus seventy-five dBm is a reasonable starting point. This forces the client to re-associate to a better AP.

Let's also briefly cover airtime fairness. In a standard 802.11 environment, every client gets an equal number of transmission opportunities. But a client connecting at a low data rate takes much longer to use its transmission opportunity than a fast client. This means slow clients disproportionately consume airtime. Airtime fairness flips this around, allocating equal time rather than equal opportunities, which significantly improves latency for the majority of clients.

Now let's do a rapid-fire Q&A based on the most common issues we see in the field.

Question one: My controller shows low channel utilisation, but users still report Teams calls dropping. What's going on?

Answer: Check your roaming configurations. If the airwaves are clear, the delay is almost certainly happening during the AP handover. Verify that 802.11r is enabled on the SSID and that the client devices actually support it. Some older devices don't, and you may need to handle them separately.

Question two: We have strong signal everywhere, but latency spikes during peak hours.

Answer: This is classic Co-Channel Interference. Strong signal doesn't mean clean signal. If your APs are transmitting at high power, they're causing CCI with their neighbours. Turn down the transmit power, and if necessary, reduce the number of APs per channel in a given area.

Question three: We enabled QoS on the wireless side, but helpdesk tickets about call quality haven't reduced.

Answer: Almost certainly a wired trust boundary issue. Check your switch port configurations for the ports connecting to your APs and WLC. Ensure they are set to trust DSCP markings rather than re-marking to Best Effort.

To summarise the key takeaways from today's briefing.

First, target latency below fifty milliseconds and jitter below twenty milliseconds for voice and video applications. These are your benchmarks.

Second, Co-Channel Interference is the primary RF cause of latency. Migrate critical traffic to five gigahertz and tune your power levels.

Third, disable legacy data rates. Anything below twelve megabits per second on five gigahertz should be disabled in most enterprise deployments.

Fourth, implement end-to-end QoS. WMM on the wireless side, DSCP trust on the wired side. Both are required.

Fifth, enable 802.11r, 802.11k, and 802.11v to eliminate roaming-induced latency and jitter.

Fixing high latency and jitter isn't about buying more expensive hardware. It's about tuning what you have correctly. The investment in getting this right yields significant returns in operational efficiency, reduced helpdesk burden, and improved staff productivity.

Thank you for joining this Purple Technical Briefing. For more detailed implementation guides and WiFi analytics capabilities, visit purple.ai.

Key Takeaways

✓Target one-way latency below 50ms and jitter below 20ms for enterprise voice and video — these are your go/no-go thresholds.
✓Co-Channel Interference is the primary RF cause of high latency in dense deployments; migrate critical traffic to 5GHz and tune AP transmit power down.
✓Disable legacy data rates (below 12 Mbps on 5GHz) to reduce airtime consumption and improve latency for all clients on an AP.
✓QoS must be end-to-end: WMM on the wireless side and DSCP trust on all wired switch ports — one without the other is ineffective.
✓Enable 802.11r, 802.11k, and 802.11v together to eliminate roaming-induced call dropouts for mobile staff.
✓Sticky clients degrade performance for themselves and their AP neighbours; configure RSSI-based disassociation thresholds on the WLC.
✓Establish baseline latency and jitter measurements and monitor continuously — proactive alerting on channel utilisation above 50% prevents reactive firefighting.

Executive Summary

For enterprise venues — from expansive retail floors to high-density stadiums and hospitality properties — staff WiFi performance is a critical operational dependency, not merely an amenity. When one-way latency exceeds 50ms or jitter climbs past 20ms, the performance of real-time communication platforms, including Microsoft Teams and Zoom, visibly degrades: audio becomes robotic, video freezes, and calls drop. This guide provides network architects and IT directors with the technical depth and actionable strategies required to identify, diagnose, and resolve the root causes of high latency WiFi on corporate WLANs. By addressing RF interference, implementing end-to-end Quality of Service, and tuning roaming parameters to align with IEEE 802.11r/k/v, organisations can deliver a robust wireless experience that supports seamless staff mobility. This investment is directly measurable: fewer helpdesk tickets, improved operational throughput, and a network infrastructure that scales with the business.

Technical Deep Dive

Latency and Jitter: The Key Differences

Latency is the time required for a data packet to travel from source to destination. Jitter is the variance in that delay between consecutive packets. In the context of 802.11 networks, both metrics are heavily influenced by the half-duplex nature of wireless transmission and the Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) protocol — the mechanism by which devices compete for airtime.

Voice and video codecs are designed with fixed jitter buffers. When jitter exceeds the buffer depth — typically 20-30ms for enterprise-grade VoIP — packets are discarded, producing the distinctive choppy or robotic audio that signals a degraded call. Conversely, high latency causes conversational overlaps that make real-time collaboration difficult. The ITU-T G.114 recommendation specifies a maximum 150ms one-way delay for acceptable voice quality, with enterprise deployments targetting 50ms.

Metric	Optimal	Acceptable	Degraded
One-Way Latency	< 20ms	20–50ms	> 50ms
Jitter	< 5ms	5–20ms	> 20ms
Packet Loss	< 0.1%	0.1–1%	> 1%

Root Cause 1: RF Environment and Co-Channel Interference

Co-channel interference (CCI) is the primary RF cause of increased latency in dense enterprise deployments. When multiple access points (APs) operate on the same channel, they share airtime under CSMA/CA. Each AP must defer transmission until it detects that another AP on the same channel has finished transmitting, effectively serialising traffic and increasing queuing delay. In a retail store with 20 APs on three non-overlapping 2.4GHz channels, each channel may be shared by six or seven APs — a configuration that will introduce significant latency under load.

The 5GHz band, with its wider channel plan (up to 25 non-overlapping 20MHz channels under 802.11ac/ax in many regulatory domains), offers significantly higher capacity for channel reuse planning. Understanding the full frequency landscape is essential; the guide Wi Fi Frequencies: A Guide to Wi-Fi Frequencies in 2026 provides a comprehensive reference for frequency planning decisions.

Adjacent Channel Interference (ACI) presents a secondary risk. ACI occurs when channels are not sufficiently separated, causing partial overlap that corrupts frames and forces retransmissions — each retransmission directly increasing observed latency.

Root Cause 2: Legacy Data Rates and Airtime Inefficiency

In a standard 802.11 BSS, all associated clients are allocated transmission opportunities. A client transmitting at 1 Mbps occupies the channel for nearly 100 times longer than a client transmitting at 100 Mbps to send the same payload. This unequal airtime consumption — caused by legacy devices or clients at the edge of coverage — increases queuing delay for all other clients on the AP. Disabling data rates below 12 Mbps on the 5GHz band and below 5.5 Mbps on 2.4GHz forces clients to use more efficient modulation, reducing per-frame airtime and improving overall latency.

Root Cause 3: QoS Misconfiguration

Without Quality of Service, a bulk file transfer is treated exactly like a Teams call. Wi-Fi Multimedia (WMM), which is the 802.11e QoS implementation, defines four access categories: Voice (AC_VO), Video (AC_VI), Best Effort (AC_BE), and Background (AC_BK). Each category has different contention window parameters that determine how aggressively it competes for airtime. Voice traffic uses a smaller contention window and shorter Arbitration Inter-Frame Space (AIFS), giving it statistical priority over bulk data.

A critical implementation detail that many deployments overlook is the trust boundary on the wired infrastructure. WMM operates at Layer 2 within the wireless domain. To maintain QoS end-to-end, the switch ports connecting APs and wireless LAN controllers must be configured to trust the DSCP markings applied by the wireless infrastructure. Without this, packets are reclassified to Best Effort at the first wired hop, rendering the wireless QoS configuration ineffective beyond the AP.

For healthcare environments where clinical communication over VoWLAN is safety-critical, this end-to-end QoS chain is non-negotiable.

Root Cause 4: Roaming Latency and Authentication Overhead

In mobile staff environments, the most operationally disruptive cause of call quality degradation is roaming-induced latency. When a client transitions between APs, the process includes: active or passive scanning to discover potential APs, authentication, and re-association. Under WPA3-Enterprise with 802.1X, the authentication phase requires a full RADIUS exchange, which can take 300-800ms depending on RADIUS server response times and network topology. This delay is directly experienced as call dropouts.

IEEE 802.11r (Fast BSS Transition) resolves this by allowing the client to pre-negotiate the Pairwise Transient Key with the target AP prior to roaming, utilising cached PMK-R1 keys distributed by the WLC. This reduces the authentication phase to a two-frame exchange, bringing total roaming time down to under 50ms. For environments with significant staff mobility — transport hubs, hospital wards, warehouse floors — 802.11r is not optional; it is a baseline requirement.

IEEE 802.11k (Neighbourhood Report) provides clients with a Neighbour Report, eliminating the need to scan every possible channel to discover potential APs. IEEE 802.11v (BSS Transition Management) allows the network to actively suggest better APs to clients, resolving the sticky client issue. For a comprehensive breakdown of roaming architectures, see Resolving Roaming Issues in Corporate WLANs .

Implementation Guide

Step 1: RF Audit and Channel Planning

Begin with a comprehensive wireless site survey utilising a spectrum analyser to identify sources of interference, including non-WiFi sources such as Bluetooth, DECT phones, and microwave ovens. Document AP placement, transmit power levels, and channel assignments. Identify APs with consistent channel utilisation exceeding 50% — these are your primary latency hotspots. Reduce AP transmit power to the minimum level required to maintain adequate coverage (-67 dBm RSSI at cell edge for voice applications). This reduces the CCI footprint of each AP, allowing for denser channel reuse. Enable automatic RF management on the WLC, but configure time restrictions to prevent channel changes during business hours, which can cause brief connectivity disruptions.

Step 2: Data Rate Optimisation

On the 5GHz band, disable all mandatory and supported rates below 12 Mbps. On the 2.4GHz band, disable rates below 5.5 Mbps. This forces clients to associate at higher rates, reducing per-frame airtime consumption. Enable Airtime Fairness to prevent any single client from monopolising the channel.

Step 3: End-to-End QoS Implementation

Enable WMM on all corporate SSIDs. Configure DSCP-to-WMM mapping: DSCP EF (46) to AC_VO, DSCP AF41 (34) to AC_VI. On the wired infrastructure, configure switch ports connecting APs and WLCs with mls qos trust dscp (Cisco IOS syntax) or equivalent. Verify the QoS chain using packet captures on the WAN router to confirm that voice traffic is arriving with the correct DSCP markings.

Use Guest WiFi to identify bandwidth-intensive applications consuming disproportionate airtime, and apply rate limiting or traffic shaping policies to protect voice and video traffic.

Step 4: Roaming Optimisation

Enable 802.11r, 802.11k, and 802.11v on the staff SSID. Note that some legacy clients may not support these standards; test thoroughly before deployment. To resolve sticky clients, configure the WLC to disconnect clients with RSSI below -75 dBm. Set the minimum RSSI threshold for association to -80 dBm to prevent clients from connecting to distant APs.

Best Practices

Security and Performance: Deploy WPA3-Enterprise with 802.1X for the staff SSID. Although 802.1X introduces initial authentication overhead, 802.11r eliminates this during roaming. Ensure RADIUS servers are deployed with redundancy and sub-100ms response times. Compliance with GDPR and PCI DSS necessitates that staff and Guest WiFi traffic be logically segregated using VLANs and separate SSIDs.

Network Segmentation: Maintain strict separation between staff and guest networks. Guest traffic should be isolated on a dedicated SSID with Captive Portal authentication, ensuring guest devices do not impact staff network performance. This is particularly relevant for Hospitality properties where guest WiFi density can be extremely high.

Monitoring and Baselining: Establish baseline latency and jitter measurements during off-peak hours. Configure SNMP traps or streaming telemetry to alert when channel utilisation exceeds 50% or client RSSI drops below -70 dBm. Proactive monitoring prevents reactive troubleshooting.

For a comprehensive workplace connectivity strategy, Office Wi Fi: Optimize Your Modern Office Wi-Fi Network provides complementary guidance on enterprise WLAN design.

Troubleshooting and Risk Mitigation

Follow a structured diagnostic approach to avoid misdiagnosing the root cause:

Isolate the Domain: Ping the local default gateway from an affected client. If latency is low, the wireless network is performing adequately and the issue lies in the wired or WAN domain. If latency is high, proceed with wireless diagnostics.
Examine Channel Utilisation: High utilisation (>50%) indicates CCI or capacity constraints. Low utilisation paired with high latency points to QoS or roaming issues.
Review Client Association: Identify clients associated at low data rates or with weak RSSI. These are likely causing airtime inefficiency or experiencing poor coverage.
Validate End-to-End QoS: Capture packets at the WAN interface and verify DSCP markings on voice traffic.
Test Roaming: Use a WiFi diagnostic tool to measure roaming transition times. Anything above 100ms indicates 802.11r is not functioning correctly.

Common Failure Modes:

Symptom	Potential Cause	Resolution
Latency spikes during peak hours	CCI / High channel utilisation	Reduce AP power, migrate to 5GHz
Audio dropouts while moving	Slow roaming / Lack of 802.11r	Enable 802.11r, tune RSSI thresholds
Constant high latency, low utilisation	Missing QoS trust boundary	Configure DSCP trust on switch ports
Intermittent packet loss	ACI / Channel overlap	Rectify channel plan, increase channel separation

ROI and Business Impact

The business case for WiFi latency optimisation is straightforward. In a warehouse or logistics operation, reducing scanner latency from 150ms to under 20ms can increase pick-and-pack throughput by 10-15%, directly impacting operating costs. In a corporate environment, eliminating dropped Teams calls reduces IT helpdesk tickets — which typically cost £25-£50 per ticket to resolve — and improves executive and employee productivity.

For Healthcare organisations deploying VoWLAN for clinical communication, the value of risk mitigation is even higher: unreliable communication in a clinical setting creates patient safety implications against which the cost of network optimisation is negligible.

Measure success based on these KPIs: average one-way latency for voice traffic, jitter measurements, roaming transition times, channel utilisation percentage, and the number of helpdesk tickets related to WiFi performance. Establish pre- and post-optimisation baselines to measure improvement and build the business case for ongoing investment.

Key Definitions

Latency

The one-way time delay for a data packet to travel from source to destination, measured in milliseconds.

High latency causes conversational delay in voice calls and video conferencing. The ITU-T G.114 standard specifies a maximum acceptable one-way latency of 150ms, with 50ms as the enterprise target.

Jitter

The statistical variation in packet arrival times, representing the inconsistency of latency across a stream of packets.

High jitter causes choppy or robotic audio as the receiving application's jitter buffer is overwhelmed and packets are discarded. Target jitter below 20ms for enterprise voice applications.

CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance)

The medium access protocol used in 802.11 WiFi networks, where devices listen for channel activity before transmitting and back off randomly if the channel is busy.

The half-duplex nature of CSMA/CA means only one device can transmit at a time on a given channel. In dense environments, this contention mechanism is the primary source of variable latency.

Co-Channel Interference (CCI)

Interference caused when multiple Access Points or clients transmit on the same frequency channel within range of each other.

CCI forces APs to defer transmission, increasing queuing delay. It is the primary RF cause of high latency in dense enterprise deployments and is mitigated through careful channel planning and power management.

WMM (Wi-Fi Multimedia)

The 802.11e QoS implementation for wireless networks, defining four Access Categories (Voice, Video, Best Effort, Background) with differentiated contention parameters.

WMM is the mechanism that gives voice and video traffic statistical priority over bulk data on the wireless medium. It must be enabled on all SSIDs carrying real-time traffic.

802.11r (Fast BSS Transition)

An IEEE standard that allows a client to pre-negotiate security credentials with a target AP before roaming, eliminating the need for a full RADIUS re-authentication during the handoff.

Without 802.11r, roaming under WPA2/WPA3-Enterprise can take 300–800ms, causing audible call dropouts. With 802.11r, roaming completes in under 50ms.

Sticky Client

A wireless device that remains associated to an AP with a degraded signal, even when a closer AP with a stronger signal is available.

Sticky clients experience high latency due to poor signal quality and consume disproportionate airtime at low data rates. WLC-side RSSI threshold enforcement is required to force these clients to roam.

Airtime Fairness

A wireless scheduling mechanism that allocates equal transmission time to all associated clients, rather than equal numbers of transmission opportunities.

Without airtime fairness, a single slow client can monopolise the channel, increasing latency for all other clients on the AP. Enabling airtime fairness protects high-speed clients from the impact of legacy or distant devices.

DSCP (Differentiated Services Code Point)

A 6-bit field in the IP header used to classify and prioritise network traffic for QoS purposes.

DSCP EF (46) is used for voice traffic; DSCP AF41 (34) for video. These markings must be trusted by wired switches to maintain QoS end-to-end from the wireless client to the WAN.

Worked Examples

A 1,200-delegate conference centre reports that staff using mobile devices experience dropped Zoom calls when moving between exhibition halls. Signal strength is consistently above -65 dBm throughout the venue, and the wireless controller shows no obvious errors. The issue is intermittent and correlates with staff movement.

A wireless packet capture during a roaming event revealed that clients were taking 480–650ms to complete the roaming process due to full 802.1X re-authentication with the RADIUS server at each AP transition. The RADIUS server was located off-site, adding approximately 80ms of round-trip WAN latency to each authentication exchange.

The resolution involved three steps: First, enable 802.11r (Fast BSS Transition) on the staff SSID to eliminate full RADIUS re-authentication during roams. Second, deploy a local RADIUS proxy or cache to reduce authentication latency for initial associations. Third, enable 802.11k to provide clients with neighbour reports, reducing the scanning phase from 200ms+ to under 30ms. Post-implementation roaming times measured at 35–45ms, eliminating all call dropouts during staff movement.

Examiner's Commentary: This case illustrates that strong RSSI does not guarantee low roaming latency. The root cause was authentication overhead, not RF quality. The 802.11r implementation is the primary fix; the RADIUS proxy addresses the initial association latency. 802.11k is a complementary optimisation that accelerates the discovery phase. Note that 802.11r requires testing with all client device types in the environment, as some older devices may not support it and may require a separate SSID or VLAN.

A national retail chain with 85 stores reports that inventory management scanners on the warehouse floor experience severe latency (150–200ms) during peak trading hours, despite a recent AP hardware refresh. Signal strength is strong, and the WLC dashboard shows no alarms. The issue is worst between 10am and 2pm.

Analysis of the WLC RF dashboard revealed channel utilisation on the 2.4GHz band exceeding 75% during peak hours. The store had 18 APs deployed, all operating on the 2.4GHz band across channels 1, 6, and 11 — meaning six APs per channel were competing for airtime. Additionally, the scanner devices were legacy 802.11n devices operating at data rates as low as 6 Mbps.

The remediation plan: Migrate the scanner SSID exclusively to the 5GHz band, leveraging the wider channel plan to reduce co-channel contention. Disable data rates below 12 Mbps on the 5GHz SSID. Enable WMM and configure the scanner traffic (UDP, port 9100) to be marked as DSCP AF41 (Video class) at the WLC. Configure switch ports to trust DSCP. Post-implementation latency measured at 8–12ms during peak hours.

Examiner's Commentary: The peak-hours correlation is a strong indicator of a capacity or interference problem rather than a coverage problem. The 2.4GHz band with only three non-overlapping channels is fundamentally unsuitable for dense deployments. The 5GHz migration is the architectural fix; the QoS configuration ensures scanner traffic is protected even under load. Disabling low data rates is a quick win that immediately reduces airtime consumption.

Practice Questions

Q1. You are the network architect for a 450-bed hospital deploying VoWLAN handsets for clinical staff across three floors. During UAT, nurses report that calls drop for approximately half a second when moving between wards. Signal strength throughout the building is consistently -62 to -68 dBm. The WLC shows no errors and channel utilisation is below 35%. What is the most likely root cause and what is your recommended resolution?

Hint: Consider what happens at the network layer when a client moves from one AP to another under WPA2-Enterprise authentication. Signal strength and channel utilisation are both healthy, so the issue is not RF-related.

View model answer

The root cause is roaming latency caused by full 802.1X re-authentication at each AP transition. With healthy RSSI and low channel utilisation, the RF environment is not the issue. The half-second dropout is characteristic of a RADIUS authentication exchange occurring during the roam. The recommended resolution is to enable IEEE 802.11r (Fast BSS Transition) on the VoWLAN SSID, which pre-negotiates the PMK-R1 key with the target AP before the roam occurs, reducing transition time to under 50ms. Additionally, enable 802.11k to provide clients with neighbour reports and reduce scanning time, and verify that the RADIUS server response time is below 100ms. Test all handset models for 802.11r compatibility before full deployment.

Q2. A large retail distribution centre has 40 APs deployed across a 20,000 sq ft warehouse floor, all operating on the 2.4GHz band using channels 1, 6, and 11. Barcode scanners used by warehouse operatives are experiencing 120–180ms latency during peak shift hours, causing the inventory management system to time out. Signal strength is strong throughout. What is the primary architectural problem and what is the remediation strategy?

Hint: Calculate how many APs are sharing each channel. Consider the fundamental limitation of the 2.4GHz band in terms of non-overlapping channel availability.

View model answer

The primary problem is severe Co-Channel Interference (CCI). With 40 APs sharing only three non-overlapping channels, approximately 13–14 APs are competing for airtime on each channel. Under CSMA/CA, this creates extreme contention and queuing delay, producing the observed 120–180ms latency. The remediation strategy is: (1) Migrate the scanner SSID exclusively to the 5GHz band, which provides up to 25 non-overlapping 20MHz channels in most regulatory domains, dramatically reducing per-channel AP density. (2) Disable data rates below 12 Mbps to reduce per-frame airtime consumption. (3) Enable WMM and mark scanner UDP traffic as DSCP AF41 to protect it from bulk data traffic. (4) Configure switch ports to trust DSCP markings. (5) Reduce AP transmit power to minimise the CCI footprint of each AP.

Q3. Your network team has implemented WMM on all corporate SSIDs and configured DSCP EF markings for Teams voice traffic at the wireless controller. However, a packet capture taken at the WAN firewall shows Teams voice traffic arriving with DSCP 0 (Best Effort). Helpdesk tickets for call quality issues have not reduced. What has been missed and how do you resolve it?

Hint: QoS is only effective if it is maintained end-to-end. Consider what happens to DSCP markings as packets traverse the wired network infrastructure between the AP and the WAN firewall.

View model answer

The wired network infrastructure is not configured to trust the DSCP markings applied by the wireless controller. When packets leave the AP and traverse the access layer switches, the switch ports are re-marking all traffic to DSCP 0 (Best Effort) because they are not configured to trust incoming DSCP values. The resolution is to configure all switch ports connecting to APs and the WLC with DSCP trust (e.g., 'mls qos trust dscp' in Cisco iOS, or equivalent in other vendor platforms). Additionally, verify that distribution and core layer switches are configured to honour DSCP markings in their QoS policies. After implementing the trust boundary configuration, re-capture at the WAN firewall to confirm that Teams voice traffic is now arriving with DSCP EF (46).

Continue reading in this series

Understanding RSSI and Signal Strength for Optimal Channel Planning

This guide provides a comprehensive technical deep-dive into RSSI, Signal-to-Noise Ratio (SNR), and RF propagation principles for optimal channel planning. It equips IT managers, network architects, and venue operations directors with actionable strategies to mitigate Co-Channel and Adjacent Channel Interference, optimise AP placement, and leverage analytics for measurable business impact across hospitality, retail, and public-sector environments.

Understanding RSSI and Signal Strength for Optimal Channel Planning

20MHz vs 40MHz vs 80MHz: Which Channel Width Should You Use?

This guide provides a definitive, vendor-neutral technical reference for IT managers, network architects, and venue operations directors on selecting the correct WiFi channel width — 20MHz, 40MHz, or 80MHz — across enterprise deployments in hospitality, retail, events, and public-sector environments. It covers the underlying IEEE 802.11 mechanics, real-world capacity trade-offs, and step-by-step deployment guidance to help teams make the right call this quarter. Understanding channel width selection is one of the highest-leverage decisions in any wireless LAN design, directly impacting throughput, interference, client density support, and the reliability of guest-facing services.