The following illustration shows the SS7 software architecture in a typical system with separate host applications handling the data and control (ISUP) interface, system configuration, and system alarms:
<NMSBREAK>
The TX board consists of the following components:
ISUP task that implements the SS7 ISUP layer.
ISUP variant task that contains the encoding and decoding messages tables for a specific ISUP variant (for example, ITU White or ANSI 95).
MTP task that implements the SS7 MTP 2 (data link) layer and the SS7 MTP 3 (network) layer.
Optional SCCP task that implements the SS7 SCCP layer.
Optional TCAP task that implements the SS7 TCAP layer.
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 host consists of the following components:
A TX driver for the native host operating system that provides low-level access to the TX board from the host.
Functions that provide the application with a high-level interface to the ISUP layer services.
Functions that provide the application with a high-level interface to the ISUP management layer services.
An alarm collector process for capturing alarms and saving them to a text file. The alarm collector (txalarm) is provided in both executable and source form. The source can be used as an example for developers who want to integrate the TX alarms into their own alarm monitoring system.
Configuration utilities (one for each SS7 layer) that read the SS7 configuration files and load the configuration to the TX processor tasks at system startup. The ISUP configuration utility (isupcfg) is provided in both executable and source form. The source code can be used as an example for developers who want to integrate the ISUP configuration into their own configuration management system.
The ISUP manager utility (isupmgr) that provides a command line interface from which alarm levels can be set, buffers can be traced, and ISUP statistics can be viewed and reset.