ent-dstn

4.289 ent-dstn

Use this command to add a destination address (a destination point code, capability point code, or network cluster address) and the associated destination attributes to the destination point code table.

Caution:

When using the Network Routing feature, limited network management is provided for point codes not covered by full point code routing, Cluster Routing, or Nested Cluster Routing.

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.

dpc/dpca/dpci/dpcn/dpcn24/dpcn16 (mandatory): Destination point code.

dpc (optional)

ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).

Synonym:

dpca

Range:

p-, 000-255, *

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

prefix—p-

The asterisk value (*) is not valid for the ni subfield.

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.

dpci (optional)

ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).

Range:

s-, p-, ps-, 0-255

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

prefix—s-, p-, ps

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, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, p-, ps-, 0-16383, aa-zz

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

prefix—s-, p-, ps

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 point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix indicates a private point code (prefix-msa-ssa-sp).

Range:

p-, 000-255

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

prefix—p

msa—000–255

ssa—000–255

sp—000–255

Default:

No change to current value.

dpcn16 (optional)

16-bit ITU national point code with subfields unit number sub number area main number area (un-sna-mna). The prefix indicates a private point code (prefix-un-sna-mna).

Range:: p-, 000-127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; prefix-p; un-000-127; sna-000-15; mna-000-31
Default:: No change to the current value.

aliasa/aliasi/aliasn/aliasn24/aliasn16 (optional): Alias point code.

aliasa (optional)

ANSI alias point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). This parameter is not valid if an ANSI (DPC or DPCA) point code is entered.

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.

aliasi (optional)

ITU international alias point code list with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

If an ITU international destination (DPCI) point code is entered, then the dpci and aliasi prefix subfields cannot be the same (both spare or both non-spare). Up to 2 comma-delimited entries can be entered in the point code list.

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.

aliasn (optional)

ITU national alias point code list 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).

If an ITU national destination (DPCN) point code is entered, then the dpcn and aliasn prefix subfields cannot be the same (both spare or both non-spare). Up to 2 comma-delimited entries can be entered in the point code list.

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

aliasn24 (optional)

24-bit ITU national alias point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). This parameter is not valid if a 24-bit ITU national (DPCN24) point code is entered.

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

aliasn16 (optional)

16-bit ITU national alias point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter is not valid if a 16-bit ITU national (DPCN16) point code is entered.

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

bei (optional)

Broadcast exception indicator. This parameter specifies whether the STP broadcasts network management messages to adjacent signaling points.

Note:

The network management messages contain information about the indicated cluster and any of that cluster’s member signaling points that are on its exception list. The messages whose broadcast is determined by this parameter are:

TFP—transfer prohibited
TCP—transfer cluster prohibited
TFA—transfer allowed
TCA—transfer cluster allowed

Range:

yes: Network management messages are not broadcast
no: Network management messages are broadcast

Default:

yes —If the DPC is a member whose associated cluster destination has bei=yes specified.

no —for DPCs in the cluster or if the DPC is a member whose associated cluster destination has bei=no specified or the bei parameter is not specified.

clli (optional)

The Common Language Location Identifier assigned to this destination.

Range:: ayyyyyyyyyy
1 alphabetic character followed by 10 alphanumeric characters
Default:: Null string

domain (optional)

The network in which the destination entity or node exists.

Range:

ss7

Default:

ss7

elei (optional)

Exception-list exclusion indicator, for cluster destinations only. This parameter specifies whether the system excludes or includes (maintains) a dynamic status exception list (x-list) for each cluster route used to reach the member signaling points that make up the cluster.

Range:

yes: Do not maintain a dynamic status x-list
no: Maintain a dynamic status x-list

Default:

homescp (optional)

This parameter specifies whether the destination point code (DPC) is considered a Home SCP when performing SCCP processing for messages with no Global Title Address Digits (Global Title Indicator (GTI) is set to zero)

This parameter can only be set to "yes" for full DPCs.

Range:

yes: the DPC is considered a Home SCP
no: the DPC is not considered a Home SCP

System Default:

homesmsc (optional)

This parameter specifies whether the DPC is considered a Home SMSC when performing SCCP processing for messages with no Global Title Address Digits (GTI is set to zero).

