A typical NMS MTP 2 implementation consists of the following components:
MTP 2 task that provides the signaling link functions defined by the ITU-T (Q.703), ANSI (T1.111), and TTC standards:
Signal unit delimitation and alignment
Error detection and correction
Link alignment
Link error monitoring
Flow control
High speed links (HSL) meet the ANSI T1.111-1996 and Q.703/Annex A standards. Each HSL occupies a full (unchannelized) T1/E1 and transfers data at the rate of 2.0 (1.544) Mbps. For information about configuring high speed links, refer to Mtp2InitLinkCfg.
The TX alarms manager task that collects unsolicited alarms (status changes) generated by the SS7 tasks and forwards them to the host for application-specific alarm processing.
The txalarm utility for displaying and optionally saving alarms from the MTP 2 task to disk.
A TX driver for the host operating system that provides low level access to the TX boards from the host.
The MTP 2 interface consisting of a set of messages passed between the application and the MTP 2 task on the TX communications processor. These messages enable the application to initialize, transfer data, and exchange status information with MTP 2, and implement the link and traffic management procedures defined in the relevant standards for MTP 3.
The mtp2cfg utility for downloading text file configurations to the MTP 2 task. mtp2cfg is provided in source and executable form.
The mtp2mgr utility for managing the MTP 2 task. mtp2mgr is provided in source and executable form.
The mtp2app and mtp2itu demonstration programs, also provided in source and executable form. These programs accept user commands and send messages to the MTP 2 task.
MTP 2 functions that manage the MTP 2 task. mtp2cfg and mtp2mgr use these functions.
The following illustration shows a typical MTP 2 implementation: