A phone drops off a store WLAN and the client detail says the phone initiated the disconnect. The signal was strong and the channel was quiet. What should the engineer treat as the lead?
Select an answer to reveal the explanation.
Short Explanation
The record says the phone hung up, and the channel was quiet. Follow your client before you retune a clean radio. A disconnect the phone started is not an empty address pool.
Full Explanation
The disconnect reason separates a client that walked away, slept, or toggled Wi-Fi from an access point that kicked it. This detail says the phone initiated the disconnect, and the signal was strong on a quiet channel, so the lead is the phone. The channel did not force it off. A client-initiated reason is not an authentication failure, so the RADIUS server is not the first stop. DHCP exhaustion prevents an address. It does not label a later disconnect as client-initiated, and this phone was already on the WLAN. The client detail says the client initiated the disconnect. The channel is not the first place to look. The device left on its own. Check one live client after the change and do not retune the rest of the floor until that client matches the result you expected. Exam caveat: a phone that leaves because a driver crashed still shows a client-initiated reason. The reason picks the next question. It does not name the bug. Operational check: reproduce with the same phone, watch whether the user or the device tears the session down, and leave the quiet channel alone unless the reason changes.