ent-appl-rtkey

Use this command to configure static entries in the Routing Key table, which associates a routing key with a socket name.

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 in Appendix A for a detailed description of point code formats, rules for specification, and examples.

asname (mandatory)

Application Server (AS) name 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.

Range:: 0 - 4294967295
See Table A-4 for valid CIC values for specified SI and MSU types.

cics (optional)

The start range of circuit identification codes assigned to the routing key.

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. This parameter is valid and required if a value of 4, 5, or 13 is specified for the si parameter and the type=full parameter is specified.

opci (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.

opcn (optional)

New 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)

Routing context. The new routing context for a routing key. The routing context uniquely identifies the routing key.

Routing context is mandatory for routing keys associated with SUA Application Servers. Routing context is optional for routing keys associated with M3UA Application Servers.

Range:: 0 - 4294967295

si (optional)

Service indicator.

Range:

0-15 or equivalent text values

Number =Text—Description

0=snm—Signaling network management messages

1=regtest—Signaling network testing and maintenance regular

2=spltes—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)

The type of routing key.

Range:

full
partial
default

Default:

full

Example

ent-appl-rtkey:asname=suaas1:dpc=8-8-8:si=3:ssn=5:rcontext=100

ent-appl-rtkey:asname=suaas2:dpc=8-8-8:si=3:type=partial:rcontext=101

ent-appl-rtkey:asname=suaas3:dpc=8-8-8:type=partial:rcontext=102

ent-appl-rtkey:asname=suaas4:si= 3:type=partial:rcontext=103

ent-appl-rtkey:asname=suaas5:type=default:rcontext=104

ent-appl-rtkey:asname=m3uaas1:dpc=8-8-9:si=5:opc=3-3-3:cics=1:cice=100:rcontext=200

ent-appl-rtkey:asname=m3uaas2:dpc=8-8-9:si=5:opc=3-3-3:type=partial:rcontext=201

ent-appl-rtkey:asname=m3uaas3:dpc=8-8-9:si=5:type=partial:rcontext=202

ent-appl-rtkey:asname=m3uaas4:dpc=8-8-9:type=partial:rcontext=203

ent-appl-rtkey:asname=m3uaas5:si= 5:type=partial:rcontext=204

ent-appl-rtkey:asname=m3uaas6:type=default:rcontext=205

ent-appl-rtkey:dpci=s-3-11-1:si=5:opci=s-4-11-1:cics=1:cice=1000:asname=asitu

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

ent-appl-rtkey:dpci=3-11-1:si=3:opci=4-11-1:cics=1:cice=1000:asname=asitu:rcontext=7

ent-appl-rtkey:dpcn16=121-10-15:si=3:opcn16=121-10-16:asname=asitu

Dependencies

The srkq parameter (see the chg-sg-opts command) limits the maximum number of static routing keys that can be provisioned using this command. For SS7IPGW and IPGWI applications running on E5-ENET-B cards, there is a limit of 2500 routing keys in the system.

The ssn parameter is valid only when the si=3 (or sccp) parameter is specified.

The value specified for the cics parameter must be less than or equal to the value specified for the cice parameter.

The ISUP routing-over-IP feature must be turned on before a DPC/SI/CIC routing key to route ISUP messages can be specified.

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

When a value of 4, 5, or 13 (tup, isup, or qbicc) is specified for the si parameter, the opc, cics, and cice parameters are required. The opc, cics, and cice parameters can be specified only if a value of 4, 5, or 13 is specified for the si parameter. See Table A-4 for valid cic and si values for MSU types.

Partial point codes are not allowed; no asterisks can be specified in the routing key in the command.

Mixed point code types are not allowed; the types for the opc and dpc parameters must match.

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

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

The group codes for the dpc and opc parameter values must match when both parameters are entered in the command.

The rcontext parameter must be specified for routing keys that are associated with SUA Application Servers.

The specified rcontext parameter value must not already exist in the database.

If specified, the service indicator parameter must be si=3 for routing keys that are associated with SUA Application Servers.

An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing context.

To assign an M3UA or SUA association to multiple routing keys with routing context, the M3UA/SUA association must be assigned to more than one AS and each AS must be assigned to a routing key with routing context.

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.

If the type=default parameter is specified, then the rcontext and asname parameters are the only optional parameters that can be specified.

The following four 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 DPC entered cannot be an APC or SAPC for an IPGWx linkset. Routing keys cannot be provisioned for the fake adjacent node.

AS can be associated to only one routing key that contains a routing context value.

The J7 support feature must be enabled before the dpcn16/opcn16 parameters can be specified.

Mixed point code types are not allowed, the types for the opc and dpc must match.

The routing context value should be unique.

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

The Routing Key table associates a routing key with a socket name or an Application Server (AS).

The routing key can be associated with up to 16 socket names or with 1 AS.

The OPC and DPC cannot specify a cluster route.

Group codes are required for ITU-N point codes and spare point codes (DPCN/OPCN) when the ITU Duplicate Point Code feature (ITUDUPPC) is turned on, and not allowed when the feature is off.

Routing context is a routing key parameter that uniquely identifies routing keys. Routing context is mandatory for routing keys associated with SUA Application Servers and optional for routing keys associated with M3UA Application Servers. An AS cannot be simultaneously assigned to routing keys with routing contexts and routing keys without routing contexts.

An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing contexts.

An AS can be associated with multiple routing keys that do not contain routing context. An AS can be associated with only 1 routing key with routing context.To assign an M3UA or SUA association to multiple routing keys with routing context, the M3UA/SUA association must be assigned to more than one AS and each AS must be assigned to a routing key with routing context.

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

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).

Output

ent-appl-rtkey:dpc=2-2-2:asname=assoc1:type=partial


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

4.281 ent-appl-rtkey