MTP3:General Configuration

• The Type of signaling parameter (i.e., Signaling Point Type) specifies whether the node being configured acts as a Signaling Point (SP) or as a Signaling Transfer Point (STP). The following values are allowed:

Signaling Point Type	Description
SP	MTP3 layer is used as an SP (signaling point) in the SS7 network
STP	MTP3 layer is used as an STP (signaling transfer point) in the SS7

---

• The Default point code 1 parameter specifies the default point code of the node being configured for ITU, TTC, and NTT networks. Used as the OPC when the user part does not specify the OPC in the data request.

• The Default point code 2 parameter specifies the default point code for ANSI or CHINA version. This is used as the OPC for ANSI or CHINA networks when the userpart does not specify the OPC in the data request.

• If the SSF validation required flag is 'True', the SSF of any message received on a link or from the userpart by MTP3 is checked against the SSF configured for that link or userpart respectively. For example, if a link is configured to carry international traffic and it receives messages with SSF other than SSF international traffic, the message is discarded.

---

• If the Restarting procedure required field is not set to 'None', the MTP3 restart procedure is started by MTP3 as soon as the first link becomes in-service. Allowable values include:

Restart Procedure	Description
None	Restart procedure disabled
ITU 88	ITU88 compliant restart procedure
ITU 92	ITU92 compliant restart procedure
ANSI	ANSI compliant restart procedure

NOTE: TTC, NTT and CHINA do not support MTP3 restart procedures. Therefore, this field should be configured with 'None'.

---

• Transfer restrict is a route management procedure of MTP3. It is a national option that can be enabled or disabled through this flag. Allowable values are 'True' or 'False'.

NOTE: TTC and NTT do not support transfer restrict procedures. Therefore, for TTC and NTT, this field is configured as 'False'.

---

• The General timers configuration parameters have the following definitions:

Timer	Description
T15 Timer	Waiting to start signaling route set congestion test. Typical value is 2000 milliseconds (2 seconds)
T16 Timer	Waiting for route set congestion status update. Typical value is 1400 milliseconds (1.4 seconds)
T18 Timer	Timer within a signaling point whose MTP restarts for supervising link and linkset activation as well as the receipt of routing information. The value is implementation and network dependent. Typical value is 11000 milliseconds (11 seconds) for ANSI and 30000 milliseconds (30 seconds) for ITU.
T19 Timer	Waiting to receive all traffic restart timer. Typical value is 67000 milliseconds (67 seconds)
T21 Timer	Waiting to restart traffic routed through adjacent SP timer. Typical value is 63000 milliseconds (63 seconds)
T26 Timer	Waiting to repeat traffic restart waiting msg timer. Typical value is 12000 milliseconds (12 seconds)

NOTE: TTC, NTT and CHINA do not support MTP3 restart procedures. Therefore, the timers related to this procedure need not be configured for these networks. For TTC and NTT, the route set congestion test is optional, in which case timers T15 and T16 need not be configured.