This parameter can only be set to "yes" for full DPCs.

Range:

yes: the DPC is considered a Home SMSC
no: the DPC is not considered a Home SMSC

System Default:

ncai (optional)

Nested cluster allowed indicator. Specifies whether the route to the cluster point code can be different for provisioned members of the cluster. A point code is a member of a cluster point code if it has the same network identifier (NI) and network cluster (NC) values as the cluster point code. This parameter can be specified only for cluster point codes. Nested cluster routing is allowed if this parameter is set to yes and the CRMD and NCR features are turned on.

Range:

yes: The cluster point code is a nested cluster point code. Point codes that are members of this cluster point code can be assigned to route sets that are different from the route set assigned to the cluster point code.
no: The cluster point code is not a nested cluster point code. Point codes that are members of this cluster point code must be assigned to the same route set assigned to the cluster point code.

Default:

nprst (optional)

NM bits reset. This parameter specifies whether the NM bits should be set to 00.

This parameter applies only to ITU IAM messages. The nptype=nm parameter must be specified (see the chg-tifopts command) before this parameter can be specified.

Range:

off: Do not set NM Bits to 00 in an ITU IAM message if the TIFOPTS nptype option value is nm
on: Set the NM Bits to 00 in an ITU IAM message if the TIFOPTS nptype option value is nm

System Default:

off

ppc/ppca/ppci/ppcn/ppcn24/ppcn16 (optional): Proxy point code.
The proxy point code must be a full point code.

ppc (optional)

ANSI proxy point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

The proxy point code must be a full point code.

Synonym:

ppca

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.

ppci (optional)

ITU international proxy 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.

ppcn (optional)

ITU national proxy 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

ppcn24 (optional)

24-bit ITU national proxy 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

ppcn16 (optional)

16-bit ITU national proxy 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

prx (optional)

Proxy point code indicator. This parameter specifies whether a destination is used as a proxy point code.

Range:

yes: The destination is used as a proxy point code.
no: The destination is not used a proxy point code.

Default:

Will not be used as a proxy point code.

rcause (optional)

Release cause. The condition that triggers the sending of a Release message.

Note:

If the rlcopc parameter is specified (see the chg-tifopts command), and a value of 0 - 127 is specified for the rcause parameter, then the rcause parameter value overrides the values specified for the TIFOPTS rcausenp and rcausepfx parameters.

Range:: 0 - 127, none
none —use the values specified for the TIFOPTS table's rcausenp and rcausepfx parameters
System Default:: none

sccpmsgcnv (optional)

SCCP UDT(S)/XUDT(S) Message Conversion Indicator. The type of conversion performed on messages for the specified destination.

Range:

none: conversion is not required on messages for the destination
udt2xudt: convert all UDT(S) messages for the destination to XUDT(S) messages
xudt2udt: convert all non-segmented XUDT(S) messages for the destination to UDT(S) messages
sxudt2udt: convert all segmented and non-segmented XUDT(S) messages for the destination to UDT(S) messages

Default:

none

spc/spca/spci/spcn/spcn24/spcn16 (optional): Secondary point code.

spc (optional)

ANSI secondary point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).

Synonym:

spca

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.

spci (optional)

ITU international secondary point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).

Range:

s-, p-, ps-, 0-255

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

prefix—s-, p-, ps

zone—0-7

area—000-255

id—0-7

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

spcn (optional)

ITU national secondary 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, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, p-, ps-, 0-16383, aa-zz

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

prefix—s-, p-, ps

nnnnn—0-16383

gc—aa-zz

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

spcn24 (optional)

24-bit ITU national secondary point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).

Range:

p-, 000-255

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

prefix—p

msa—000–255

ssa—000–255

sp—000–255

spcn16 (optional)

16-bit ITU national secondary point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix indicates a private point code (prefix-un-sna-mna).

Range:: p-, 000-127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; prefix---p; un--000---127; sna---000---15; mna---000---31

splitiam (optional)

This parameter specifies when and how to split an ITU IAM message into 1 IAM message + 1 SAM message.

This parameter applies only to ITU IAM messages.

Range:

15-31, none

15-31 - Maximum number of CdPN digits allowed in the IAM message before splitting occurs. The remaining digits, up to a total of 32, are encoded in the SAM message.

none -the value specified for the TIFOPTS table's splitiam parameter is used to determine when to split the IAM message

System Default:

none

Example

To add destination 8-1-1 with CLLI of systest1:

ent-dstn:dpc=8-1-1:clli=systest1:bei=yes

To add destination 8 with ITU and national aliases:

ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124

To add cluster 20-2-*:

ent-dstn:dpc=20-2-*:elei=yes:bei=yes

To add a destination with an SPC of 100:

ent-dstn:dpc=20-2-2:spc=100-100-100

To add nested cluster 21-2-*:

ent-dstn:dpc=21-2-*:elei=yes:bei=yes:ncai=yes

To add network routing destination 21-*-*:

ent-dstn:dpc=21-*-*

To add ITU national destination 7654 with a group code of FR and secondary point code of 7050:

ent-dstn:dpcn=7654-fr:spc=7050-fr

To add ITU-N 24-bit destination 15-100-10:

ent-dstn:dpcn24=15-100-10:bei=no

To add a 24-bit ITU-N destination with a 24-bit ITU-N secondary point code of 99:

ent-dstn:dpcn24=12-12-12:spcn24=99-99-99

To add destination 1-6-1 with a 24-bit ITU-N alias:

ent-dstn:dpci=1-6-1:aliasn24=4-4-4

To add private ANSI destination point code p-100-100-101 with spare point code alias s-1-123-1:

ent-dstn:dpca=p-100-100-101:spca=2-2-3:aliasi=s-1-123-1:aliasn=128

To add spare ITU-I destination point code s-2-100-1 with ANSI alias point code 121-120-120 and ITU-N alias spare point code s-129:

ent-dstn:dpci=s-2-100-1:spci=s-2-129-9:aliasa=121-120-120:aliasn=s-129

To add spare ITU-N destination point code s-231 with ITU-N secondary point code 129, ANSI alias point code 120, and ITU-I alias spare point code s-2-123-2:

ent-dstn:dpcn=s-231:spcn=129:aliasa=120-120-122:aliasi=s-2-123-2

To define a destination as a proxy point code:

ent-dstn:dpc=11-11-11:prx=yes

To associate a proxy point code with a destination point code:

ent-dstn:dpc=11-11-11:ppc=2-7-2

To add ITU-I destination point code 3-30-3 with ITU-I spare alias s-3-30-3:

ent-dstn:dpci=3-30-3:aliasi=s-3-30-3

To add ITU-N destination point code 8199-aa with ITU-I aliases s-4-0-7 and 4-0-7:

ent-dstn:dpcn=8199-aa:aliasi=s-4-0-7,4-0-7

To add destination 11 with SCCPMSGCNV type as UDT2XUDT:

ent-dstn:dpc=11-11-11:sccpmsgcnv=udt2xudt

To add ITU-N 16-bit destination 121-10-5:

ent-dstn:dpcn16=121-10-5

Dependencies

Note:

A full point code contains numerical values for all three segments of the point code.

The ANSI self-ID destination point code for the STP must be defined before ANSI destinations can be entered.

The ITU-I self-ID destination point code for the STP must be defined before ITU-I destinations can be entered.

The ITU-N self-ID or SPCN destination point code for the STP must be defined before ITU-N destinations can be entered.

The 24-bit ITU-N self-ID or SPCN24 destination point code for the STP must be defined before 24-bit ITU-N destinations can be entered. (See the chg-sid command.)

The Destination point code table can contain up to 2000 entries.

The destination address must be a full point code or a cluster point code.

The specified destination address cannot already exist in the Destination entity set.

A destination address cannot already be defined as an alias address.

The Spare Point Code Support feature must be enabled before the spare point code prefix (s-) can be specified for an ITU-I or ITU-N destination, secondary, or alias point code.

The specified dpc value cannot match the point code, secondary point code, or capability point code of the system.

A destination can have up to two alias point codes. A destination alias point code type (ANSI, ITU-I, ITU-N, ITU-N24) must not match that destination's true point code type. If both alias point codes are defined, the point code types of the aliases must not match.

Alias point codes are supported only for full point code destinations.

Alias point codes for destinations must be full point codes.

An alias point code cannot already be defined as a destination point code.

The format of the specified dpcn or aliasn parameter must match the format that was assigned with the chg-stpopts:npcfmti parameter.

If the 7000 Routesets or 8000 Routesets feature is enabled, then the total number of provisioned aliases in the system cannot exceed 8000. If the 10,000 Routesets feature is enabled, then the total number of provisioned aliases in the system cannot exceed 10000.

If an ANSI or ITU-I point code is specified, the aliasn or the aliasn24 parameter can be specified, but not both.

A 24-bit ITU-N point code cannot have:

A 14-bit ITU-N alias point code
An ANSI alias point code

A 24-bit ITU-National point code can have an ITU-I point code alias. This allows conversion of 14-bit ITU-I routing label to 24-bit routing label and vice versa.

An ITU-I point code can have either a 14-bit ITU-N alias or a 24-bit ITU-N alias, but not both.

A 14-bit ITU-N point code cannot have a 24-bit ITU-N alias point code.

An ANSI point code cannot have a 24-bit ITU-N alias point code.

The CRMD feature must be turned on before a cluster destination point code (ni-nc-*) can be specified.

A cluster destination cannot be defined using the same network identifier (ni) and network cluster (nc) subfields of any previously defined alias ANSI point codes.

The CRMD (Cluster Routing and Management Diversity) and NCR (Nested Cluster Routing) features must be turned on before the ncai parameter can be specified.

If the ncai=yes parameter is specified, then the maximum number of provisioned nested clusters must be no greater than 500.

When a cluster point code is specified, the collection of signaling points sharing the same network identifier (ni) and network cluster (nc) subfields must have the same route set.

Cluster DPCs are not allowed to inherit cluster members that have routes with A or E linkset types.

Network routing is valid only if the Network Routing (NRT) feature is turned on.

When using network routing, if the destination point code has a value of * in the nc subfield, the ncm subfield must also be * (e.g., dpc=21-*-*).

The ncai parameter can be specified only for cluster destinations.

Alias ANSI point codes cannot have the same network identifier (ni) and network cluster (nc) subfields as a cluster point code that is already defined.

The CRMD feature must be turned on before the elei parameter can be specified.

The elei parameter can be specified only for cluster destinations (e.g., dpc=ni-nc-*).

The CLLI of the destination point code cannot match the CLLI of the system.

A reserved word cannot be specified for the destination identifier (clli).

If the corresponding destination for the specified destination point code is an adjacent signaling point (matched a Far End point code in its linkset entity set), the CLLI of the specified destination point code cannot be assigned to any other destination address.

The value of the dpc parameter must be a valid point code.

If specified, the spc parameter value must be already be configured as a secondary point code in the Secondary Point Code table.

The value specified for the spc parameter must be a full point code.

If the spc parameter is specified, the domain=ss7 parameter must be specified.

If the spc parameter is specified, then the value specified for the dpc parameter must be a full point code.

The network type of the value specified for the spc parameter must match the network type of the value specified for the dpc parameter.

If an ITU national destination is provisioned and the ITUDUPPC feature is turned on, and if the destination does not use an SPC, the group code of the destination must be the same as the group code of the ITU national true point code.

For example, if the ITU national true point code has a group code of ee, then you can add destinations with group codes of ee without using an SPC. Destinations with a group code of ff, however, must use an SPC with a group code of ff.

The Route table cannot be full.

If an ITU national destination is provisioned and the ITUDUPPC feature is turned on, and if the destination uses an SPC, then the group code of the destination must match the group code of the SPC.

