My Oracle Support Banner

Enhancement for Inter-SLC aRI Routing (Doc ID 2968166.1)

Last updated on AUGUST 16, 2023

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) the Signaling Transport (SIGTRAN) stacks (m3ua_if and sua_if) always expect that any assistRequestInstruction (aRI) messages received are in response to the establishTemporaryConnection (eTC) message it sent out.

The following article explains how the eTC and aRI messages are correlated:

How to Link Correlation ID in the AssistRequestInstructions to the RoutingAddress in the EstablishTemporaryConnection for IVR Calls in Snoop Traces (Doc ID 1310239.1)

When an aRI is received by a SIGTRAN stack, it tries to match the received correlationID (in the aRI) with an existing Service Logic Execution Environment (SLEE) call ID (CID).  As the correlationID was not generated from this SLC, the following warning is logged by the SIGTRAN stack:

WARNING: detected correlation ID: '<ID>' outside of valid range

which will then forward the aRI to slee_acs on a new SLEE dialog, which in turn logs the following errors:

ERROR: handleINAPComponent: No context, No IDP
ERROR: acsChassisMain: Unhandled INAP Component (type 14, opErrId 16, call <ID>)

This results in the announcement that was meant to be played to the caller to fail and a potential leak in resources.


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.