Adding a Destination Point Code

This procedure is used to add a destination point code to the database, using the ent-dstn command.

The ent-dstn command uses these parameters:

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code being added to the database

:aliasa/aliasi/aliasn/aliasn24 – The alternate destination point code. Two optional alias addresses can be defined.

:ppc/ppca/ppci/ppcn/ppcn24 – The proxy point code that is assigned to the destination point code.

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes. A private point code cannot be used as an alias point code.

:clli – The Common Language Location Identifier assigned to this point code

:domain – The network in which the destination entity or node exists, SS7.

:ipgwapc – IP Gateway Adjacent Point Code indicator. Specify ipgwapc=yes to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. The default is ipgwapc=no.

:bei – Broadcast exception indicator that indicates whether transfer-prohibited (TFP) messages will be broadcast from this node. The bei=yes parameter means TFPs will not be broadcast. The bei=no parameter means TFPs will be broadcast.

:spc/spca/spci/spcn/spcn24 – The secondary point code as defined by the ent-spc command. The secondary point code allows the EAGLE to use another point code in addition to the one defined by the dpc, dpca, dpci, dpcn, or dpcn24 parameters of the ent-dstn command for SS7 routing purposes. Refer to the Multiple Point Code Support section for more information on secondary point codes. A private point code cannot be used as a secondary point code.

:prx – This parameter specified whether or not the destination point code is proxy point code. This parameter has two values, yes or no. If the prx parameter value is yes, the destination point code is a proxy point code. If the prx parameter value is no, the destination point code is not a proxy point code.

The ppc and prx parameters can be specified only if a quantity of proxy point codes is enabled. Proxy point code quantities are enabled in groups of 10. The enabled quantity of proxy point codes is shown in the rtrv-ctrl-feat output. If no proxy point code quantity is shown in the rtrv-ctrl-feat output, or the proxy point code quantity needs to be increased, up to a maximum quantity of 100 proxy point codes, perform the Changing the Proxy Point Code Quantity procedure.

The ppc parameter assigns a proxy point code to a destination point code. The proxy point code value must be provisioned in the database. The destination point code must be a full point code, in the SS7 domain, and cannot be a private point code. The destination point code cannot have the ipgwapc=yes parameter value assigned. The destination point code and proxy point code must be the same network type. For example, if the destination point code is an ANSI point code, the proxy point code must be an ANSI point code. If the destination point code and proxy point code are 14-bit ITU-N point codes with a group code, the group code values for both the destination point code and the proxy point code must be the same. The spc and ppc parameters cannot be specified together in the same ent-dstn command line.

The prx parameter specifies whether or not the destination point code specified with the ent-dstn command is a proxy point code. The destination point code value must be a full point code, in the SS7 domain, and cannot be a private point code. The destination point code value cannot have the ipgwapc=yes parameter value assigned.

:nprst - NM bits reset. This parameter specifies whether the NM bits in an ITU IAM message should be set to 00. This parameter has two values.

off - Do not set NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.
on - Set the NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.
The default value for this parameter is off.

:rcause - Release cause. This parameter specifies the condition that triggers the sending of a Release message. This parameter has these values.

0 - 127
none - use the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.
The default value for this parameter is none.

If the rlcopc parameter value in the rtrv-tipopts output is on and a value of 0-127 is specified for the rcause parameter, then the rcause parameter value overrides the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.

:splitiam - This parameter specifies how and when to split an ITU IAM message into one IAM message and one SAM message. This parameter has these values.

15-31 - The maximum number of CdPN digits allowed in the IAM message before the splitting occurs. The remaining digits, up to a total of 32, are encoded in the SAM message.
none - the value specified for the splitiam parameter in the rtrv-tifopts output is used to determine when to split the IAM message.
The default value for this parameter is none.

To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

TIF Number Portability - part number 893018901
TIF SCS Forwarding - part number 893022201
TIF Simple Number Substitution - part number 893024001
TIF Additional Subscriber Data - part number 893024501
TIF Generic Routing Number - part number 893025501
The status of these features is shown in the rtrv-ctrl-feat output. Perform the procedures in TIF User's Guide to enable these features.

:homescp - This parameter specifies whether the destination point code should be considered a home SCP when performing SCCP processing for messages that have no global title address digits (the global title indicator (GTI) is set to zero). This parameter cannot be specified for a cluster point code or a network routing point code. These are the values for this parameter.

