Incorrect IMEISV Decoding On User-Equipment-Info-Value AVP Values
(Doc ID 3071988.1)
Last updated on MARCH 14, 2025
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
Diameter gateway converts IMEISV hex information to ascii text format such as 0x5364334481593170 incorrectly as below:
User-Equipment-Info (458,M,l=60) =
User-Equipment-Info-Type (459,M,l=12) = IMEISV (0)
User-Equipment-Info-Value (460,M,l=16) = htYP06($
The correct conversion should be:
User-Equipment-Info (458,M,l=60) =
User-Equipment-Info-Type (459,M,l=12) = IMEISV (0)
User-Equipment-Info-Value (460,M,l=16) = 0x5364334481593170
The issue can be reproduced by sending a Seagull usage using the value for example 0x5364334481593170 for User-Equipment-Info-Value AVP.
Changes
Added a new method “isAlphanumeric” to validate whether the string is composed of letters and digits only.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |