My Oracle Support Banner

M3UA: How to Change the SCCP Origination Address in the TCAP CONTINUE Message (Doc ID 2774876.1)

Last updated on MAY 12, 2021

Applies to:

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


In the current scenario, customer is using a Virtual Global Title (Virtual GT) to round robin the TCAP traffic between the two SLC Nodes (Service Logic Center Nodes).
With this configuration, for long SMSs (more than 160chars) SLC will use the Virtual GT Address in TCAP CONTINUE message sent back to MSC (Mobile Switching Center). STP (Service Translation Point) will use this GT to route the next message in the dialog (forwardSM) to the next available SLC. In some cases, it will be a different SLC and the message will fail with "Unrecognised Transaction ID".

Scenario is like this:
1. STP sends a Begin ( TCAP message ) to SLC Instance_1 using Virtual GT;
2. SLC Instance_1 replies and sends Continue message to STP using Virtual GT;
3. STP sends the invoke forwardSM to SLC Instance_2 using Virtual GT;
4. SLC Instance_2 rejects the message to STP and logs this message: "Unrecognised Transaction ID received"

M3UA interface is used for TCAP traffic.

Qn: Is there an option to force SLC sends the Physical GT Address?


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.