ACS Does Not Support TCAP Basic End Scenarios and Never Releases Voice Calls for NotifyAndContinue ERBCSM Events
(Doc ID 2420923.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.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), Advanced Control Services (ACS) does not support a Transaction Capabilities Application Part (TCAP) Basic End scenario.
A Basic End is a TCAP_END sent to the remote end to end a TCAP dialog and as a result, ACS does not free allocated resources and the call never ends on the Service Logic Controller (SLC). This issue only affects resources on the SLC as the call/reservation is correctly terminated with the Online Charging System (OCS).
This issue affects all calls which end due to a Basic Call State Model (BCSM) Event previously armed as NotifyAndContinue arriving at the SLC in a TCAP_CONTINUE.
By default, the following events are armed as NotifyAndContinue:
- o/tDisconnect (for Leg1)
It is expected that the SLC sends a TCAP_END with no components to end the TCAP dialog with the Mobile Switching Center (MSC).
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