A call sounds fine at your desk. You walk toward the stockroom and the other person disappears for a moment. By the time you reach the door, the call has ended. A speed test back at the desk will not explain what happened along that route.
Check the walking path, the phone's connection changes and the call service before changing settings. Roaming is the process of a device moving its WiFi connection between access points, the devices providing wireless coverage. A delayed handoff is one possibility, but so are missing coverage and problems outside the WiFi network.
Find out which connection the call is using
Start with the phone model and call type. A mobile carrier's WiFi calling service is not the same as a business calling app. The phone may also move between WiFi and cellular service, which is a different transition from moving between office access points.
Record whether the problem happens on one phone or several, in one application or all calls, and in one direction along the route. Include the time so a technician can compare the event with network records. Do not capture private conversation content when a simple timing note will do.
Repeat a stationary test at the places where the call breaks up. If it also fails while you stand still there, investigate coverage or local interference before treating it as a handoff problem. If stationary use is stable but walking triggers the failure, the transition deserves closer attention.
Watch what the phone actually does while moving
Ask the technician to observe which access point serves the phone along the route, where it changes and what happens at the interruption. A nearby access point does not guarantee the phone has joined it. Client devices use their own roaming behaviour and supported features.
Use the same route and normal walking pace with a representative device. Test both directions where relevant, because the starting connection can affect the result. Compare an affected phone with another suitable device without assuming they should make identical decisions.
The useful record links the physical location to the connection event. Meeting room doorway, still on reception access point is more actionable than a screenshot taken after the phone recovered. It helps distinguish a gap from a device holding onto a connection too long.
- Phone model, operating system and call application.
- Starting location and access point.
- Walking route, direction and approximate interruption point.
- Access point change or disconnect event near that time.
- Stationary comparison and result after any approved change.
Use roaming features for the clients they support
Some systems provide features that help clients discover alternatives or make a handoff faster. Fast roaming, commonly associated with the 802.11r standard, can reduce the authentication work during a supported transition. It does not create coverage where there is none.
Compatibility matters. The access points, network security settings and client devices must support the intended behaviour. A setting that benefits current phones may need testing with older scanners or other business equipment on the same wireless service.
Ask for the change to be tied to the observed fault and tested on the installed versions. Do not enable every advanced wireless option because the names suggest performance. Keep a record of the prior settings and an approved rollback method if essential devices stop connecting.
Make roaming changes during an agreed maintenance window when they could disrupt work. A successful test on one technician's phone is not acceptance for every device the business relies on.
Do not force a handoff into a coverage gap
A minimum signal setting tells an access point when to disconnect a weak client. It can be useful in a designed environment, but disconnecting the phone does not guarantee another access point is available or that the phone will choose it.
If the threshold is wrong, the device may reconnect to the same access point or repeatedly lose service. Manufacturer guidance explicitly warns about this behaviour. Do not copy a signal number from another building and treat it as a universal roaming fix.
Check placement, overlap and interference first. Raising transmit power everywhere can also have unwanted effects, including encouraging a client to remain attached farther away. The plan needs to account for the device's return connection and neighbouring radios, not just a stronger signal displayed on the phone.
A good walking test follows the phone between rooms, not just the signal bars at each desk.Retest the call path and keep the limits clear
After a justified change, repeat the same walking and stationary tests. Check ordinary busy conditions where practical, and confirm other essential devices still work. If the symptom remains, revisit the evidence instead of layering another setting over an unproven diagnosis.
If access point transitions look healthy but carrier WiFi calls still fail, investigate the carrier, handset and wider connection. If only one business calling app is affected, involve its support path. An office wireless change cannot guarantee the behaviour of every outside service.
Keep the accepted routes, devices, settings and remaining limitations in the network record. Recheck when partitions move, new access points are installed or the business changes its phones. Roaming is a property of the working combination, not a permanent promise printed on the access point box.
Plan the next step with NeuroDesk
NeuroDesk's wireless planning accounts for the rooms and routes where people work. Bring the affected phone models, call application and a description of where the interruption occurs. We can scope a walking test rather than judging the installation only from a stationary speed check.
See our business wireless planning for the relevant scope.
Sources and technical scope
The technical references below describe particular equipment and software. Features and limits must be checked against the installed model and configuration; they are not promises for every system.