Call Not Terminated By UATB In The Last Slice Before The Max Call Duration Is Reached
(Doc ID 2431912.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
An issue was found on Network Charging and Control (NCC) Version 5.0.2 for calls ending in the last slice before the max call duration is reached.
Scenario looks like this:
- A call is handled by UATB FN with max call duration set.
- The call is disconnected by the called party (oDisconnect, legId=2) and the disconnect is flagged by ACR.legActive=false.
- If the event is received with the last slice before max call duration expiry, the disconnect information is ignored and UATB node does not exit and continues in the call (next AC message is sent to the network).
The expected behavior:
- Call should be ended and the UATB node exits on the ACR.legActive=false flag
Terms and abbreviations:
Universal Attempt Termination with Billing Feature Node (UATB FN) node is used to bill subscribers for calls that they make or receive.
A Mobile Switching Center (MSC) is the centerpiece of a network switching subsystem. The MSC is mostly associated with communications switching functions, such as call set-up, release, and routing.
applyCharging (AC) - Message used by the Service Control Point (SCP) to grant a defined duration for the call. The parameter in it called maxCallPeriodDuration defines the maximum time allowed before the first applyChargingReport has to come back from the switch, this parameter is in deci-seconds.
applyChargingReport (ACR) - This message is an answer from the network switch (MSC) when one of the following scenarios happened :
: the call has ended, or
: the duration of the last applyCharging.maxCallPeriodDuration parameter has elapsed.
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