Specifications

Appendix A - Protocol Configuration Using Discrete Messages
108
A.3 Q.SAAL Protocol Configuration Using Individual
Messages
The process to configure the board for Q.SAAL links using individual messages is
closely related to section A.1 on page 104. The full message sequence is shown
diagrammatically in Figure 4. Q.SAAL Configuration Message Sequence Diagram.
1. Build and send an SSD Reset Request (SSD_MSG_RESET) to the SSD module. This
message contains the parameters required to initialize the SSD module.
For each board in the system:
2. Build and send a Board Reset Request (SSD_MSG_RST_BOARD). This message
contains the address (or identifier) of the board and the name of the code file. It
causes the board to be reset and the code file downloaded. For each board, the
application should wait until a Board Status Indication (SSD_MSG_STATE_IND) is
received and inspect the status field to determine if the reset operation was
successful. On failure, the user should check carefully the event and failure codes
as defined in the SSD_MSG_STATE_INDSSD_MSG_STATE_IND message and try
again.
3. Build and send a Board Configuration Request (MGT_MSG_CONFIG0) to the
onboard management task (MGMT_TASK_ID) to configure the basic board
parameters. When using Dialogic
®
DSI SS7MD Boards, the value of the config_type
parameter in the Board Configuration Request must be set to 3. Wait for the
confirmation message and check the status.
4. To set up the LIU and port for the T1/E1/J1 ports, the LIU Configuration Request
(LIU_MSG_CONFIG) should be used. Wait for the confirmation message for each
LIU and check the status.
For each board running ATM links:
5. Configure the ATM module using a ATM_MSG_CONFIG message to configure the
ATM per board options and vpi/vci masks. Wait for the confirmation message from
each ATM module and check the status.
For each ATM cell stream in the system:
6. Build and send an ATM cell stream configuration request
(ATM_MSG_CFG_STREAM) to set up the parameters of the ATM link. Wait for the
confirmation message and check the status.
For each Q.SAAL link in the system:
7. Build and send a Q.SAAL Link Configuration Request (QSL_MSG_CFG_LINK) to set
up the per link configuration parameters. Wait for the confirmation message and
check the status.
8. If the required per link timer values are different from the defaults, build and send
a per Q.SAAL link timer configuration (QSL_MSG_CFG_TIMERS). Wait for the
confirmation message and check the status.
Once per system:
9. Build and send an MTP3 Module Reset Message (MTP_MSG_RESET) to reset the
MTP3 module. See the MTP3 Programmer's Manual for the message definition. Wait
for the confirmation message and check the status.
10. Build and send an MTP3 Module Configuration Request (MTP_MSG_CONFIG) to set
up configuration parameters that relate to the MTP3 environment (number of link