Control Plan Stops Processing when CIR Received in Mid-call BFT
(Doc ID 2367809.1)
Last updated on MARCH 16, 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 Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), in a mid-call Billing Failure Treatment (BFT) scenario when BFT processing is not allowed, slee_acs sends a Release Call (without a Disconnect Leg) and then, when the Call Information Request (CIR) is received, the call just stops.
No more nodes are processed, and a final call Call Detail Record (CDR) is written just ending on the UATB node:
The expected behavior is to allow normal call processing to continue.
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