yes- the specified DPC is considered a home SCP.
no - the specified DPC is not considered a home SCP. This is the default value.

:homesmsc - This parameter specifies whether the destination point code (DPC) should be considered a home SMSC when performing SCCP processing for messages that have no global title address digits (the global title indicator (GTI) is set to zero). This parameter cannot be specified for a cluster point code or a network routing point code. These are the values for this parameter.

yes- the specified DPC is considered a home SMSC.
no - the specified DPC is not considered a home SMSC. This is the default value.

:sccpmsgcnv - The sccpmsgcnv parameter controls SCCP UDT(S)/XUDT(S) message conversion for the specified destination. This parameter can be specified only if the XUDT UDT Conversion feature is enabled and turned on. The rtrv-ctrl-feat output shows the status of the XUDT UDT Conversion feature. If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature. This parameter contains these values.

none - SCCP UDT(S)/XUDT(S) message conversion is not required on messages for the destination. This value is the default value for this parameter.
udt2xudt - All UDT(S) messages for the destination are converted to XUDT(S) messages.
xudt2udt - All non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages. Segmented XUDT(S) messages for the destination are not converted to UDT(S ) messages.
sxudt2udt - All segmented and non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages.

The elei and ncai parameters cannot be specified in this procedure. To use these parameters to provision a destination point code, perform the Adding a Cluster Point Code procedure.

Secondary point codes must be a full point code. A secondary point code can only be assigned to a full point code. The network type of the secondary point code must match the network type of the DPC. The secondary point code used in this procedure must be configured in the database with the ent-spc command. The secondary point codes are shown in the SPCA, SPC-I, SPC-N, and SPC-N24 fields of the rtrv-spc command output. If the desired secondary point code is not shown in the output of the rtrv-spc command, perform the Adding a Secondary Point Code procedure to configure the desired point code as a secondary point code.

The value of the clli parameter cannot be in the DPC table and cannot match the CLLI of the EAGLE. Verify this by entering the rtrv-dstn and the rtrv-sid commands, shown in steps 1 and 5 of the procedure that follows. If the value of the clli parameter matches any CLLI values in either of these outputs, choose another value for the clli parameter that does not match any CLLIs shown in either of these command outputs.

To enter point codes of any network type (ANSI, ITU-I, 14-bit ITU-N, or 24-bit ITU-N) into the database with the ent-dstn command, the self ID of the EAGLE must be defined for these networks. Verify this with the rtrv-sid command.

If a point code value is shown in the PCA column of the rtrv-sid command, then ANSI point codes can be specified with the ent-dstn command.

If a point code value is shown in the PCI column of the output of the rtrv-sid command, then ITU-I point codes can be specified with the ent-dstn command. The PCI column of the rtrv-sid output can contain spare and non-spare point code values. To provision ITU-I non-spare point codes in this procedure, the rtrv-sid output must contain an ITU-I non-spare point code in the PCI column. To provision ITU-I spare point codes in this procedure, the rtrv-sid output must contain an ITU-I spare point code in the PCI column.

If a point code value is shown in the PCN column of the output of the rtrv-sid command, then 14-bit ITU-N point codes can be specified with the ent-dstn command. The PCN column of the rtrv-sid output can contain spare and non-spare point code values. To provision 14-bit ITU-N non-spare point codes in this procedure, the rtrv-sid output must contain a 14-bit ITU-N non-spare point code in the PCN column. To provision 14-bit ITU-N spare point codes in this procedure, the rtrv-sid output must contain a 14-bit ITU-N spare point code in the PCN column.

If a point code value is shown in the PCN24 column of the output of the rtrv-sid command, then 24-bit ITU-N point codes can be specified with the ent-dstn command.

If no values are shown in the PCA, PCI, PCN, or PCN24 columns in the rtrv-sid command output, the self-identification of the EAGLE must be updated with an ANSI point code, ITU international point code, 14-bit ITU national point code, or a 24-bit ITU national point code. Perform the Adding a Point Code to the Self-Identification of the EAGLE procedure to add the necessary point codes to the self-identification of the EAGLE.

Note:

The EAGLE can contain 14-bit ITU national point codes or 24-bit ITU national point codes, but both at the same time.

Private point codes cannot be specified in the self-identification of the EAGLE, therefore, private point codes can be added as long as the self identification of the EAGLE contains a point code with the same network type as the private point code being added in this procedure. The ITU National and International Spare Point Code Support feature does not have to be enabled to add a private point code. A proxy point code cannot be used as a value when specifying a private point code.

