4.189 dlt-appl-rtkey

Use this command to delete static entries from the Routing Key table. These entries are used to associate a routing key with a socket name. A static entry is created using the ent-appl-rtkey command.

There are three types of routing keys, as follows:

  • DPC, SI, SSN routing keys, which are used to route SCCP messages
  • DPC, SI routing keys, which are used to route non-SCCP and non-ISUP messages
  • DPC, SI, CIC routing keys, which are used to route ISUP messages

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.
asname (optional)
Application Server (AS) name; AS assigned to this routing key.
Range:
ayyyyyyyyyyyyyy

Up to 15 alphanumeric characters; the first character must be a letter

cice (optional)
The end range of circuit identification codes assigned to the routing key. The cice and cics parameters identify the routing key to be changed. Valid only and required if a value of 4, 5, or 13 is specified for the si parameter.
Range:
0 - 4294967295

See Table A-4  for valid CIC values for specified SI and MSU types.

cics (optional)
The end range of circuit identification codes assigned to the routing key. The cice and cics parameters identify the routing key to be changed. Valid only and required if a value of 4, 5, or 13 is specified for the si parameter.
Range:
0 - 4294967295

See Table A-4  for valid CIC values for specified SI and MSU types.

dpc (optional)
ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
dpca
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

dpc/dpca/dpci/dpcn/dpcn24/dpcn16 (optional)
Destination point code.
dpci (optional)
ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

dpcn (optional)
ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

dpcn24 (optional)
24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

dpcn16 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000---127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un-000-127
sna-000-15
mna-000-31
opc (optional)
ANSI originating point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
opca
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

opc/opca/opci/opcn/opcn24/opcn16 (optional)
Originating point code. Valid only and required if the si parameter has a value of 4, 5, or 13.
opci (optional)
ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

opcn (optional)
ITU national originating point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

opcn24 (optional)
24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

opcn16 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000---127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un-000-127
sna-000-15
mna-000-31
rcontext (optional)
Identify a routing key by its routing context when a routing key needs to be deleted as an optional alternative to entering the dpc/si/ssn/opc/cics/cice/type key parameters.
Range:
0 - 4294967295
si (optional)
Service indicator.
Range:
0 - 15

0-15 or equivalent text values

Number = TextDescription

0=snm—Signaling network management messages

1=regtest—Signaling network testing and maintenance regular

2=spltest—Signaling network testing and maintenance special

3=sccp—SCCP

4=tup—Telephone user part

5= isup—ISDN user part

13= qbicc

ssn (optional)
Subsystem number.
Range:
0 - 255
type (optional)
Type of routing key that is being changed.
Range:
full
partial
default
Default:
full

Example

dlt-appl-rtkey:dpc=1-1-1:si=3:asname=as1:ssn=255

dlt-appl-rtkey:dpci=s-3-11-1:si=5:opci=s-4-11-2:

cics=1:cice=1000:asname=asitu

dlt-appl-rtkey:rcontext=100

dlt-appl-rtkey:dpcn16=121-10-5:si=5:opcn16=121-10-6:cics=1:cice=1000:

asname=asitu

Dependencies

The SSN is valid and must be specified only when the si=3 (or sccp) parameter is specified. When the si=3 (or sccp) parameter is not specified, the ssn parameter must not be specified.

The value entered for the cics parameter must be less than or equal to the value entered for the ending circuit identification code cice parameter.

A circuit identification code range (cics to cice) that overlaps an existing routing key cannot be specified.

When the DPC is ANSI and the si=4 parameter is specified, a DPC/SI routing key must be specified (TUP is used only in an ITU network).

The opc, cics, and cice parameters are required and can be entered only if the si parameter value is 4, 5, or 13.

If the si parameter has a value of 4, 5, or 13 (tup, isup), or the qbicc parameter is specified, the opc, cics, and cice parameters used to route ISUP messages must be specified. The opc, cics, and cice parameters can be specified only if the si parameter has a value of 4, 5, or 13 (tup, isup), or if the qbicc parameter is specified.

Table A-4 shows valid CIC values for SI types 4, 5, and 13.

The routing key must be in the Routing Key table.

If the asname parameter is specified, the AS name must already be defined in the AS table. The AS name and parameters specified for a routing key must use an address format that is valid for the adapter type used by the ASP associations assigned to the AS.

When the type=full parameter is specified, the dpc and si parameters must be specified.

The following types of partial routing keys are supported:

  • DPC-SI-OPC (ignore CIC) can be used as a partial match key for CIC- based traffic.
  • DPC-SI (ignore all other fields) can be used as a partial match key for CIC- based traffic or SCCP traffic.
  • DPC only (ignore all other fields) can be used as a partial match for any type of traffic.
  • SI only (ignore all other fields) can be used as a partial match for any type of traffic.

The following card locations are not valid for this command: 1113, 1115, 1117, 1118, and all xy09 and xy10 locations (where x is the frame and y is the shelf). The card must be equipped and in service.

If the type=default parameter is specified, then the dpc, si, ssn, opc, cice, and cics parameters cannot be specified.

The asname or the rcontext parameter must be specified in the command.

The opc, cics, and cice parameters can be specified with the si parameter only if the si parameter has a value of 4, 5, or 13 (or tup, isup, or qbicc).

Notes

A specific routing key/socket name association can be deleted by specifying a fully qualified routing key (dpc/dpca, si, ssn, and asname). By default, socket associations in the static key entries are deleted using the dlt-appl-rtkey command.

The OPC and DPC cannot specify a cluster route.

Group codes are required for ITU-N point codes (DPCN/OPCN) when the Duplicate Point Code feature is turned on.

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).

Output

dlt-appl-rtkey:asname=tekelec:si=3:ssn=255:type=full:dpc=2-2-2

    rlghncxa03w 08-03-17 15:35:05 EST  EAGLE 38.0.0
    DLT-APPL-RTKEY: MASP A - COMPLTD 
;