AVP Response Value Is Hitting 32 Bits Integer Limit
(Doc ID 2518810.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communications Convergent Charging Controller (OC3C) version 6.0.1, The Diameter Charging Driver (DCD) product provides functionality that allows the Prepaid Charging product to interface with applications using the DIAMETER protocol.
DCD allows the user to configure custom Attribute Value Pair (AVP), used in Diameter to represent properties of a particular request or answer. Those AVP can have the data format as Integer64.
There is an issue when the charging system returns a bucket value too big to fit into a 32 bits integer (2,147,483,647).
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