Your phone works at your desk, then the call breaks up as you walk towards a meeting room. Adding internet bandwidth may do nothing for that fault. The useful investigation is what happens between the device and the office access points along that route.
This guide focuses on movement-related Wi-Fi interruptions in UAE offices. It complements the Teams call-quality diagnosis guide, which covers the broader question of whether a problem follows a headset, computer, room or network.
Separate a weak room from a failed transition
Start with three comparisons using the same authorised device and application: stationary near the first access point, stationary in the destination room, and moving between them. Repeat in both directions. Note the time, exact location and whether the application recovers on its own.
- If the destination is poor even while stationary, investigate its coverage and capacity first.
- If both endpoints work but the transition fails, collect roaming and authentication evidence.
- If only one device model struggles, compare its software, drivers and supported features.
- If several rooms fail at busy times, widen the investigation beyond movement.
These comparisons narrow the next test; they do not prove a single cause. Keep the device on the approved staff network so the comparison does not accidentally change firewall rules, internet routing or access permissions.
Record which access point the device actually uses
A familiar Wi-Fi name does not tell you which access point serves the device. Ask IT to record the serving AP or BSSID, signal evidence and connection events along the walking route. Mark the interruption on a floor plan and compare it with the time of any AP change.
For a hypothetical office with a reception area and two meeting rooms, the useful evidence might be: “This phone stayed attached to the reception AP at the far room; another model changed AP earlier.” That is a specific observation to investigate, rather than an instruction to turn every radio to maximum power.
ITZ's office Wi-Fi assessment and setup service can review the route, device mix and access-point layout. Request an Office Wi-Fi Roaming Review with the affected rooms and examples of the devices involved.
Do not treat roaming controls as a coverage repair
Ubiquiti's Wi-Fi settings guide distinguishes BSS Transition, which encourages clients towards a better AP, from 802.11r Fast Roaming, which speeds supported handoffs. Compatibility matters, particularly with older devices. A setting that helps a modern phone is not evidence that every scanner or legacy endpoint will behave the same way.
Ubiquiti also warns that Minimum RSSI disconnects clients below the configured threshold. The client must find another AP; without a suitable alternative, repeated disconnections can result. There is no universal threshold to copy into every office.
Ask the engineer to distinguish the proposed change from the symptom it is meant to address. “Improve the usable transition area between these two rooms” is a testable objective. “Enable every advanced option” is not a diagnosis.
Check the path behind each access point
A good wireless signal is only part of the route. Include AP uptime, power, switch ports, uplink errors and the network assigned to the staff Wi-Fi in the investigation. Where APs use wireless uplinks, inspect those links as well. A handoff cannot repair an unreliable connection behind the destination AP.
For an office extension, request a review of cabling and office network configuration alongside radio placement. Have the engineer check that the intended staff network is implemented consistently across the APs. Do not remove guest isolation or security controls simply to make a test appear successful; use the guest network isolation checklist to preserve that boundary.
Run a small, repeatable acceptance test
- Select representative phones, laptops and any mobile scanners used for work.
- Agree walking routes, application tasks and an acceptable interruption level with the team.
- Capture the original behaviour before changing configuration.
- Change one relevant setting or infrastructure element, with a saved rollback configuration.
- Repeat the route in both directions during representative occupancy.
- Check stationary devices and ordinary business access for regressions.
The result should include both the user's experience and the engineer's observations. Record a remaining limitation explicitly: for example, an older scanner may need a different supported design. Avoid claiming that a single successful walk proves uninterrupted service for every device and every busy period.
Request an office Wi-Fi roaming review
Tell ITZ where movement causes interruptions, how many users are affected, which AP brand is installed and whether the issue began after an office or configuration change. Request a review of coverage, transitions and uplink dependencies, followed by a prioritised test and improvement plan.
