Changing a Destination Point Code

This procedure is used to change the attributes of a full destination point code in the database, using the chg-dstn command.

To change the attributes of a cluster point code, go to the Changing the Attributes of a Cluster Point Code procedure.

This procedure cannot be used to change a true point code (dpc/dpca/dpci/dpcn/dpcn24), or a proxy point code value assigned to a DPC. To change a true point code or a proxy point code value assigned to a DPC, the destination point code must be removed, then re-entered. Perform the Removing a Destination Point Code procedure to remove the point code from the database. To add the new point code, perform one of these procedures:

• Cluster point code – Adding a Cluster Point Code
• Network routing point code – Adding a Network Routing Point Code
• All other point codes – Adding a Destination Point Code

Note:

To add a proxy point code, the point code cannot be a cluster point code or a network routing point code.

The destination point code to be changed must be in the database.

The chg-dstn command uses these parameters:

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code in the database being changed.

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

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

: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 chg-dstn command for SS7 routing purposes. See 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. To specify the prx=yes parameter, 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.

To specify the prx=no parameter, the proxy point code cannot be assigned to a destination point code or assigned to a linkset. Proxy point codes are shown in the rtrv-dstn:dpc=<DPC being changed> output with the entry PRX=yes. To verify if the proxy point code is assigned to a destination point code, enter the rtrv-dstn command with the ppc parameter equal to the proxy point code value. This will display all the destination point codes that reference the proxy point code. These destination point codes must be removed before the prx=no parameter can be specified..

To verify if the proxy point code is assigned to a linkset, enter the rtrv-ls command with the ppc parameter equal to the proxy point code value. This will display all the linksets that reference the proxy point code. These linksets must be removed before the proxy point code can be removed.

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

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

: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.
• 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 Changing the Attributes of 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 in the SS7 domain. Secondary point codes cannot be assigned to DPCs that have proxy point codes assigned to them. The same secondary point code value cannot be assigned to DPCs and to linksets The network type of the secondary point code must match the network type of the destination point code. 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.

If a secondary point code is assigned to the destination point code, the group code of the 14-bit ITU-N destination point code must match the group code of the secondary point code. Otherwise, the group code of the destination point code must match the group code assigned to the EAGLE’s true 14-bit ITU-N point code, shown in the PCN field of the rtrv-sid output.

The value none for the spca, spci, spcn, or spcn24 parameters removes the assignment of the current secondary point code and leaves the destination point code without a secondary point code.

The value of the clli parameter cannot be in the destination point code table and cannot match the CLLI of the EAGLE. Verify this by entering the rtrv-dstn and the rtrv-sid commands. 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, or ITU-N - 14-bit or 24-bit) into the database with the chg-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 field of the rtrv-sid command, then ANSI point codes can be specified with the chg-dstn command.

If a point code value is shown in the PCI field of the output of the rtrv-sid command, then ITU-I point codes can be specified with the chg-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 field of the output of the rtrv-sid command, then 14-bit ITU-N point codes can be specified with the chg-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 field of the output of the rtrv-sid command, then 24-bit ITU-N point codes can be specified with the chg-dstn command.

If no values are shown in the PCA, PCI, PCN, or PCN24 fields in the rtrv-sid command output, the self-identification of the EAGLE must be updated with an ANSI point code, ITU international point code or a 14-bit ITU national point code. Perform the Changing the Self-Identification of the EAGLE procedure to change 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.

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

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

DPC Type	Alias Point Code Type (See Notes 1 - 7)	Alias Point Code Type (See Notes 1 - 7)	DPC TYPE	Alias Point Code Type (See Notes 1 - 7)	Alias Point Code Type (See Notes 1 - 7)
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 9)	ITU-N Spare (Note 9)
	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 8)	ITU-I Spare (Note 8)
	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 9)	ITU-N Spare (Note 9)		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 8)	ITU-I Spare (Note 8)
	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 thealiasa parameter. ITU-I and ITU-I Spare alias point codes are specified with thealiasi parameter. ITU-N and ITU-N Spare alias point codes are specified with thealiasn parameter. ITU-N24 alias point codes are specified with thealiasn24 parameter. If the alias point code parameter is not specified, the parameter's value is not changed. If the valuenone is specified for an alias point code parameter, the current value for that parameter is removed from the DPC. The new alias point code value replaces the current alias point code value that is assigned to the DPC. To specify the ITU-I and ITU-I Spare alias point codes for the DPC, both point code values are specified with thealiasi 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. Thealiasa andaliasn 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 thealiasn 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. Thealiasa andaliasi 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.

Destination point codes and alias point codes must be unique in the database. A point code cannot be defined as a true destination point code and an alias point code.

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

Table 2-18 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

If either the dpcn or aliasn parameters are specified with the chg-dstn command, the format of the 14-bit ITU-N 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.

1. 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
      007-*-*       ----------- 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-007   ----------- yes ---    1-117-3         10-13-11-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
      4-163-5       ----------- no  ---    250-200-007  --------------   SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      7-9-10-1-fr   --------    no  ---    210-090-100     1-75-6        SS7
      7-9-10-1-ge   --------    no  ---    210-100-100     2-175-6       SS7
      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):                   21
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  24
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  29
       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):                   31
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 2
       Proxy DPC (s)                   2
       TOTAL DPC(s):                  36
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  22
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   This procedure cannot be used to change the DPC value (dpc/dpca/dpci/dpcn/dpcn24). To change the DPC value, the destination point code must be removed, then re-entered. Perform the Removing a Destination Point Code procedure to remove the point code from the database. To add the new point code, perform one of these procedures.

   • Cluster point code – Adding a Cluster Point Code
   • Network routing point code – Adding a Network Routing Point Code
   • All other point codes – Adding a Destination Point Code

   If the DPC value is not being changed, continue the procedure with 2.

2. Display all the attributes of the point code being changed, using the rtrv-dstn command with either the dpca, dpci, dpcn, or dpcn24 parameters.

   For this example, enter this command.

   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
      -----------  ---- no      none   off   none     no     no    none
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   21
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  24
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  29
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If a proxy point code is assigned to the DPC, and you wish to change the proxy point code assigned to the DPC, the DPC must be removed, then re-entered with the new proxy point code value. Perform the Removing a Destination Point Code procedure to remove the point code from the database. To add the new point code, perform one of these procedures.

   • Cluster point code – Adding a Cluster Point Code
   • Network routing point code – Adding a Network Routing Point Code
   • All other point codes – Adding a Destination Point Code

   If a proxy point code is not assigned to the DPC, continue the procedure with 3.

