My Oracle Support Banner

The SIGTRAN Stacks Do Not Support Full Correlation IDs (Doc ID 2964495.1)

Last updated on AUGUST 02, 2023

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.6.0.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.6.0.0 [Release 4.3 to 12.0.0]
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) up to and including 12.0.6.0, the Signalling Transport (SIGTRAN) stacks do not support full correlation IDs.

In this context, a "full" correlation ID is when the assistRequestInstructions (aRI) sent by a Signalling Resource Function (SRF) sets the correlation ID to the entire assistingSSPIPRoutingAddress from the estalishTemporaryConnection (eTC).

The expected/supported approach is the SRF extracts just the correlation ID from the assistingSSPIPRoutingAddress as described in Note 1310239.1 and returns just this field.

The m3ua_if/sua_if processes will log an error such as:

Apr 3 21:20:56.520754 m3ua_if(25909) WARNING: detected correlation ID: '-418857314' outside of valid range

which results in the announcement failing.

From the specification, the definition of the correlation ID is:

This parameter is used by the SCF to associate the AssistRequestInstructions from the assisting SSF or by a SRF with the InitialDP from the initiating SSF. The value of the "correlationID" may be extracted from the digits received from the initiating SSF or be all of the digits

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!

In this Document
Symptoms
Cause
Solution
References


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