7921g will not associate

Answered Question
Jul 14th, 2008

Hi, I have a 7921g with 1.0.6 phone load and cannot get it to associate to two access points.

One is an Apple Airport Extreme (802.11g version). I've turned encryption off and left the network open. I've tested connections to it using a wireless computer and it all works fine. The phone comes up with a "Connection failed" message, I've enabled logging on the phone and it states:

1980-01-01 00:14:51:0370 CP-7921G user.info wlanmgr: Final active scan in channel 6

1980-01-01 00:14:51:0390 CP-7921G user.notice wlanmgr: Scan Complete Event

1980-01-01 00:14:51:0400 CP-7921G user.notice wlanmgr: We have 1 bssids

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: bssid00:0A:95:F3:A4:B7 rssi=-38 chan=6 adconvoice

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_request:61: Processing WLAN security request

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_request:66: SSID = adconvoice

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_request:116: WLAN_SECURITY_MODE_OPEN_WITHOUT_WEP

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:619: Dumping auth_record....

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:620: authMode = 0

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:621: eapType = -1

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:622: keyType = 0

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:623: encryptType = 0

1980-01-01 00:14:51:0400 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:624: ccxConfig = 0

1980-01-01 00:14:51:0410 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:625: ccxNetworkEap = 0

1980-01-01 00:14:51:0410 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:626: UserName =

1980-01-01 00:14:51:0410 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:627: Password = <hidden text>

1980-01-01 00:14:51:0410 CP-7921G user.info wlanmgr: wlan_security_dump_auth_record:628: WPA_PSK passPhrase: <hidden text>

1980-01-01 00:14:51:0420 CP-7921G user.info wlanmgr: wlan_security_request:456: Setting the Supplicant parameters

1980-01-01 00:14:51:0420 CP-7921G user.info wlanmgr: wlan_security_request:460: WLAN security request result = 0

1980-01-01 00:14:51:0420 CP-7921G user.info wlanmgr: Enabling 802.11d and 802.11h

1980-01-01 00:14:51:0420 CP-7921G user.warn wlanmgr: AP is rejected 9

1980-01-01 00:14:51:0420 CP-7921G user.info wlanmgr: Disabling 802.11d and 802.11h

1980-01-01 00:14:51:0430 CP-7921G user.warn wlanmgr: Failure to associate

The second AP I've tried to associate with is the built-in 802.11g wireless in the UC520. I get an "Authentication failed" with this one even though I've made it open as well.

The log message from the phone for this attempt is:

1980-01-01 00:14:51:0310 CP-7921G user.info wlanmgr: Final active scan in channel 2

1980-01-01 00:14:51:0340 CP-7921G user.notice wlanmgr: Scan Complete Event

1980-01-01 00:14:51:0340 CP-7921G user.notice wlanmgr: We have 1 bssids

1980-01-01 00:14:51:0340 CP-7921G user.info wlanmgr: bssid 00:1E:BE:F2:63:A0 rssi=-42 chan=2 speaktome

1980-01-01 00:14:51:0340 CP-7921G user.info wlanmgr: wlan_security_request:61: Processing WLAN security request

1980-01-01 00:14:51:0340 CP-7921G user.info wlanmgr: wlan_security_request:66: SSID = speaktome

1980-01-01 00:14:51:0340 CP-7921G user.info wlanmgr: wlan_security_request:90: AP has encryption enabled unexpectedly !

1980-01-01 00:14:51:0340 CP-7921G user.info wlanmgr: Disabling 802.11d and 802.11h

1980-01-01 00:14:51:0360 CP-7921G user.warn wlanmgr: Authentication Failed

thanks.

I have this problem too.
0 votes
Correct Answer by migilles about 8 years 4 months ago

There is no 1.0(6) build, so this means you have the mfg load still on the phone. Recommend to load the 1.1(1) release.

http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser-crypto

From the log, looks like you have open authentication enabled without WEP enabled, but appears your AP may have encryption enabled.

If using open + wep, then choose that option on the 7921G and enter the WEP key info.

Also not sure if you have a -W model 7921G phone or not, but per your info, you are located in Australia, so -W would be the model that you would order. If so, then 802.11d (world mode) must be enabled on the AP. Not sure if the Airport supports this, but the UC520 does.

Enter "world-mode dot11d country AU both".

This is documented in the 7921G Deployment Guide @ http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
migilles Tue, 07/15/2008 - 12:08

There is no 1.0(6) build, so this means you have the mfg load still on the phone. Recommend to load the 1.1(1) release.

http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser-crypto

From the log, looks like you have open authentication enabled without WEP enabled, but appears your AP may have encryption enabled.

If using open + wep, then choose that option on the 7921G and enter the WEP key info.

Also not sure if you have a -W model 7921G phone or not, but per your info, you are located in Australia, so -W would be the model that you would order. If so, then 802.11d (world mode) must be enabled on the AP. Not sure if the Airport supports this, but the UC520 does.

Enter "world-mode dot11d country AU both".

This is documented in the 7921G Deployment Guide @ http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf.

Damian Halloran Wed, 07/16/2008 - 20:10

Thanks for the response.

Was able to do the firmware upgrade no problem, and this fixed the issue with connecting to the UC520.

But the Apple connection is still not working which may be due to the lack of support of 802.11d on the base station. I've tried the handset with two different Apple base stations of the same era so you must be right since the error is exactly the same for both.

Thanks again for your assistance.

Actions

This Discussion