The type of alias point code that can be provisioned with the ent-dstn command is dependent on the type of DPC that is being provisioned. Table 2-15 shows the DPC and alias point type combinations that can be used with the ent-dstn command.

Table 2-15 Destination Point Code Type and Alias Point Code Type Combinations

DPC Type	Alias Point Code Type (See Notes 1 - 4)	Alias Point Code Type (See Notes 1 - 4)	DPC TYPE	Alias Point Code Type (See Notes 1 - 4)	Alias Point Code Type (See Notes 1 - 4)
ANSI	no alias specified	no alias specified	ITU-I	no alias specified	no alias specified
	ITU-I	no alias specified		ANSI	no alias specified
	ITU-I	ITU-N		ANSI	ITU-N
	ITU-I	ITU-N Spare		ANSI	ITU-N Spare
	ITU-I	ITU-N24		ANSI	ITU-N24
	ITU-I Spare	no alias specified		ITU-I Spare	no alias specified
	ITU-I Spare	ITU-N		ITU-I Spare	ITU-N
	ITU-I Spare	ITU-N Spare		ITU-I Spare	ITU-N Spare
	ITU-I Spare	ITU-N24		ITU-I Spare	ITU-N24
	ITU-N	no alias specified		ITU-N	no alias specified
	ITU-N Spare	no alias specified		ITU-N (Note 6)	ITU-N Spare (Note 6)
	ITU-N24	no alias specified		ITU-N Spare	no alias specified
ITU-I Spare	no alias specified	no alias specified		ITU-N24	no alias specified
	ANSI	no alias specified	ITU-N	no alias specified	no alias specified
	ANSI	ITU-N		ANSI	no alias specified
	ANSI	ITU-N Spare		ANSI	ITU-I
	ANSI	ITU-N24		ANSI	ITU-I Spare
	ITU-I	no alias specified		ITU-I	no alias specified
	ITU-I	ITU-N		ITU-I (Note 5)	ITU-I Spare (Note 5)
	ITU-I	ITU-N Spare		ITU-I Spare	no alias specified
	ITU-I	ITU-N24		ITU-N Spare	no alias specified
	ITU-N	no alias specified		ITU-N Spare	ITU-I
	ITU-N (Note 6)	ITU-N Spare (Note 6)		ITU-N Spare	ITU-I Spare
	ITU-N Spare	no alias specified	ITU-N24	no alias specified	no alias specified
	ITU-N24	no alias specified		ANSI	no alias specified
ITU-N Spare	no alias specified	no alias specified		ANSI	ITU-I
	ANSI	no alias specified		ANSI	ITU-I Spare
	ANSI	ITU-I		ITU-I	no alias specified
	ANSI	ITU-I Spare		ITU-I Spare	no alias specified
	ITU-I	no alias specified
	ITU-I (Note 5)	ITU-I Spare (Note 5)
	ITU-I Spare	no alias specified
	ITU-N	no alias specified
	ITU-N	ITU-I
	ITU-N	ITU-I Spare
Notes: ANSI alias point codes are specified with the`aliasa` parameter. ITU-I and ITU-I Spare alias point codes are specified with the`aliasi` parameter. ITU-N and ITU-N Spare alias point codes are specified with the`aliasn` parameter. ITU-N24 alias point codes are specified with the`aliasn24` parameter. To specify the ITU-I and ITU-I Spare alias point codes for the DPC, both point code values are specified with the`aliasi` parameter and the values are separated by a comma. For example, to specify the alias point codes 2-005-7 and s-3-002-1, the aliasi parameter is specified like this;`aliasi=2-005-7,s-3-002-1`. The`aliasa` and`aliasn` parameters cannot be specified for the DPC. To specify the ITU-N and ITU-N Spare alias point codes for the DPC, both point code values are specified with the`aliasn` parameter and the values are separated by a comma. For example, to specify the alias point codes 00010 and s-00020, the aliasn parameter is specified like this;`aliasn=00010,s-00020`. The`aliasa` and`aliasi` parameters cannot be specified for the DPC.

Alias point codes can only be specified for full point code entries, and must be full point codes.

ANSI alias point codes cannot be a member of a cluster point code that is already in the database. 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.

The EAGLE can contain the quantities of alias point codes shown in Table 2-16 depending the features that are enabled or turned on.

Table 2-16 Maximum Alias Point Code Quantities

Feature Status	Maximum Alias Point Code Quantity
The 5000 Routes feature is off and 6000, 7000, 8000, or 10,000 routesets are not enabled	12000
The 5000 Routes feature is on and 6000, 7000, 8000, or 10,000 routesets are not enabled	12000
6000 routesets are enabled	12000
7000 routesets are enabled	8000
8000 routesets are enabled	8000
10,000 routesets are enabled	10000

Destination point codes and alias point codes must be unique in the database. A point code can be defined as a true destination point code, an alias point code, the self ID of the EAGLE, or the capability point code of the EAGLE. The self IDs and capability point codes of the EAGLE can be verified with the rtrv-sid command.

If the PCTYPE field of the rtrv-sid command output contains the entry ANSI, and the network value of the destination point code specified by the ent-dstn command is from 0 to 5, the cluster value of that point code must be from 1 to 255. If the network value of that point code is from 6 to 255, the cluster value of that point code must be from 0 to 255.

The actual number of destination point codes that can be configured in the database is set by the mtpdpcq parameter of the chg-stpopts command, and is shown in the MTPDPCQ field in the rtrv-stpopts command output.

If the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled, a maximum of 2000 destination point codes can be configured in the database.

If the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled, a maximum of 5000 destination point codes can be configured in the database.

If 6000 routesets are enabled, a maximum of 6000 destination point codes can be configured in the database.

If 7000 routesets are enabled, a maximum of 7000 destination point codes can be configured in the database.

If 8000 routesets are enabled, a maximum of 8000 destination point codes can be configured in the database.

If 10,000 routesets are enabled, a maximum of 10,000 destination point codes can be configured in the database.

Note:

For more information on the destination point code quantities, refer to the Changing the DPC Quantity procedure.

If ITU-N point codes are specified with the ent-dstn command, the format of the point code values must match the format shown in the NPCFMTI field of the rtrv-stpopts command output. For more information, refer to the 14-Bit ITU National Point Code Formats section.

Canceling the RTRV-DSTN Command

Because the rtrv-dstn command used in this procedure can output information for a long period of time, the rtrv-dstn command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-dstn command can be canceled:

Press the F9 function key on the keyboard at the terminal where the rtrv-dstn command was entered
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-dstn command was entered
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-dstn command was entered, from another terminal other than the terminal where the rtrv-dstn command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, refer to Commands User's Guide.

Display the current destination point codes, using the rtrv-dstn command.

This is an example of the possible output.

rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   001-002-003   ls04clli    yes --- ----------      --------------   SS7
   030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
   111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
   240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3-fr  SS7
   240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0-ge SS7
   240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1-fr SS7
   240-012-008   ----------- yes ---    1-113-5         10-13-10-2-ge SS7

   DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
   2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1-ge  SS7
   2-131-2       ----------- no  ---    222-211-001     11-11-8-2-fr  SS7
   2-131-3       ----------- no  ---    222-211-002     11-11-8-3-ge  SS7

   DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
   10-15-2-3-fr  rlghncbb013 no  ---    222-200-200     2-121-1       SS7
   10-15-2-3-ge  rlghncbb013 no  ---    222-100-200     2-100-1       SS7
   10-15-3-0-fr  rlghncbb013 no  ---    222-200-201     2-121-2       SS7
   10-15-3-0-ge  rlghncbb013 no  ---    222-100-201     2-100-2       SS7

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   18
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    TOTAL DPC(s):                  20
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  22
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

If a quantity of proxy point codes is enabled, the number of proxy point codes that are provisioned in the database are shown at the end of the rtrv-dstn output as shown in this example.

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   18
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC (s)                   1
    TOTAL DPC(s):                  20
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  22
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

To add the new DPC, these entities must be checked depending on how the DPC will be provisioned.
Perform the commands and procedures as required depending on how the DPC will be provisioned.

The addition of the new DPC cannot exceed the current capacity shown in the DESTINATION ENTRIES ALLOCATED or the Destination table row of the rtrv-dstn output. If the current capacity will be exceeded by adding the new DPC, and the maximum capacity is shown in the rtrv-dstn output: 10,000 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED rows are not shown in the rtrv-dstn output, or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED rows are shown in the rtrv-dstn output, perform Removing a Destination Point Code or Removing a Route Exception Entry to remove an existing DPC or exception route entry.

If the maximum capacity is not shown in the rtrv-dstn output, perform Changing the DPC Quantity to increase the number of DPCs that can be in the database.

The type of point code being added, ANSI, ITU-I, ITU-N, ITU-N24 must be shown in the rtrv-dstn output or the rtrv-sid output. If the point code type is not shown in the rtrv-dstn output, perform the rtrv-sid command in 3. If the point code type is not shown in rtrv-dstn and rtrv-sid, perform Adding a Point Code to the Self-Identification of the EAGLE to add a point code of the desired point code type.

If the new DPC will be a 14-bit ITU-N point code, and a group code will be assigned to the point code, the group code must be defined in rtrv-sid output in 3, rtrv-dstn output in 1, or rtrv-spc output in 4. If the group code is not shown in either of these outputs, perform Adding a Point Code to the Self-Identification of the EAGLEto add an entry with the desired group code. If the group code will be different from the ones shown in the rtrv-sid or rtrv-dstn outputs, perform Adding a Secondary Point Code to add a secondary point code with the desired group code.

If a secondary point code will be specified with the DPC, the secondary point code must be shown in the rtrv-spc output in 4. It the secondary point code is not shown in the rtrv-spc output, performAdding a Secondary Point Code to add the desired secondary point code.

If the clli parameter will be specified with the DPC, the clli parameter value cannot be shown in the rtrv-sid or rtrv-dstn outputs. Enter the rtrv-sid command in 3 to verify the CLLI value in the self-identification of the EAGLE.

The format of a 14-bit ITU-N DPC must match the format defined by the NPCFMTI value in the rtrv-stpopts output. Enter the rtrv-stpopts in 5 to verify the NPCFMTI value. If you wish to change the format, perform 14-Bit ITU National Point Code Formats.

To specify an alias point code with the DPC, adding the new alias point code cannot exceed the maximum alias point code quantity shown in the ALIASES ALLOCATED: or the Alias table row in the rtrv-dstn output. If the maximum alias point code quantity will be exceeded, perform Changing a Destination Point Code to remove enough alias point codes to allow the new alias point code to be added.

If the nprst or rcause parameters will be specified with the DPC, the TIF Number Portability feature must be enabled. Enter the rtrv-ctrl-feat command in 6 to verify that the feature is enabled. If the feature is not enabled, perform the procedures in TIF User's Guide to enable the TIF Number Portability feature.
If the splitiam parameter will be specified with the DPC, at least one of these features must be enabled.
- TIF Number Portability
- TIF SCS Forwarding
- TIF Simple Number Substitution
- TIF Additional Subscriber Data
- TIF Generic Routing Number
  Enter the rtrv-ctrl-feat command in 6 to verify if any of these features are enabled.
  
  If none of these features are enabled, perform the procedures in TIF User's Guide to enable one of more of these features.
If the prx=yes or ppc parameters will be specified with the DPC, the Proxy Point Code feature must be enabled. The addition of the proxy point code with the prx=yes parameter cannot exceed the enabled proxy point code quantity, shown in the PPC table or PROXY DPC(s): row of the rtrv-dstn output. Enter the rtrv-ctrl-feat command in 6 to verify if a proxy point code quantity is enabled. If a proxy point code quantity is enabled, the Proxy Point Code feature is enabled. To enable the Proxy Point Code feature or increase the proxy point code quantity, perform Changing the Proxy Point Code Quantity. If the enabled quantity is 100, and 100 proxy point codes are in the database, no more proxy point codes can be added.

The ppc parameter assigns an existing proxy point code to the DPC. Enter the rtrv-dstn:prx=yes command in 7 to verify that the proxy point code is in the database.

The sccpmsgcnv parameter specifies the kind of conversion performed on messages for the specified destination. This parameter can be specified only if the XUDT UDT Conversion feature is enabled and turned on. Enter the rtrv-ctrl-feat command in 6 to verify that the XUDT UDT Conversion feature is enabled and turned on. If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

After the required entities have been verified and provisioned, continue the procedure with 8.

Display the self-identification of the EAGLE using the rtrv-sid command.

This is an example of the possible output.

