Dialogic DSI SPCI Network Interface Boards - Manual (Page 36)

6 Message Reference
36
6 Message Reference
6.1 Overview
This section describes the individual messages that may be sent to and
received from the Dialogic
® DSI SPCI Network Interface 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 DSI SPCI Network Interface Board the
application must call the library function GCT_set_instance to select the board
to which the message is sent. After receiving a message from the board, the
application must 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 four categories:
• General Configuration Messages,
• Hardware Control Messages,
• MTP Interface Messages, and
• Event Indication Messages.
6.1.1 General Configuration Messages
General Configuration Messages are normally issued by the s7_mgt
configuration utility in which case they need not, and must 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
DSI SPCI Board, configure each board and optionally configure additional
routes.
6.1.2 Hardware Control Messages
Hardware Control Messages are used to control various hardware devices on
the board. This includes the T1/E1 Line Interface Units (LIU), the digital cross
connect switches and the clocking mode for the DSI SPCI 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 to not
use s7_mgt), then the user application needs to build and send at least some
of the Hardware Control Messages.