Welltech Dialogic SS7 Protocols ISUP - Manual (Page 121)

Dialogic ® SS7 Protocols ISUP Programmer's Manual Issue 15
121
8 Non-Primitive Interface
In addition to the primitives defined for the User to ISUP interface and the
ISUP to MTP interface, the ISUP module supports non-primitive requests for
configuration and diagnostic purposes. The message structure and
parameters for each message are defined in the following subsections.
When the ISUP module returns a confirmation message containing a status
value, the status will be one of the following:
Value Mnemonic Description
0 none Success
1 ISPE_BAD_ID Inappropriate or invalid id in request message.
5 ISPE_BAD_MSG Inappropriate or unrecognized message type.
6 ISPE_BAD_PARAM Invalid parameters contained in message.
7 ISPE_BAD_LICENSE Invalid message / parameter for this license.
8 ISPE_NO_MEMORY No memory available.
8.1 Configure Request
This message must be the first message issued to the ISUP module. It is
used to configure the environment dependent features for the module. It is
sometimes referred to as the ‘per-module’ configuration message. Please
refer to Section : 2.2 Module Configuration on page 13 for details of how the
configuration messages are used.
Message Header
structure MSG
type ISP_MSG_CONFIG (0x7700)
id 0
src Originating module ID
dst ISUP module ID
rsp_req Sending layer's bit set if confirmation required
hclass 0x00
status 0x00
err_info 0x00
len 40