My Oracle Support Banner

SCA Fails to Terminate Calls with ACS on State Machine Errors (Doc ID 2383168.1)

Last updated on APRIL 12, 2018

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.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), the Session Control Agent (SCA) is the Session Initiation Protocol (SIP) gateway to Advanced Control Services (ACS).  It converts SIP messages to equivalent Intelligent Network Application Part (INAP) messages to charge and control a SIP session.

A bug exists in SCA where state machine errors do not clear the call with ACS.  Depending on exactly which where the state machine exception occurs, a call may not terminate until the caller has completely run out of funds.

Here is an example of an SCA state machine error alarm:

ERROR: (SIPInteraction.cc:2591) 1500: State machine error; transition: <Message Type>, state: <Current State>

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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