My Oracle Support Banner

SLC Never Returns a CONNECT for Mobile Terminating Calls (Doc ID 2298745.1)

Last updated on MARCH 14, 2022

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), a problem exists when trying to have Advanced Control Services (ACS) on the Service Logic Controllers (SLCs) return a CONNECT operation in response to an Initial Detection Point (IDP) with Detection Point (DP) set to Terminating_Attempt_Authorized(12).  A Terminating_Attempt_Authorized(12) Detection Point in the Terminating Basic Call State Model (T-BCSM) represents an attempt to establish a Mobile Terminating (MT) call.

Very specific conditions (as defined in the various Signalling System Number 7 (SS7) protocol specifications for telephony) determine whether a Service Control Point (SCP) should return a CONNECT or a CONTINUE operations.  A full list of these conditions can be found in the ACS Technical Guide under the Notes section of the useContinueOperation.  The SLCs are SCPs.

ACS complies with these conditions for Mobile Originating (MO) calls, but for MT calls, never returns a CONNECT regardless of any other configuration whether in acs.conf or in an ACS Control Plan (CP).

As a result of this, it is not possible perform certain functions such as changing the terminating number for a call by returning a different Destination Routing Address (DRA) as this parameter is only allowed in a CONNECT operation.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.