3. To change the attributes of a DPC, these entities must be checked depending on how the attributes of the DPC will be changed. Perform these commands and procedures as required depending on how the attributes of the DPC will be changed.

   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 4. If the point code type is not shown in the rtrv-dstn and rtrv-sid outputs, perform the Adding a Point Code to the Self-Identification of the EAGLE procedure to add a point code of the desired point code type.

   If the new point code 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 4, rtrv-dstnoutput in 1, or rtrv-spc output in 5. If the group code is not shown in either of these outputs, perform the Adding a Point Code to the Self-Identification of the EAGLE procedure to 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 the Adding a Secondary Point Code procedure to add a secondary point code with the desired group code.

   If a secondary point code value will be changed, the new secondary point code must be shown in the rtrv-spc output in 5. If the new secondary point code is shown in the rtrv-spc output, and the Multiple Linksets to Single Adjacent PC feature is enabled and turned on, the new secondary point code cannot be the secondary point code of a linkset. Enter the rtrv-ctrl-feat command in 8 to verify if the Multiple Linksets to Single Adjacent PC feature is enabled and turned on. If the Multiple Linksets to Single Adjacent PC feature is enabled and turned on, enter the rtrv-ls command in 6 with the spc/spca/spci/spcn/spcn24 parameter with the new secondary point code value from the rtrv-spc output. It the secondary point code is not shown in the rtrv-spc output, perform the Adding a Secondary Point Code procedure to add the desired secondary point code. The spc/spca/spci/spcn/spcn24 parameter cannot be specified for a DPC that contains a proxy point code, shown the PPCA/PPCI/PPCN/PPCN24 field when the individual DPC is displayed.

   If the clli parameter value will be changed, the new clli parameter value cannot be shown in the rtrv-sid or rtrv-dstn outputs. Enter the rtrv-sid command in 4 to verify the CLLI value in the self-identification of the EAGLE.

   The format of a 14-bit ITU-N point code must match the format defined by the NPCFMTI value in the rtrv-stpopts output. Enter the rtrv-stpopts in 7 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, specifying 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, remove enough alias point codes to allow the new alias point code to be added. Enter the chg-dstn command with the DPC that contains the alias point code that is being removed and with the aliasa/aliasi/aliasn/aliasn24=none parameter. Enter this command as needed to remove the required number of alias point codes.

   If the nprst or rcause parameters will be specified with the DPC, the TIF Number Portability feature must be enabled. If the current rcause value is none and the current nprst value is off, enter the rtrv-ctrl-feat command in 8 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

     If the current splitiam value is none, enter the rtrv-ctrl-feat command in 8 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 parameter 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 8 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 the Changing the Proxy Point Code Quantity procedure. The prx=yes parameter cannot be specified for the DPC if any of these conditions are present.

   • If the enabled quantity is 100 and 100 proxy point codes are in the database.
   • If the DPC is a private point code, a cluster point code, a network routing point code, or the adjacent point code of an IPGWx linkset. The private point codes, cluster point codes, and network routing point codes are shown in the rtrv-dstn output. Display the linkset with the rtrv-ls command in 10, then re-enter the rtrv-ls command in 11 with the name of the linkset that has the DPC as its adjacent point code to verify if the linkset is an IPGWx linkset.

   If the current PRX value is yes, the PRX value cannot be changed if the DPC is referenced by other point codes as a proxy point code. Enter the rtrv-dstn command in 9 with the ppc/ppca/ppci/ppcn/ppcn24 parameter and the DPC that is being changed to verify if the proxy point code is referenced by other point codes. Perform the Removing a Destination Point Code procedure to remove the point code that reference the proxy point code.

   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 8 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 12.

4. Display the EAGLE self-identification, using the rtrv-sid command.

   This is an example of the possible output.

   rlghncxa03w 07-05-10 11:43:04 GMT  EAGLE5 37.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
   

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

   This is an example of the possible output.

   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.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
   

6. A secondary point code cannot be added to a DPC if that secondary point code is assigned to any linksets.

   Display the linksets that have the secondary point code assigned to them by entering the rtrv-ls command with either the spc/spca, spci, spcn, or spcn24 parameters.

   For this example, enter this command.

   rtrv-ls:spca=010-100-010

   This is an example of the possible output.

   rlghncxa03w 07-05-19 17:06:08 EST  37.5.0     
        
   SPCA = 010-100-010
                                    L3T SLT              GWS GWS GWS 
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS    
   lsn1          000-007-000   none 1   1   no  PRX 0    off off off no    off    
   lsn2          001-001-001   none 1   1   no  PRX 0    off off off no    off    
   
   Link set table is (11 of 1024) 1% full. 
   

7. 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 07-05-17 16:02:05 GMT  EAGLE5 37.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.
8. Display the features that are enabled by entering the rtrv-ctrl-featcommand.

   The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.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.
   

