My Oracle Support Banner

ACS Change CDR Node Fails to Handle Negative Diameter Exponent Values (Doc ID 2234989.1)

Last updated on MARCH 12, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.0 to 6.0.0 [Release 6.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 6.0.0 [Release 6.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), the value retrieved from a Profile Tag for a stored Attribute Value Pair (AVP) is wrong.  The value retrieved is "AVP-Exponent=4294967295" while the the expected value is "AVP-Exponent=-1".

The AVP value is received by Diameter Charging Driver (DCD) application from an external Billing Engine (BE) and is stored in a Profile Tag (AVP-Exponent in this case) for future use.

DCD allows the Service Logic Controllers (SLCs) to interact with a BE over the Diameter protocol.

AVP definitions are configured in /IN/service_packages/eserv.config file, in the AVPs section.

In this case, the custom AVP is defined like this:

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
Cause
Solution
References


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