Unable to register IP Communicator via Wireless Controller connection
Wireless access via a Cisco Controller works well (i.e. web, mail, IM) except for IP Communicator (220.127.116.11). A protocol trace shows that the TFTP dnload occurs but appears to break when the client SKINNY register request message does not recieve a response from the Call Mgr. TCP retransmissions of the SKINNY register request and keepalives are repeated and results with the "registering" state displayed on the IP Comm display.
This same IP communicator config works well via a wired LAN or remote VPN connections.
Any ideas what the issue might be or where I might look? QoS? TKIP/AES? LWAPP tunnel? I have gone thru the list of caveats but nothing has helped.
Thanks for your help... I'm stuck! -W
Well made some progress today. IP comm with the IntelPRO/Wireless 2915ABG but not with the Broadcom 1350. Anyone else have this issue. I am suspecting the broadcom aes implementation...
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
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 f...