Welltech SPCI2S Intel NetStructure SS7 Boards - Manual (Page 32)

SS7 Programmer’s Manual for SPCI2, SPCI4 and CPM8 Issue 2 Page 32
5. APPLICATION MESSAGE SPECIFICATIONS
5.1 Overview
This section describes the individual message that may be sent to and received
from the board. Some messages are sent by the user’s application software whilst
others are sent by utility programs such as the configuration utility s7_mgt.
Prior to sending any message to the board the application should call the library
function GCT_set_instance to select which board the message will be sent to. After
receiving a message from the board the application should call the library function
GCT_get_instance to determine which board the message came from. These
library functions are described in the
Software Environment Programmer’s
Manual.
The messages are grouped into 4 categories: General Configuration Messages,
Hardware Control Messages, MTP Interface Messages and Event Indication
Messages.
5.1.1 General Configuration Messages
General Configuration Messages are normally issued by the s7_mgt configuration
utility in which case they need not and should not be generated by any user
application software.
If the user elects not to use s7_mgt then it is necessary for the application to build
and send messages to configure the SSD module, reset each individual board,
configure each board and optionally configure additional routes.
5.1.2 Hardware Control Messages
Hardware Control Messages are used to control various hardware devices on the
board. This includes the E1 / T1 Line Interface Units (LIU), the digital cross connect
switches and the clocking mode for the board.
In a static configuration, all these hardware blocks can be set up using the s7_mgt
configuration utility along with the appropriate commands in the config.txt file.
If dynamic control of the hardware is required (or the user has elected not to use
s7_mgt) then the user application will need to build and send at least some of the
Hardware Control Messages.