Controlling the TCAP Transaction ID Length Applied by NCC when Sending a TCAP Message
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
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.
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 hundreds of Community platforms