Cisco Bug: CSCup71470 - Not interpreting RZC H6a AVP as a full hexadecimal value
Dec 24, 2016
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: Not interpreting RZC H6a AVP as a full hexadecimal value Conditions: We are testing zone code restriction on the MME, where the zone code for a specific subscriber is received in the ULA from the HSS. From 3GPPTS 23.003, it is indicated that the Zone Code has a fixed length of two octets and is coded in full hexadecimal representation; however, the ASR5K interpretation is actually treating each octet (of the two) separately, converting each to its string value and then concatenating (for example, if 30 32 is received as an RSZC value, then the ASR5K interprets it as a string value '02'). The problem in this interpretation is that the values will be limited to only 100 values (from 00 to 99). Currently if the value sent is 00 FF, ASR5K can not convert it to a numerical string value (given that numerical string value is converted only from 30 to 39 octet values), while 00 FF should be handled as a full hex and thus convert it to 255 as a numeric value. This needs to be checked and fixed as it does not abide with the standard and is a requirement by customers.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases