My Oracle Support Banner

Controlling the TCAP Transaction ID Length Applied by NCC when Sending a TCAP Message (Doc ID 2011901.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.

Goal

This note explain if it is possible to control the length of the TCAP Originating Transaction ID (OTID) the Network Charging and Control (NCC) application decides to apply.

For example, forcing the NCC application to always generate 4 octets long OTIDs. 

Solution

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
Goal
Solution
 ANSI vs ITU TCAP
 NCC use of 1, 2, 3 or 4 octets OTIDs
References


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