5 Key Takeaways
- Roaming thresholds and AP power imbalance are the leading causes of Teams call drops when moving between rooms.
- Shift-change slowdowns often result from authentication surges, DHCP bottlenecks, and physical RF congestion.
- Monitoring core KPIs. roaming delay, SNR, airtime, retries, and application metrics. is essential for wireless health.
- 6 GHz Wi-Fi (6E/7) improves capacity but demands precise coverage planning due to shorter indoor range.
- Accurate diagnosis requires comparing Wi-Fi, WAN, DNS, and infrastructure metrics to pinpoint real performance bottlenecks.
Summary
This guide explains why UK business Wi-Fi suffers from roaming failures, shift-change congestion, and inconsistent performance across 5 GHz and 6 GHz. It outlines essential KPIs. SNR, airtime, retries, and roaming delay. and provides practical diagnostic steps to isolate wireless, WAN, and DNS issues for real-time applications like Teams.
Introduction
Reliable Wi-Fi connectivity is essential for modern UK workplaces that depend on Teams calls, cloud applications, IoT devices, and mobile workflows. Yet issues such as roaming failures, slowdowns during busy periods, and fluctuating performance remain common. This guide explores the underlying causes and the key metrics that define healthy enterprise Wi-Fi.
Why do calls or Microsoft Teams meetings drop when I walk between rooms?
Real-time apps such as Teams, Zoom and VoIP are extremely sensitive to interruptions during roaming. When a user walks between rooms, the device must negotiate a fast handover to the next access point (AP). If roaming is late, slow, or unstable, the session can freeze, distort, or disconnect. In UK offices, warehouses, hospitals and education environments, improper AP placement or misconfigured roaming thresholds are frequent root causes.
Is my device failing to roam quickly enough between access points?
Devices often “stick” to their original AP even after moving far away, a behaviour known as sticky client behaviour.
This happens when:
- Roaming thresholds are too low (e.g., –75 dBm or below).
- APs are spaced too far apart.
- The network lacks 802.11k/v/r fast-roaming support.
- Signal overlap is either too weak (gaps) or too strong (indecision).
As of 2025, most enterprise-grade devices support 802.11k/v, and many support 802.11r, though not all networks enable it by default.
Reference roaming standards: Wi-Fi Alliance – Fast Roaming (802.11r).
Could AP placement or transmit power imbalance be causing call drops?
A frequent cause is transmit power imbalance between APs and client devices. APs often transmit at much higher power, while phones and laptops typically transmit at only 15–18 dBm.
When APs are too “loud”:
- Clients attach prematurely.
- Devices roam too late.
- Throughput drops as devices cling to weak connections.
- Packet loss spikes during transitions.
Balancing AP power levels and ensuring appropriate overlap significantly reduces roaming instability. A detailed assessment can highlight mismatches. Many UK organisations use structured RF mapping.
Are Teams calls sensitive to packet loss and jitter during roaming?
Yes. Microsoft Teams specifies the following baseline requirements for stable real-time calls:
| Metric | Recommended Threshold | Why It Matters |
| Latency | <150 ms | Reduces noticeable voice delay |
| Jitter | <30 ms | Minimises distortion/robotic audio |
| Packet Loss | Ideally <1% (short bursts up to ~5% tolerated) | Sustained >1% affects call clarity |
| Roaming Delay | <150 ms | Prevents freeze during AP handover |
| Minimum RSSI | >–67 dBm | Required for HD audio/video |
Even a 100 ms roam interruption can momentarily freeze a session. Large campuses often experience jitter bursts when users pass through congested zones during movement.
How do 5 GHz and 6 GHz bands affect roaming reliability?
Wi-Fi 6E and Wi-Fi 7 expand capacity, but also complicate roaming:
- 6 GHz has shorter propagation range (~6–8 dB more loss than 5 GHz indoors).
- More APs are needed for continuous coverage.
- Devices may roam unpredictably if 6 GHz coverage has gaps.
- Band steering may occasionally move a device between 5/6 GHz mid-session depending on chipset behaviour.
- Mixed BYOD environments introduce inconsistent roaming logic across vendors.
Roaming typically works best when transitions occur at a consistent RSSI threshold around –67 dBm. Organisations validate roaming boundaries using periodic wireless health evaluations such as: UK Netcom Wi-Fi Surveys.
What causes random Wi-Fi slowdowns during shift changes or peak movement times?
Shift-change slowdowns are highly predictable in dense environments such as factories, hospitals, warehouses and call centres. Sudden device activity and mass movement often trigger authentication bursts, DHCP congestion, RF absorption, or AP saturation. leading to momentary slowness.
Are too many devices joining the network at the same time?
Large-scale login windows can trigger authentication storms, particularly for 802.1X (EAP) environments.
Symptoms include:
- Long connection times
- Temporary “cannot connect” errors
- 5–20 second waits for authentication
- Controller or RADIUS CPU spikes
Could DHCP or IP pool exhaustion be causing slow or failed connections?
DHCP pool issues frequently appear during shift overlaps.
A /24 (254 usable IPs) is insufficient for 300–400 devices joining simultaneously, leading to:
- “Obtaining IP address” hangs
- IP conflicts
- Multiple DHCP retries
Solutions include:
- Expanding address scopes
- Reducing DHCP lease times
- Segmenting user categories
Is RF congestion occurring due to movement of metal equipment or staff?
During shift changes, moving groups of people absorb RF energy (especially at 2.4 GHz) while machinery and metal objects create dynamic multipath reflections. This causes:
- Temporary interference spikes
- Shifting signal paths
- Increased retries
Warehouses and logistics hubs are especially susceptible to these effects.
Are IoT devices competing with users at predictable times?
IoT devices such as scanners, sensors, cameras and environmental monitors frequently synchronise data uploads at scheduled intervals.
Patterns include:
- Hourly synchronisation
- End-of-shift data dumps
- Simultaneous telemetry bursts
This behaviour consumes airtime and can create predictable bottlenecks.
Is load balancing or band steering misaligned with actual client behaviour?
Load balancing may push clients onto bands or APs that appear under-utilised but provide weaker real-world performance. Issues include:
- Steering clients onto 6 GHz where coverage isn’t continuous
- Rejecting clients due to aggressive thresholds
- Multiple steering decisions during movement
Many organisations resolve these behaviours by tuning band steering aggressiveness and evaluating per-AP utilisation. Support and diagnostic services are available via:
UK Netcom Wi-Fi Diagnostics.
What KPIs should IT teams track to measure enterprise Wi-Fi health accurately?
Effective Wi-Fi troubleshooting requires measurable KPIs across roaming, RF quality, airtime, retries, and application-level performance. Below are the most reliable indicators used across enterprise deployments in 2025.
Which roaming KPIs indicate healthy mobility for voice and video?
Key roaming KPIs:
- Roaming delay <150 ms
- Roam trigger >–67 dBm
- 802.11k/v/r assistance enabled
- Sticky client rate kept minimal
High-performing networks typically achieve ~90–95% successful fast transitions.
What signal and RF quality metrics matter most for stable connectivity?
Essential RF indicators include:
- SNR >25 dB for reliable throughput
- RSSI >–67 dBm for real-time apps
- CCI minimised with thoughtful channel planning
- ACI prevented by using proper channel widths and non-overlapping channels
Signal quality matters far more than signal strength.
How does airtime utilisation predict future congestion?
Airtime is the true limiting resource in Wi-Fi. Thresholds:
- <70% = healthy
- ~80% = growing congestion
- >90% = latency + retransmissions become inevitable
Airtime is consumed by:
- IoT chatter
- Retries/retransmissions
- Legacy 2.4 GHz devices
- Multicast or broadcast traffic
- Dense client presence
Why are packet retries and retransmissions critical indicators?
Retries reveal RF problems more reliably than RSSI.
- <10–15% = normal
- 15–25% = watch for interference
- >30% = severe RF or congestion issues almost guaranteed
High retries correlate closely with user complaints regarding slowness or unstable calls.
How should IT track real-time app KPIs (Teams, Zoom, VoIP)?
Monitor:
- MOS >4.0
- Jitter <30 ms
- Latency <150 ms
- Packet delay variation
These reflect real-world call quality far more accurately than raw Wi-Fi throughput.
What infrastructure KPIs reveal hidden bottlenecks?
Consider:
- AP CPU load (watch for unusual spikes rather than fixed numeric thresholds)
- Controller/gateway throughput
- Switch uplink saturation
- Firewall traffic shaping or DPI bottlenecks
- PoE draw (Wi-Fi 6E/7 APs commonly consume 21–35 W)
How can IT teams isolate whether slowness is caused by Wi-Fi or the wider network?
Some “Wi-Fi problems” are actually WAN or application-layer issues. Comparing local vs external behaviour helps determine the true cause.
Does internal ping behave differently from external ping?
If:
- Internal ping (gateway/AP) is stable
- External ping is unstable
→ the WAN, not Wi-Fi, is at fault.
Could DNS latency be misdiagnosed as Wi-Fi delay?
Slow DNS creates:
- Website hang-on-load
- Delayed Teams sign-in
- “No internet” messages despite good signal
Testing DNS latency independently avoids misdiagnosis.
Is the WAN link saturated during shift changes?
WAN congestion can mimic Wi-Fi issues.
Typical peak-time culprits:
- Teams/Zoom sessions
- Cloud authentication bursts
- File sync
- Backups
- OS updates
Correlating WAN utilisation with Wi-Fi KPIs provides clarity.
What tools and methods help diagnose enterprise Wi-Fi issues quickly?
Modern diagnostics combine spectrum analysis, analytics platforms and periodic RF surveys.
Spectrum analysis exposes non-Wi-Fi interference, including:
- CCTV systems
- microwaves
- Bluetooth scanners
- faulty radios
- wireless audio systems
These devices disrupt Wi-Fi but cannot be seen in standard Wi-Fi dashboards.
How do AI analytics platforms detect repeating patterns?
AI/ML systems automatically identify patterns such as:
- DHCP storms
- periodic interference
- AP hardware faults
- device-specific anomalies
- recurring application issues
Predictive insights reduce time-to-resolution.
When is a full Wi-Fi survey recommended?
A survey is recommended when:
- the building layout changes
- new machinery is installed
- density increases
- Teams Rooms or VoIP systems are added
- roaming gaps or dead zones appear
Surveys validate RF health across all coverage areas.
What KPIs Define a Healthy Enterprise Wi-Fi Network?
| KPI Category | Metric | Recommended Baseline (2025) | Why It Matters |
| Mobility | Roaming Delay | <150 ms | Prevents Teams call drops |
| RF Health | SNR | >25 dB | Supports stable throughput |
| Congestion | Airtime Use | <70% | Avoids saturation |
| Reliability | Retry Rate | <15% | Indicates interference |
| Application | Jitter | <30 ms | Protects real-time media |
| Infrastructure | AP Load | Monitor for unusual spikes | Indicates controller/AP health |
Conclusion
Diagnosing Wi-Fi performance issues requires more than signal checks. it requires understanding roaming behaviour, RF quality, congestion indicators and the KPIs that expose hidden problems. As UK organisations in 2025 rely increasingly on Teams, IoT and mobility, Wi-Fi must be designed, validated and monitored with precision.
A well-optimised network is predictable, measurable, and ready for operational growth. If your organisation is experiencing roaming issues, shift-related slowdowns or unpredictable performance, a structured Wi-Fi health evaluation can provide clarity.
Ready to stabilise your Wi-Fi? Book a professional Wi-Fi site survey with UK Netcom today.
FAQs
How often should an enterprise run a Wi-Fi health check?
Most UK businesses benefit from a Wi-Fi health audit every 6–12 months, especially after layout changes or increased device density.
Do Wi-Fi 6/7 upgrades automatically fix roaming issues?
No. roaming stability still depends on AP placement, power tuning and client capabilities. Standards help, but design matters more.
Why does my Wi-Fi show full bars but still feel slow?
RSSI only shows strength, not quality. Low SNR, interference or saturation can cause slowness despite “full bars”.
What is the most overlooked cause of enterprise Wi-Fi problems?
Transmit power imbalance between APs and clients, which forces devices to roam too late.
Should UK businesses disable 2.4 GHz entirely?
Generally no. Many IoT and legacy devices depend on 2.4 GHz; instead, optimise it and use 5/6 GHz for performance clients.