rlghncxa03w 06-10-10 11:43:04 GMT  EAGLE5 36.0.0
   PCA             PCI          PCN                CLLI              PCTYPE
   100-100-100     3-75-7       7-9-8-1-fr         rlghncxa03w       OTHER

   CPCA
   002-002-002       002-002-003       002-002-004      002-002-005
   002-002-006       002-002-007       002-002-008      002-002-009
   004-002-001       004-003-003       050-060-070

   CPCA (LNP)
   005-005-002       005-005-004       005-005-005

   CPCI
   1-002-1           1-002-2           1-002-3          1-002-4
   2-001-1           7-222-7

   CPCN
   2-0-10-3-fr       2-0-11-0-fr       2-0-11-2-fr      2-0-12-1-fr
   2-2-3-3-fr        2-2-4-0-fr        10-14-10-1-fr

Display the secondary point codes in the database with the rtrv-spc command.

This is an example of the possible output.

rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0
SPC (Secondary Point Codes)
SPCA
     001-010-010
     002-010-010
     003-010-010
     010-100-010
SPC-I
         1-253-5
         2-254-6
         3-255-7
         4-100-1
SPC-N
        10-1-11-1-ge
        13-2-12-0-ge
        14-15-12-1-ge
SPC-N24
none
Secondary Point Code table is (11 of 40) 28% full

Display the existing values for the npcfmti parameter by entering the rtrv-stpopts command.
The value for the npcfmti parameter is shown in the NPCFMTI field. This is an example of the possible output.
```
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0
STP OPTIONS
-----------------------
NPCFMTI        4-4-4-2
```
Note:
Thertrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-stpopts command, see thertrv-stpopts command description in Commands User's Guide.

Display the features that are enabled by entering the rtrv-ctrl-feat command..

The following is an example of the possible output.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Command Class Management  893005801  on      ----
LNP Short Message Service 893006601  on      ----
Intermed GTT Load Sharing 893006901  on      ----
XGTT Table Expansion      893006101  on      4000000
XMAP Table Expansion      893007710  on      3000
Large System # Links      893005901  on      1500
Routesets                 893006401  on      6000
HC-MIM SLK Capacity       893012707  on      64

The following features have been temporarily enabled:

Feature Name              Partnum   Status  Quantity     Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.

Display the proxy point codes in the database by entering this command.
rtrv-dstn:prx=yes

This is an example of the possible output.
```
rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0

PRX = yes

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24   DMN
   002-002-002   ----------- no  --- ----------      --------------   SS7

Destination table is (18 of 2000) 1% full
Alias table is (22 of 8000) 1% full
PPC table is (1 of 10) 10% full
```
If the desired proxy point code is shown in the rtrv-dstn output, perform 8.c of 8 to assign the proxy point code to the destination point code with the ppc parameter.

If the desired proxy point code is not shown in the rtrv-dstn output, add the proxy point code by performing 8.b of 8 with the prx=yes parameter. After the new proxy point code has been added, perform 8.c of 8 again to assign the proxy point code to the destination point code with the ppc parameter.
Add the destination point code, using the ent-dstn command.
- If proxy point codes are not being provisioned in this procedure, perform 8.a.
- If a new proxy point code is being provisioned with the prx=yes parameter, perform 8.b.
- If a proxy point code is being assigned to a destination point code, perform 8.c.
1. Add the destination point code to the database without specifying the prx or ppc parameters. If alias point codes will be assigned to the DPC, Table 2-15 shows the DPC and alias point type combinations that can be used with the ent-dstn command.
  
  ent-dstn:dpca=240-012-007:bei=yes:aliasi=1-117-3:aliasn=10-13-11-1-fr :spca=001-010-010:homescp=yes:homesmsc=yes:sccpmsgcnv=xudt2udt
  
  ent-dstn:dpca=240-012-006:spca=002-010-010
  
  ent-dstn:dpci=4-163-5:bei=no:aliasa=250-200-007:domain=ss7:spci=2-254-6
  
  ent-dstn:dpcn=7-9-10-1-fr:bei=no:aliasa=210-090-100 :aliasi=1-75-6:domain=ss7
  
  ent-dstn:dpcn=7-9-10-1-ge:bei=no:aliasa=210-100-100:aliasi=2-175-6 :domain=ss7:spcn=13-02-12-0-ge
  
  ent-dstn:dpci=3-002-1:aliasn=9-12-2-1-fr,s-8-11-3-0-ge
  
  ent-dstn:dpcn=10-11-1-3-fr:aliasi=3-125-0,s-4-135-3
  
  ent-dstn:dpcn=6-10-7-9-ge:bei=no:aliasa=211-100-100:aliasi=3-175-6 :spcn=13-02-12-1-ge:rcause=15:nprst=on:splitiam=20
2. To add a new proxy point code to the database, specify the ent-dstn command with the prx=yes parameter.
  
  For this example, enter this command.
  
  ent-dstn:dpca=003-003-003:prx=yes
  
  Note:
  The point code being added as a proxy point code must be a full point code, in the SS7 domain, and cannot be a private point code. The point code cannot have the ipgwapc=yes parameter value assigned.
3. To assign a proxy point code to a destination point code, specify the ent-dstn command with the ppc parameter.
  For this example, enter this command.
  
  ent-dstn:dpca=004-004-004:ppca=003-003-003
  
  The following rules apply to assigning proxy point codes to destination point codes.
  - The destination point code must be a full point code and cannot be a private point code.
  - The destination point code cannot have the ipgwapc=yes parameter value assigned.
  - The destination point code and proxy point code must be the same network type. For example, if the destination point code is an ANSI point code, the proxy point code must be an ANSI point code.
  - If the destination point code and proxy point code are 14-bit ITU-N point codes with a group code, the group code values for both the destination point code and the proxy point code must be the same.
When the ent-dstn command has successfully completed, and the Cluster Routing and Management Diversity feature is turned off (shown with the CRMD = off entry in the rtrv-feat command output), and no proxy point code quantity is enabled, this message should appear.
```
rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
Destination table is (27 of 2000) 1% full 
Alias table is (27 of 12000) 1% full
ENT-DSTN: MASP A - COMPLTD
```
If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), and no proxy point code quantity is enabled, this message should appear.
```
rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   27
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  31
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
ENT-DSTN: MASP A - COMPLTD
```
If a proxy point code quantity is enabled and the Cluster Routing and Management Diversity feature is turned off (shown with the CRMD = off entry in the rtrv-feat command output), this message should appear.
```
rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
Destination table is (29 of 2000) 1% full 
Alias table is (27 of 12000) 1% full
PPC table is (2 of 10) 20% full
ENT-DSTN: MASP A - COMPLTD
```
If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), and a proxy point code quantity is enabled, this message should appear.
```
rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
ENT-DSTN: MASP A - COMPLTD
```

Verify the changes using the rtrv-dstn command with the DPC that was entered in 8.

For this example, enter these commands.

rtrv-dstn:dpca=240-012-007

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   240-012-007   ----------- yes ---    1-117-3         10-13-11-1-fr SS7

   SPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   001-010-010  ---- no      none   off   none     yes    yes   xudt2udt

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpca=240-012-006

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1-fr SS7

   SPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   002-010-010  ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpci=4-163-5

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
   4-163-5       ----------- no  ---    250-200-007  --------------   SS7

   SPCI         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   2-154-6      ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpcn=7-9-10-1-fr

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
   7-9-10-1-fr   ----------- no  ---    210-090-100     1-75-6        SS7

   SPCN         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpcn=7-9-10-1-ge

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
   7-9-10-1-ge   ----------- no  ---    210-100-100     2-175-6       SS7

   SPCN          NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   13-02-12-0-ge ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpca=003-003-003

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   003-003-003   ----------- no  --- ----------      --------------   SS7

   SPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ---- yes, 1  none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpca=004-004-004

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   004-004-004   ----------- no  --- ----------      --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   003-003-003  ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpci=3-002-1

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCI          CLLI        BEI ELEI    ALIASN          ALIASN       DMN
   3-002-1       ----------- no  ---     9-12-2-1-fr   s-8-11-3-0-ge  SS7

   SPCI         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpcn=10-11-1-3-fr

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCN          CLLI        BEI ELEI    ALIASI          ALIASI       DMN
   10-11-1-3-fr  ----------- no  ---     3-125-0       s-4-135-3      SS7

   SPCN         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ---- no      none   off   none     no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

rtrv-dstn:dpcn=6-10-7-9-ge

This is an example of the possible output.

rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCN          CLLI        BEI ELEI   ALIASA           ALIASI        DMN
   6-10-7-9-ge   ----------- no  ---    211-100-100      3-175-6       SS7

   SPCN          NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   13-02-12-1-ge ---- no      15     on    20       no     no    none

DESTINATION ENTRIES ALLOCATED:   2000
    FULL DPC(s):                   25
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 2
    Proxy DPC(s):                   2
    TOTAL DPC(s):                  29
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  27
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

Back up the new changes, using the chg-db:action=backup:dest=fixed command.

These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 2-30 Adding a Destination Point Code

Sheet 1 of 5

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5