BFT EDR Tag Written to ACS EDRs on Mid-Session DIAMETER_CREDIT_LIMIT_REACHED (4012) Responses
(Doc ID 2551993.1)
Last updated on SEPTEMBER 15, 2020
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 to 22.214.171.124.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 126.96.36.199.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 188.8.131.52, the Billing Failure Treatment (BFT) Event Data Record (EDR) tag is written to the EDR when a mid-session DIAMETER_CREDIT_LIMIT_REACHED (4012) response is received by the Diameter Charging Driver (DCD).
A mid-session DIAMETER_CREDIT_LIMIT_REACHED (4012) is not a BFT case as it is merely caused by the account running out of funds.
Setting the parameter acsCharging.switchConfiguration.addDisconnectOrRelease to true does prevent the BFT tag from being written, but this can alter the call flow for the affected service and it is not recommended without further consideration.
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