The ncai parameter can be specified only for cluster destinations (for example (dpc=ni-nc-*).

The value of the clli parameter cannot already exist in the Route table.

The ICNP feature must be turned on before the icnpxlat, cgpafmt, and cdpafmt parameters can be specified.

The NCR feature must be enabled before the ncai parameter can be enabled.

The MAS configuration table is corrupt or cannot be found.

The route table is corrupt or cannot be found.

If the 6000 Routesets feature is turned on, and the destination point code to be provisioned is above 5000, then the GPSM-II OAM cards must be used.

The alias parameter must be specified with a different point code type than the dpc parameter.

The aliasa and dpca parameters cannot be specified together in the command. The aliasi and dpci parameters and the aliasn and dpcn parameters cannot be specified together in the command if the prefix subfields are the same (both are spare or both are non-spare).

The Proxy Point Code feature must be enabled before the prx=yes parameter can be specified.

The Proxy Point Code feature must be enabled before the ppc parameter can be specified.

If the ppc parameter or the prx=yes parameter is specified, then the value specified for the dpc parameter must be a full point code.

The spc and ppc parameters cannot be specified together in the command.

The values specified for the dpc and ppc parameters must have the same network type.

The values specified for the dpc and ppc parameters must have the same group code.

The number of proxy destinations cannot exceed the value given by the enabled Proxy Point Code quantity feature.

If the value of the dpc parameter is a private point code, then the prx=yes parameter cannot be specified.

If the value of the dpc parameter is a private point code, then the ppc parameter cannot be specified.

The dpc parameter and the prx=yes parameter must be specified before the ppc parameter can be specified.

The total number of proxy destinations cannot exceed the total capacity (100) of the Proxy Point Code feature.

The prx parameter must have a value of yes or no.

Cluster destination point codes cannot inherit cluster members that have routes using proxy linksets.

The spare ITU-I self-ID destination point code for the STP must be defined before spare ITU-I destinations can be entered.

The spare ITU-N self-ID destination point code for the STP must be defined before spare ITU-N destinations can be entered.

A maximum of two aliases can be specified per destination point code.

If the dpci parameter is specified, then a combination of ITUI and ANSI aliases cannot be specified. If the dpcn parameter is specified, then a combination of ITUN and ANSI aliases cannot be specified.

Two ITUI or two ITUN aliases can be specified for the same destination point code only if the aliases have different prefixes. One alias must be spare and one non-spare.

The TIF Number Portability feature must be enabled before the rcause or nprst parameter can be specified.

A TIF feature must be enabled before the splitiam parameter can be specified.

The XUDT UDT Conversion feature must be turned on before the sccpmsgcnv parameter can be specified.

The value specified for the ppc parameter must already exist in the DSTN table and the prx=yes parameter must be assigned.

ITU-N16 destination cannot be provisioned if ITU-N16 site id is not provisioned.

The J7 Support feature must be enabled before the aliasn16 parameter can be specified.

If the J7 Support feature is enabled then the aliasa and aliasn24 parameters cannot be specified.

Spare point codes for aliasn 1 and aliasn 2 must be different, and spare point codes for aliasi 1 and aliasi 2 must be different.

Notes

Upon initial installation of the system, the self point code must be entered before you enter any destination.

When you define a DPC with the unique destination signaling point of a provisioned cluster, the DPC automatically inherits the route set of its cluster if the ncai=no parameter is specified. If the ncai=yes parameter is specified, the provisioned members can have a different route set.

When you define a cluster point code for previously defined destination signaling points, the cluster automatically inherits the unique route set of its members.

For ITU national duplicate point codes, you cannot change a destination’s group code. To move a destination from one group to another, provision a new destination that uses the new group code and delete the old destination.

The system requires that the destination point code of each routeset be entered in the database. For example, to enter 6000 routesets in the database, 6000 destination point codes must be entered in the database.

If you have turned on the 5000 Routes feature, prior to provisioning the additional routing table entries, you must issue the chg-stpopts command to specify the maximum number of allowed DPCs and dynamic x-list entries.

If the 6000, 7000, 8000, or 10,000 Routesets feature is enabled, then in order to enter more than 2000 destination point codes, the maximum number of point codes that can be configured on the system must be changed to 6000, 7000, 8000, or 10000 respectively, using the mtpdpcq parameter of the chg-stpopts command.

In this command, only ITU-international and ITU national point codes and aliases support the spare point code subtype prefix (s-). Only ITU-international and ITU national point codes support the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-). Aliases do not support the private (internal) point code prefix.

If the Proxy Point Code feature is enabled, then the value specified for the ppc or dpc parameter (when the destination point code is designated as a proxy point code) must be full point codes. Cluster point codes and private point codes are not supported.