9. Display the point codes in the database that have the proxy point code assigned to them by entering the rtrv-dstn command with the ppc/ppca/ppci/ppcn/ppcn24 parameter. The ppc/ppca/ppci/ppcn/ppcn24 parameter value is the proxy point code being removed in this procedure. For this example, enter this command.

   rtrv-dstn:ppca=002-002-002

   This is an example of the possible output.

   rlghncxa03w 09-05-28 21:16:37 EDT EAGLE5 41.0.0     
        
      DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      000-005-000   ----------- no  --- ----------      --------------   SS7
      PRX = no      PPC =    002-002-002 
   
      001-001-002   ----------- no  --- ----------      --------------   SS7
      PRX = no      PPC =    002-002-002
   
      Destination table is (11 of 2000) 1% full
      Alias table is (0 of 12000) 0% full
      PPC table is (2 of 10) 20% full 
   

10. Display the linksets in the database by entering the rtrv-ls command. This is an example of the possible output.

    rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
    
                                     L3T SLT              GWS GWS GWS
    LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    e1e2          001-207-000   none 1   1   no  B   6    off off off no    off
    ls1305        000-005-000   none 1   1   no  A   1    off off off no    off
    ls1307        000-007-000   none 1   1   no  A   1    off off off no    off
    e1m1s1        001-001-001   none 1   1   no  A   7    off off off no    off
    e1m1s2        001-001-002   none 1   1   no  A   7    off off off no    off
    lsn10         240-012-007   none 1   1   no  A   1    off off off no    off
    ls20          002-002-002   none 1   1   no  PRX 1    off off off no off
    
                                     L3T SLT              GWS GWS GWS
    LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    e1e2i         1-207-0       none 1   1   no  B   4    off off off ---   on
    ls1315        0-015-0       none 1   1   no  A   1    off off off ---   off
    ls1317        0-017-0       none 1   1   no  A   1    off off off ---   on
    e1m2s1        1-011-1       none 1   1   no  A   7    off off off ---   off
    e1m2s2        1-011-2       none 1   1   no  A   7    off off off ---   off
    
    Link set table is (10 of 1024) 1% full.
    

11. Display the attributes of the linkset shown in 10 whose APC is the DPC being changed by entering the rtrv-ls command with the lsn parameter.

    For this example, enter this command.

    rtrv-ls:lsn=lsn10

    This is an example of the possible output.

    rlghncxa03w 07-05-28 21:16:37 EDT EAGLE5 37.0.0     
    
                                         L3T SLT              GWS GWS GWS     
    LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS    
    lsn10         240-012-007   none 1   1   no  A   1    off off off no    off
    
               CLLI         TFATCABMLQ MTPRSE ASL8
               -----------  1          ---    no
    
               IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
               yes     ---------- 200    100    % 80      % CdPA
    
    
               LOC  PORT SLC TYPE
               1211 A     0  SS7IPGW
    
    Link set table is (10 of 1024) 1% full. 
    

