Unable to use DisconnectLeg Operations in Low Balance Scenarios with DCD
(Doc ID 2380374.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
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), it is not possible to have the Service Logic Controller (SLC) send a disconnectLeg operation back to the network.
A disconnectLeg operation is typically used to disconnect the B-Leg or Called Party of a voice call with the intention of reconnecting the A-Party or Calling Party to another destination (such as a call center or announcement server when the subscribers funds have been exhausted). For example:
Enabling disconnectLeg operations is covered in: What is the Difference Between Exit Branches in the UATB Node that have Released or Disconnected Causes (Doc ID 1591825.1)
In very low balance situations (where the returned funds from the diameter server is less than the configured DCD lowCreditBuffer Attribute Value Pair (AVP)), and the Final-Unit-Indicator (FUI) is set, the releaseIfDurationExceeded flag is being set in the applyChargingReport back to the Mobile Switching Center (MSC). When the releaseIfDurationExceeded flag is set, the MSC disconnects the call once the granted call duration has lapsed and releases both legs of the call. For example:
As a result, the disconnectLeg operation can no longer be used as the call no longer exists.
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