One of dpc/dpca/dpci/dpcn/dpcn24/dpcn16 is mandatory and they are mutually exclusive.

Only one of aliasa/aliasi/aliasn/aliasn24/aliasn16 can be specified as they are mutually exclusive.

Only one of spc/spca/spci/spcn/spcn24/spcn16 can be specified as they are mutually exclusive.

Output

This example shows the output with the NCR, NRT, and CRMD features off and all Routes and Routesets features off:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-17 15:35:05 EST  EAGLE 31.8.0
    Destination table is (10 of 2000) 1% full 
    Alias table is (8 of 12000) 1% full
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output with the NCR, NRT, and CRMD features off and the DSTN5000 (5000 Routes) feature on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    Destination table is (10 of 5000) 1% full
    Alias table is (8 of 12000) 1% full
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output with one or more of the NCR, NRT, or CRMD features on and the DSTN5000 (5000 Routes) feature on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    DESTINATION ENTRIES ALLOCATED:   5000
        FULL DPC(s):                    9
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  10
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   8
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output with the NCR, NRT, and CRMD features off and the 6000 Routesets feature on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    Destination table is (60 of 6000) 1% full
    Alias table is (8 of 12000) 1% full
    ENT-DSTN: MASP A - COMPLTD 
;

Thus example shows the output with one or more of the NCR, NRT, or CRMD features on and the 6000 Routesets feature on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    DESTINATION ENTRIES ALLOCATED:   6000
        FULL DPC(s):                   46
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  12
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   8
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output with the NCR, NRT, and CRMD features off. When the 7000 Routesets quantity feature is on, the Destination table line shows "...of 7000". When the 8000 Routesets quantity feature is on, the Destination table line shows "...of 8000."

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    Destination table is (60 of 7000) 1% full
    Alias table is (8 of 8000) 1% full
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output with one or more of the NCR, NRT, or CRMD features on. When the 7000 Routesets quantity feature is on, the DESTINATION ENTRIES ALLOCATED line shows "7000". When the 8000 Routesets quantity feature is on, the DESTINATION ENTRIES ALLOCATED line shows "8000."

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 04-08-18 08:29:15 EST  EAGLE 31.8.0
    DESTINATION ENTRIES ALLOCATED:   8000
        FULL DPC(s):                    9
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  10
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                   8
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output when none of the NCR, NRT, or CRMD features on. A destination is defined as a proxy point code.

 ent-dstn:dpc=11-11-11:prx=yes


    tekelecstp 07-03-07 16:34:32 EST  EAGLE 37.5.0
    Destination table is (11 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (2 of 10) 20% full
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output when one or more of the NCR, NRT, or CRMD features are on. The destination refers to a proxy point code.

 ent-dstn:dpc=1-1-1:ppc=11-11-11


    tekelecstp 07-03-05 17:34:18 EST  EAGLE 37.5.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   27
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 1
        Proxy DPC(s):                   1
        TOTAL DPC(s):                  30
        CAPACITY (% FULL):              2%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   0
        CAPACITY (% FULL):              0%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output when the NCR, NRT, and CRMD features are off and the 10,000 Routesets feature is on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 10-08-17 08:29:15 EST  EAGLE 43.0.0
    Destination table is (10 of 10000) 1% full
    Alias table is (8 of 10000) 1% full
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output when one or more of the NCR, NRT, or CRMD features and the 10,000 Routesets feature is on:

 ent-dstn:dpc=8-8-8:aliasi=1-2-3:aliasn=124


    rlghncxa03w 10-08-17 08:29:15 EST  EAGLE 43.0.0
    DESTINATION ENTRIES ALLOCATED:   10000
        FULL DPC(s):                    9
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  10
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               10000
        ALIASES USED:                   8
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD 
;

This example shows the output when the J7 feature is enabled:

ent-dstn:dpci=1-2-6:aliasn16=2-4-6


    tekelecstp 13-02-27 13:58:55 EST  45.0.0-64.56.0
    ent-dstn:dpc=1-2-6:aliasn16=2-4-6
    Command entered at terminal #4.
    Destination table is (2 of 2000) 1% full
    Alias table is (1 of 12000) 0% full

    ENT-DSTN: MASP A - COMPLTD
;

Related Topics