You are here: CSP Developer’s Guide: Common Channel Signaling > 2 Introduction to SS7 > MTP3 for Japanese Telecommunications

MTP3 for Japanese Telecommunications

Overview

Dialogic’s system software SS7 stack has been enhanced to support MTP3 variants used in Japan: JT, NTT and DDI. While the term JT is used as a variant within the system software, JT is also the TTC standard for MTP3 used in Japanese telecommunications networks. The JT variant supports Japan Telecom. The NTT variant supports Nippon Telegraph and Telephone of Japan. The DDI variant supports DDI Corporation of Japan.

MTP3 JT, NTT, DDI Variants

The system software SS7 stack supports MTP3 variants: JT, NTT and DDI, which support networks in Japan. The Japanese telecommunications specification, TTC JT-Q707, defines Signal Routing Test (SRT) to verify a signaling route for end-to-end communication. The telecommunications specification of the International Telecommunication Union (ITU-T), ITU-T Q.707, defines Signaling Link Test (SLT), but does not define SRT. Even though JT-Q707 does not define SLT, the software allows a host to locate a destination point code (DPC) and test a signaling route to a switch using JT standards.

Hardware Requirements

The feature requires an SS7 Series 3 and SS7 I/O Series 3 Card Set.

Locating a DPC and Testing a Signaling Route

The MTP3 component, Signaling Link Test Control (0x41) allows a switch to locate a DPC and test a signaling route. With JT, NTT, and DDI variants, SLTC is not performed by default. You must manually activate this component by sending a PPL Event Request message. The table below describes the process of testing a signaling route and accessing a destination using the SLTC component.

Stage | Description
--- | ---
1 | To initiate a Signaling Route Test, the host sends a PPL Event Request (0x44) to the MTP3 PPL component, SLTC.
2 | If the PPL Event Request is successful in locating a DPC, the switch immediately sends an ACK (acknowledgment) to the host. If the switch is unsuccessful in detecting a DPC a NACK (Negative Acknowledgment) is sent to the host and the signaling route test is not initiated.
3 | If the PPL Event Request was successful, a Signaling Route Testing message is sent to the remote DPC.
4 | After the test is completed, the switch sends a PPL Event Indication (0x43) to the host with the results of the test.

Example Configuration File

This section shows examples of configuration files.

PPL Event Request: To Initiate SRTC

The script below uses the PPL Event Request message to activate a route signaling test.

00 1d 00 44 00 0d ff\

00 01 09 02 00 00 \ ' AIB type - Stack/Link(0x09)

00 41 00 01 \ ' PPL comp/Event ID (0x41/0x0001)

01 02 1e 0a 00 01 00 12 00 04 00 00 02 22 ' ICB sub type - 0x1E

PPL Event Indication - Result of SRTC

The following is an example of a configuration script file using the PPL Event Indication message to get the results of a signaling route test.

00 23 00 43 00 00 00 \

00 01 09 02 01 04 \ ' AIB type - Stack/Link(0x09)

00 41 00 01 \ ' PPL comp/Event ID (0x41/0x0001)

01 02 1E 10 00 02 00 11 00 02 00 10 00 12 00 04 00 00 01 11 ' ICB sub type - 0x1E

See Signaling System Number Seven.
Message Transfer Part level 3 - network level
International Telecommunications Union (UN)
International Telephone Union – Telecommunications sector (UN)
ITU-TSS Publication on Testing and Maintenance (MTP)
Destination Point Code
See Programmable Protocol Language.
A condition that, when met, drives a state machine from one state to another. A condition that drives a Component out of its current state by invoking an associated primitive.
Positive acknowledgment to a message
Negative acknowledgement to a message.
See Address Information Block.
See Information Control Block.