DisconnectLeg Responses Causes Hung Calls if Mid-Call BFT Event Occurs for Non-VWS Billing Domains
(Doc ID 2360872.1)
Last updated on FEBRUARY 14, 2018
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 to 188.8.131.52.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Convergent Charging Controller (OC3C) and Oracle Communications Network Charging and Control (OCNCC or NCC), under the following conditions:
- Mid-Call Billing Failure Treatment (BFT) has been applied due to an error from a non-Voucher and Wallet Server (VWS) Billing Engine (BE)
- A disconnectLeg Reponse was received from the network confirming the successful release of the B-Leg of a call
The active call will hang due to slee_acs and the Universal Attempt Termination to Pending with Billing (UATB) node expecting a Confirm/Commit Reservation (CR) Response from the BE which never arrives (as no CR Request was ever sent out).
No errors related to the hung calls are visible in the logs.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!