01-29-2014 04:00 AM - edited 08-29-2017 06:22 AM
In this document Cisco TAC engineer "Michael Combs" has explained about issue - 7925G handsets failing Association to AP due to Association Status code 201 and Reason: 'Call failed: TSPEC QOS Policy does not match'
7925g issues - Phones are not able to register to CUCM
5500 Series Wireless LAN Controller (AIR-CT5508)
WLAN with Cisco Unified Wireless IP Phones
Configuration Assistance
AIR-CT5508-50-K9 // upgraded firmware for phones and wireless controller will not accept phone registrations
Debug on the WLC showed that the 7925G was failing association as the AP was returning an Association status code of 201.
This is due to a TSPEC request from the handset being refused due to the WLAN configuration. The WLAN the 7925G was attempting to connect to was configured with a QoS profile of Silver (UP 0,3), rather than Platinum (UP 6,7) as required. This lead to a TSPEC mismatch for voice traffic/action frame exchange from the handset via the WLAN, and ultimately a rejection from the AP.
Create a new WLAN with a QoS profile of Platinum specifically for the 7925G handsets and configured as per established best practices, and as defined in the 7925G deployment guide:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7925g/7_0/english/deployment/guide/7925dply.pdf
Once configured, the issue should be resolved.
==Trap==
Thu xxx 16 xx:05:44 20xx VoIP Call Failure: '1x:xx:1x:xx:xx:xx' client, detected by 'xx-xx-xx' AP on radio type '802.11a'. Reason: 'Call failed: TSPEC QOS Policy does not match'.
==debug client <mac>==
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Adding mobile on LWAPP AP 3x:xx:cx:9x:x0:x0(0)
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Association received from mobile on AP 3x:xx:cx:9x:x0:x0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID xxx) ===> 'none' (ACL ID xxx) --- (caller apf_policy.c:1x09)
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID xxx5) ===> 'none' (ACL ID xxx) --- (caller apf_policy.c:18x6)
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Applying site-specific Local Bridging override for station 1x:xx:1x:xx:xx:xx - vapId 1, site 'default-group', interface 'xwirex'
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Applying Local Bridging Interface Policy for station 1x:xx:1x:xx:xx:xx - vlan 510, interface id 12, interface 'xwirex'
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx processSsidIE statusCode is 0 and status is 0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx processSsidIE ssid_done_flag is 0 finish_flag is 0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx STA - rates (4): 130 132 139 150 0 0 0 0 0 0 0 0 0 0 0 0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx suppRates statusCode is 0 and gotSuppRatesElement is 1
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx STA - rates (12): 130 132 139 150 12 18 24 36 48 72 96 108 0 0 0 0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx extSuppRates statusCode is 0 and gotExtSuppRatesElement is 1
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Processing RSN IE type 48, length 22 for mobile 1x:xx:1x:xx:xx:xx
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx CCKM: Mobile is using CCKM
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Received RSN IE with 0 PMKIDs from mobile 1x:xx:1x:xx:xx:xx
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Setting active key cache index 8 ---> 8
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx unsetting PmkIdValidatedByAp
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Sending Assoc Response to station on BSSID 3x:xx:cx:9x:x0:x0 (status 201) ApVapId 1 Slot 0
*apfMsConnTask_1: xx xx xx:50:xx.xxx: 1x:xx:1x:xx:xx:xx Scheduling deletion of Mobile Station: (callerId: 22) in 3 seconds
VoIP Call Failure: '1x:xx:1x:xx:xx:xx' client, detected by 'xx-xx-xx' AP on radio type '802.11b/g'. Reason: 'Call failed: TSPEC QOS Policy does not match'.
1x:xx PM
Client Excluded: MACAddress:1x:xx:1x:xx:xx:xx Base Radio MAC :3x:xx:cx:9x:x0:x0 Slot: 1 User Name: dwpv\mtl7925 Ip Address: xx.xx.x.xx Reason:802.11 Association failed repeatedly. ReasonCode: 2
Cisco Unified Wireless IP Phone 7925G, 7925G-EX, and 7926G Deployment Guide
Cisco Unified Wireless IP Phone 7925G, 7925G-EX, and 7926G Setup
Cisco Unified Wireless IP Phone 7925G, 7925G-EX, and 7926G Administration Guide - Troubleshooting
Thanks Vinay. We just had a customer run into this issue. I appreciate the write up.
thank you. that resolved my issue as well.
Is this issue isolated to the 5500 series WLC or would it impact the 7500 series as well?
I would guess that it would impact the 7500 series too. It sounds like it's a general requirement going forward.
Hello Vinay, we have someone who's insisting on using a 7925G on our WLAN, and running into this issue.
Are you aware of any considerations with respect to changing the profile from silver to platinum? Are there resource issues to be concerned with?
Ron
Hi All,
I had the same problèm using 7926 on our WLAN (with 5508 WLC) and i turned Quality of Service (QoS) from silver to platinium and evry thing's is good now.
Thank you
Vinay,
How does this affect phones that are associated to a standardized WLAN (data and voice endpoints), but the QoS profile and interface is dynamically assigned via radius (ISE)? In other words, the WLAN QoS is set to Silver, but the authz profile applied via ISE (AAA Override) is Platinum.
Thanks,
Tim
Hi Tim, All,
i have the Issue that the SSID is configured for Platinum and every Client, 7925 including, gets VLAN and QOS Profile from ISE. The Thing is, that if i configure CAC, we see the Message:
VoIP Call Failure: '[MAC]' client, detected by '[AP-Name]' AP on radio type '802.11b/g'. Reason: 'Call failed: TSPEC QOS Policy does not match'.
Since CAC is to configure as a Global Parameter we cannot decide between Voice Handsets and other Clients. Should the QOS Profile set to Silver or Bronze? A separate Voice SSID is not an Option, since the Customer trust in a Single SSID Approach.
Any Idea is Welcome...
BR, Michael
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: