Tekelec IP7 Secure Gateway Administration Manual page 573

Database Administration Manual - IP7 Secure
Gateway
SI=4 (TUP)
type=full
ncics=<0 to 4095> (See
Notes 2 and 3)
ncice=<0 to 4095> (See
Notes 2 and 3)
rcontext=<the current
routing context value
assigned to the routing
key> (See Notes 4 and
5)
1. The values for these parameters must be entered exactly as shown in the rtrv-appl-rtkey
command output for the routing key being changed. However, text strings can be used in place of
some numerical service indicator values. See
these text strings. The text string must correspond to the numerical value shown in the routing key
being changed.
2. The cics and cice parameters must be specified and either the ncics or ncice parameters, or
both, must be specified. If both the ncics and ncice parameters are specified, the value of the
ncics parameter must be less than the value of the ncice parameter. If the ncics parameter is
not specified, the value of the ncice parameter must be greater than or equal to the cics parameter
value. If the ncice parameter is not specified, the value of the ncics parameter must be less than
or equal to the cice parameter value.
3. The new CIC range cannot overlap the CIC range in an existing routing key.
4. If the routing key contains a numerical value in the RCONTEXT column in the rtrv-appl-rtkey
output, the rcontext parameter and value can be used in place of the dpc, si, opc, cics, cice,
or type=full parameters and values to identify the routing that is being changed with the
chg-appl-rtkey command. However, if only the rcontext parameter is used to identify the
routing key being changed, only one of these parameters, ncics or ncice can be specified with the
chg-appl-rtkey parameter. If you wish to specify the ncics and ncice parameters with the
chg-appl-rtkey parameter, the dpc, si, opc, cics, cice, or type=full parameters and values
must be specified with the chg-appl-rtkey command.
5. If the routing key contains dashes in the RCONTEXT column in the rtrv-appl-rtkey output,
the dpc, si, opc, cics, cice, or type parameters and values must be used with the
chg-appl-rtkey command to identify the routing key being changed.
Rules for Splitting the Range of CIC Values in an Existing Routing Key
The parameter combinations used by the chg-appl-rtkey command to split the range of CIC values
in the routing key are shown in
CIC Values in an Existing Routing
910-6278-001 Revision A, January 2012
SI=5 (ISUP)
type=full
ncics=<0 to 16383> (See
Notes 2 and 3)
ncice=<0 to 16383> (See
Notes 2 and 3)
rcontext=<the current
routing context value
assigned to the routing
key> (See Notes 4 and
5)
Table 38: Service Indicator Text String Values
Table 40: Routing Key Parameter Combinations for Splitting the Range of
Key.
IETF M3UA and SUA Configuration Procedures
type=full
ncics=<0 to 4095> (See
Notes 2 and 3)
ncice=<0 to 4095> (See
Notes 2 and 3)
rcontext=<the current
routing context value
assigned to the routing
key> (See Notes 4 and
5)
SI=13 (QBICC)
type=full
ncics=<0 to 4294967295>
(See Notes 2 and 3)
ncice=<0 to
4294967295> (See Notes
2 and 3)
rcontext=<the current
routing context value
assigned to the routing
key> (See Notes 4 and
5)
for a list of
573