I have 7921 phones along with 1242 LWAPP APs. I have noticed the phones resist roaming to an AP that is closer (stronger signal). I did some testing on some APs that did not have any other associations. What I found was the phone would cling to the AP that it originally associated with. Even when the signal showed 1 bar on the phone and I was standing 2 feet away from another AP, the phone would not roam. The voice quality was suffering, but the phone would not let go of the distant AP. If I powered off the phone and powered it back on, it would associate to the AP that was 2 feet away. When I walked away, it clung to that AP. Only when the signal was so weak that is was effectively gone, would the phone switch to another AP. I am using WPA-PSK to authenticate the phone. I am running 18.104.22.168 on the controllers. The phone loads are from the latest device pack in CallManager. I have a dedicated voice VLAN defined on the APs. I have WMM Policy, 7920 AP CAC, and 7920 Client CAC all disabled. Does anyone know how to make these phones ?less sticky??
It is my understanding that the phone and the AP negotiate the power setting on the phone. Regardless, I want to phone to roam to a stronger AP when it gets below 2 bars. It will not. It should roam before voice quality suffers. I can hear clipping and the voice will sound fuzzy. I know these phones avoid roaming by design. I just want them to roam more quickly than they do now.
With 5 GHz, must abide by 802.11h and passively scan the DFS channels (UNII-2).
If on call, may not receive the beacon that comes out every 100ms as the phone can not wait that long when on call. When received the phone can probe that channel for the phone's configured network, to see if there are Aps on that channel that have the phone's SSID or not.
We are working on some items to make the phone more agressive in roaming though.
Would suggest opening a TAC case for support assistance.
Some enhancements were made to the roaming mechanism to make it more aggressive which is required in some environments where an aop association can be short lived.
Also a comment on the original post, it showed that WMM and AP CAC were disabled, which means QBSS will not be enabled as well. Should always have WMM enabled per the 7921G Deployment Guide, but some 3rd party APs may not support QBSS, where a fix is available in 1.0(5) that addresses an issue in regards to only roaming on BSS loss when QBSS is not enabled.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...