My Oracle Support Banner

DCA Integer AVP Values Stored and Used as Hexadecimal Strings in ACS (Doc ID 2920331.1)

Last updated on JANUARY 12, 2023

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.


On all versions of Oracle Communications Convergent Charging Controller (OC3C or 3C) and Oracle Communications Network Charging and Control (OCNCC or NCC), Attribute Value Pairs (AVPs) received in Credit Control Request (CCR) messages by the Diameter Control Agent (DCA) as integers get stored and treated as a hexadecimal string (ie. 10 vs "0x0A") in Advanced Control Services (ACS).

As a result, attempts to use the numerical value of the stored value fail.

For example, the CC-Time AVP received by DCA, is, by default, stored in the "Extension Digits 5" profile tag (which is of type octet string) as a hexadecimal string.  If trying to pass this value through to Diameter Charging Driver (DCD), the following can be seen if debug is enabled:

No error is through as ACS is not aware that it has failed to convert 0x7B to 123d (and sets the number to 0 instead).


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.