Welltech Dialogic SS7 Protocols ISUP - Manual (Page 14)

Section 2 General Description
14
Depending on the platform that ISUP is running, some or all of these
configuration messages may be generated based on text based configuration
files (config.txt). In such cases the user does not need to generate the
individual configuration messages. Refer to the product documentation for the
specific product for further information.
2.2.1 Customizing ISUP variants
The ISUP module supports a variant-based mechanism that enables the user
to select a custom-reserved variant thus permitting the ISUP module to send
and receive proprietary parameters (in supported ISUP messages only) to
and from the network. The following messages are required for this
mechanism:
• Variant Initialisation message (0x5712)
• Custom Parameter Configuration message (0x5713)
Refer to
Section 8.6 on page 142 and Section 8.7 on page 143 for further
details.
The variant-based mechanism may be initialized as follows:
1. Configure the ISUP module using the Configure Request message
(0x7700) as described in Section : 2.2 Module Configuration on page 13 .
2. Two ‘custom’ variant values are specifically reserved for this procedure
as shown in the following table (refer to the parameter in
Section : 8.2 Configure Circuit Group Request on page 126 ):
Value Mnemonic Meaning
0xfd ISPGVAR_CUST02 Custom variant CUST02
0xfe ISPGVAR_CUST01 Custom variant CUST01
Configure a circuit group and select one of the available custom variant
values using the Configure Circuit Group Request message (0x7701).
The Configure Circuit Group Request message may be sent at any stage
after the ISUP module has been configured; it is not necessary to wait
until after the custom variant and parameters have been configured.
3. Initialize a custom variant using the Variant Initialisation message
(0x5712) and specify the ISUP variant e.g. ISPGVAR_ITU92 upon which
the custom variant is based. The Variant Initialisation message may be
sent at any stage after the ISUP module has been configured but it must
be sent before the Custom Parameter Configuration message (described
in the next step).
4. Configure the custom parameter using the Custom Parameter
Configuration message (0x5713). The Custom Parameter Configuration
message may be sent at any stage after the ISUP module has been
configured but it must be sent before the sending and receiving of any
customized parameters.