You are here: CSP Developer’s Guide: Common Channel Signaling > 6 SCCP/TCAP > Adjacent Translators Configuration

Adjacent Translators Configuration

Overview

In SCCP, a Global Title Translator is the node that performs the global title translation (GTT). The result of the GTT could be the DPC/SSN or another global title, in which case another node is used to perform further GTT. Therefore, there may be more than a translator involved before an SCCP message reaches its destination.

Adjacent Translator

The Adjacent Translator is the first node that performs the GTT from the point of view of the SSP (adjacent is a logical term). For example, Node A is adjacent to Node B if any SS7 path exists between them without a GTT in the path.

Alternatively, the physically adjacent STP could be the Adjacent Translator and be responsible for routing to the next GTT. Dialogic’s SCCP implementation places no limitation on the network configuration.

If an Adjacent Translator needs to be defined for a subsystem, the route to the Point Code must be defined first. If it is not, a NACK of DPC Not Configured (0x550E) is returned. To delete a route, you must first delete the Adjacent Translator, otherwise, a NACK of SCCP/TCAP Related Configuration Parameter Error (0x55).

If you delete an SSN, all of its associated configuration, including Adjacent Translators, is automatically deleted.

Routing with a Global Title

For any local SSN, you can define Adjacent Translators and Network destination point codes and subsystem numbers. If the adjacent translator is defined, you may route the message to the translator node for global title translation

Destination Point Code
SubSystem Prohibited. See also Service Switching Point.
See Signaling System Number Seven.
A number that addresses a node in a SS7 network.
Negative acknowledgement to a message.
See Transaction Capability Application Part.