My Oracle Support Banner

SDK Unable to Handle TCAP_PRE_END from ACS (Doc ID 2551995.1)

Last updated on OCTOBER 09, 2020

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.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), custom applications written with the Software Development Kit (SDK) for NCC/3C are not able to accept an internal TCAP_PRE_END operation from Advanced Control Services (ACS).

The code that decides which operations to accept/reject are hardcoded in the SDK and unrecognized operations are discarded before they are made available to custom code.

The following alarm is logged when a TCAP_PRE_END is received:

The most common use of this operation is ACS' Absent Without Leave (AWOL) logic which times out calls when outstanding messages have not been received in time.  More information on AWOL can be found in the ACS Technical Guide.

The Transaction Capabilities Application Part (TCAP) primitives currently supported by the SDK are:

As a result of this, it is not possible to add custom logic to applications based on a TCAP_PRE_END message.

Changes

 

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
Changes
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.