12. Change the destination point code using the chg-dstn command.

    If alias point code values will be changed, Table 2-17 shows the DPC and alias point type combinations that can be used with the chg-dstn command.

    For this example, enter these commands.

    chg-dstn:dpca=240-012-007:clli=ls09clli:bei=no:aliasi=2-66-1 :aliasn=0-10-13-3-fr:spca=003-010-010:homescp=yes:homesmsc=yes:sccpmsgcnv=udt2xudt

    chg-dstn:dpci=2-131-2:aliasn=8-10-2-0-fr,s-9-11-1-3-fr

    chg-dstn:dpcn=10-15-3-0-fr:aliasi=3-150-7,s-3-125-2

    If the point code is being changed to a proxy point code, the prx=yes parameter must be specified. The point code cannot be a private point code, cannot have the ipgwapc=yes parameter assigned, and cannot be a cluster or network routing point code.

    If the point code is being changed from a proxy point code to a non-proxy point code, the prx=no parameter must be specified. The proxy point code cannot be assigned to a linkset or to other destination point codes.

    An SPC cannot be assigned to a destination point code if the SPC is assigned to a linkset.

    If the aliasn parameter is specified with the chg-dstn command, make sure that the format of the ITU national alias point code matches the format shown in the NPCFMTI field of the rtrv-stpopts command output shown in 7 or with the format that was defined when the procedure in the 14-Bit ITU National Point Code Formats section was performed in 3.

    When this command has successfully completed, and the Cluster Routing and Management Diversity feature is turned off (CRMD = off in the rtrv-feat command output), and no proxy point code quantity is enabled, this message should appear.

    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    Destination table is (24 of 2000) 1% full
    Alias table is (29 of 8000) 1% full
    CHG-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 when each command has successfully completed.

    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   21
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  24
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  29
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    CHG-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 06-10-17 15:35:05 GMT EAGLE5 36.0.0
    Destination table is (24 of 2000) 1% full 
    Alias table is (29 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 06-10-17 15:35:05 GMT EAGLE5 36.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   24
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        Proxy DPC(s):                   2
        TOTAL DPC(s):                  28
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  27
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD
    

13. Verify the changes using the rtrv-dstn command, and specifying the destination point code that was entered in 12.
    1. If an ANSI destination point code was changed in 12, use the dpca parameter to display the attributes of the destination point code.
    2. If an ITU international destination point code was changed in 12, use the dpci parameter to display the attributes of the destination point code.
    3. If a 14-bit ITU national destination point code was changed in 12, use the dpcn parameter to display the attributes of the destination point code.
    4. If a 24-bit ITU national destination point code was changed in 12, use the dpcn24 parameter to display the attributes of the destination point code.

       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   ls09clli    no  ---    2-66-1          0-10-13-3-fr  SS7
       
          SPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
          003-010-010  ---- no      none   off   none     yes    yes   udt2xudt
       
       DESTINATION ENTRIES ALLOCATED:   2000
           FULL DPC(s):                   21
           EXCEPTION DPC(s):               0
           NETWORK DPC(s):                 1
           CLUSTER DPC(s):                 2
           TOTAL DPC(s):                  24
           CAPACITY (% FULL):             1%
       ALIASES ALLOCATED:               8000
           ALIASES USED:                  29
           CAPACITY (% FULL):             1%
       X-LIST ENTRIES ALLOCATED:         500
       RTRV-DSTN: MASP A - COMPLTD
       

       rtrv-dstn:dpci=2-131-2

       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
          2-131-2       ----------- no  ---     8-10-2-0-fr   s-9-11-1-3-fr  SS7
       
          SPCI         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
          -----------  ---- no      none   off   none     no     no    none
       
       DESTINATION ENTRIES ALLOCATED:   2000
           FULL DPC(s):                   21
           EXCEPTION DPC(s):               0
           NETWORK DPC(s):                 1
           CLUSTER DPC(s):                 2
           TOTAL DPC(s):                  24
           CAPACITY (% FULL):             1%
       ALIASES ALLOCATED:               8000
           ALIASES USED:                  29
           CAPACITY (% FULL):             1%
       X-LIST ENTRIES ALLOCATED:         500
       RTRV-DSTN: MASP A - COMPLTD
       

       rtrv-dstn:dpcn=10-15-3-0-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-15-3-0-fr  rlgnncbb013 no  ---     3-150-7       s-3-125-2      SS7
       
          SPCN         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
          -----------  ---- no      none   off   none     no     no    none
       
       DESTINATION ENTRIES ALLOCATED:   2000
           FULL DPC(s):                   21
           EXCEPTION DPC(s):               0
           NETWORK DPC(s):                 1
           CLUSTER DPC(s):                 2
           TOTAL DPC(s):                  24
           CAPACITY (% FULL):             1%
       ALIASES ALLOCATED:               8000
           ALIASES USED:                  29
           CAPACITY (% FULL):             1%
       X-LIST ENTRIES ALLOCATED:         500
       RTRV-DSTN: MASP A - COMPLTD
       

14. 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-32 Changing a Destination Point Code

Sheet 1 of 4

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4