Integer Profile Fields Are Read Incorrectly
Last updated on JULY 17, 2017
Applies to:Oracle Communications Network Charging and Control - Version 6.0.1 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
Integer profile fields are being interpreted as a four-byte hex string within the control plans.
For example an integer value is found by a APTB(Prefix Tree Branching) feature node and written to integer tag 336 which corresponds to a value of 0x0150 in hexadecimal.
Looking at slee-acs log:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms