Adding a Route Containing an SS7 DPC

This procedure is used to add a route containing an SS7 DPC to the database using the ent-rte command. The routes configured in this procedure do not contain cluster point codes as DPCs, or IPGWx linksets. These routes are configured in these procedures:

• Adding a Route Containing a Cluster Point Code
• Adding a Route Containing an IPGWx Linkset

The ent-rte command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code of the node that the traffic is being sent to.

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.

:lsn – The name of the linkset that will carry the traffic to the node specified by the destination point code.

:rc – The relative cost (priority) for this route.

:force – This parameter allows a route to be added to the database even if the linkset to be assigned to the route does not have any signaling links in it.

These items must be configured in the database before a route can be added in this procedure:

• Destination point code (DPC) – see one of these procedures depending on the type of point code required:
  • For a Network Routing DPC – see Adding a Network Routing Point Code.
  • For all other DPCs – see Adding a Destination Point Code
• Linkset – see Adding an SS7 Linkset
• Link – see Adding an SS7 Signaling Link.

The linkset assigned to this route must have an adjacent point code (APC) in the SS7 domain. The domain of the DPC is shown in the DMN field in the output of the rtrv-dstn command.

The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, routes containing ANSI DPCs must have linksets with ANSI APCs; routes containing ITU-I DPCs must have linksets with ITU-I APCs; routes containing 14-bit ITU-N DPCs must have linksets with 14-bit ITU-N APCs; routes containing 24-bit ITU-N DPCs must have linksets with 24-bit ITU-N APCs. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Alias point codes and secondary point codes cannot be used. True point codes are shown in the output of the rtrv-dstn command in the DPCA, DPCI, DPCN, or DPCN24 fields. Private point codes cannot be used as the DPC of a route in this procedure. Routes that have private point codes as the DPC of a route can contain only IPGWx linksets. Perform the Adding a Route Containing an IPGWx Linkset procedure to add routes containing IPGWx linksets.

The DPC of the route is the destination point code to be reached by the route and is shown in the output of the rtrv-rte command in the DPCA, DPCI, DPCN, or DPCN24 fields.

The APCA, APCI, APCN, and APCN24 fields in the output of the rtrv-rte command show the point code of the node that is directly adjacent to the node in the route.

A linkset can only be entered once as a route for each DPC.

A maximum of six routes can be defined for each DPC.

If the 6-Way Loadsharing on Routesets feature is enabled and turned on, a maximum of six routes in the routeset can be assigned the same relative cost value. It is recommended that the routeset be provisioned with a group of four routes that have the same relative cost value and another group of two routes that have the same relative cost value. Three or five routes in the routeset that have the same relative cost value can be provisioned, but the odd number makes it more difficult to distribute the route traffic evenly. Six routes in the routeset that have the same relative cost value can be provisioned, but this does not allow for any backup routes and also offers the worst chance for congestion and queuing issues during network failures. If the 6-Way Loadsharing on Routesets feature is not enabled or not turned on, a maximum of two linksets can be assigned the same relative cost value. The relative cost value of the route is defined by the rc parameter of the ent-rte command and is shown in the RC field in the output of the rtrv-rte command.

The force=yes parameter must be specified if the specified linkset has no signaling links assigned to it. Otherwise, each linkset must have at least one signaling link assigned to it.

The ANSI DPC (DPC/DPCA) of the route can use either a full point code or a network routing point code. ITU DPCs (DPCI, DPCN, and DPCN24) must use full point codes. For more information on network routing point codes, go to the Network Routing section.

If the DPC of the route is a network routing point code, only linksets, specified with either the lsn or nlsn parameters, whose linkset type is either B, C, or D can be assigned to the route. The linkset type is shown in the LST field of the rtrv-ls command output. If the linkset type of the desired linkset is either A, E, or PRX, one of three actions must be taken.

• Choose another linkset with the linkset type B, C, or D.
• Change the linkset type of an existing linkset - perform the Changing an SS7 Linkset procedure.
• Add a new linkset to the database with the necessary signaling links and the linkset type B, C, or D.
  1. Perform the Adding an SS7 Linkset procedure to add the linkset.
  2. If the necessary signaling links are not in the database, go to the Adding an SS7 Signaling Link procedure and add the signaling links to the database.

If the DPC of the route is a member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then the route to the DPC must be the same as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code. For more information, see the Nested Cluster Routing section.

For routes containing 14-bit ITU National DPCs with group codes, if the linkset assigned to the route has the MULTGC value set to yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the MULTGC value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route.

When a new route is being added and the DPC of that route contains a proxy point code, the first route assigned to this DPC must be a linkset whose linkset type is PRX and must have a proxy point code assigned to the linkset. The proxy point code that is assigned to the linkset must be the proxy point code that is assigned to the DPC of the route. After this route has been added, other routes can be added to this DPC. The linksets for these routes can contain proxy point codes, but do not have to contain proxy point codes.

Canceling the RTRV-LS, RTRV-DSTN, and RTRV-RTE Commands

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

• Press the F9 function key on the keyboard at the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered.
• Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered.
• Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered, from another terminal other that the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were 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, go to Commands User's Guide.

1. Display the current route configuration using the rtrv-rte 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           ALIASI     ALIASN/N24    LSN        RC    APCA
      140-012-004    1-111-1    10-13-12-1    ls000001   10    240-012-002
                                              ls000002   10    240-012-002
                                              ls000003   20    240-012-002
                                              ls000004   30    240-012-002
                                              ls000005   40    240-012-002
                                              ls000006   50    240-012-002
                                                  RTX:No  CLLI=dp1
      140-012-005 1-111-2 10-13-12-2          ls000001   10    240-012-002
                                              ls000002   10    240-012-002
                                              ls000003   20    240-012-002
                                              ls000004   30    240-012-002
                                              ls000005   40    240-012-002
                                              ls000006   50    240-012-002
                                                  RTX:No  CLLI=dp2
      DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
      2-234-5    11-13-3-3       240-111-111  ls100001   10    1-234-5
                                              ls100002   10    1-234-6
                                              ls100003   20    1-234-7
                                              ls100004   30    1-234-1
                                              ls100005   40    1-234-2
                                              ls100006   50    1-234-3
                                                  RTX:No  CLLI=idp1
      DPCN             ALIASA         ALIASI  LSN        RC    APC
      12-12-13-3       011-222-111    0-001-1 ls200001   10    10-13-9-3
                                              ls200002   10    10-13-10-0
                                              ls200003   20    10-13-10-1
                                              ls200004   30    10-13-10-2
                                              ls200005   40    10-13-10-3
                                              ls200006   50    10-13-11-0
                                                  RTX:No  CLLI=ndp1
   
      DPCN24           ALIASA         ALIASI  LSN        RC    APC
   

   If the destination point code of the route being added in this procedure is not shown in the rtrv-rte output, perform one of these procedures in Chapter 2 to add the destination point code of the route to the destination point code table.

   • For a Network Routing DPC – Adding a Network Routing Point Code.
   • For all other DPCs – Adding a Destination Point Code.
     After the new DPC has been added, continue the procedure by performing one of these steps.

     • If a proxy point code was assigned to the new DPC that was added, continue this procedure with 2.
     • If a proxy point code was not assigned to the new DPC that was added, continue the procedure by performing one of these steps.
       • If no more than two routes in the routeset will have the same relative cost value, and the new DPC is a member of a cluster, continue the procedure with 6.
       • If no more than two routes in the routeset will have the same relative cost value, and the new DPC is not a member of a cluster, continue the procedure with 7.
       • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
         • If the new DPC is a member of a cluster, continue the procedure with 6.
         • If the new DPC is not a member of a cluster, continue the procedure with 7.
       • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 5.

   If the destination point code of the route being added in this procedure is shown in the rtrv-rte output, continue the procedure by performing one of these steps.

   • If the DPC that you wish to add the route to contains six routes, no more routes can be added to this DPC. A DPC of a route can contain a maximum of six routes. Choose another DPC to add the routes to and repeat this step.
   • If the DPC that you wish to add the route to is a network routing point code, or already has at least one route assigned to it, continue the procedure by performing one of these steps.
     • If no more than two routes in the routeset will have the same relative cost value, and the DPC is a member of a cluster, continue the procedure with 6.
     • If no more than two routes in the routeset will have the same relative cost value, and the DPC is not a member of a cluster, continue the procedure with 7.
     • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
       • If the DPC is a member of a cluster, continue the procedure with 6.
       • If the DPC is not a member of a cluster, continue the procedure with 7.
     • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 5.
   • If the DPC that you wish to add the route to is not a network routing point code, and has no routes assigned to it, continue this procedure with 2.
2. The first route to a DPC that contains a proxy point code must be a linkset whose linkset type is PRX. This linkset must contain the proxy point code that is assigned to the DPC of the route..

   Verify if the DPC of the route contains a proxy point code by entering the rtrv-dstn command with the DPC of the route. For this example, enter this command.

   rtrv-dstn:dpca=003-003-003

   This is an example of the possible output.

   rlghncxa03w 10-12-15 09:22:39 EST  43.0.0
   
      DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      003-003-003   ----------- no  --- ----------      --------------   SS7
   
      PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
      010-010-010  ---- no      none   off   none     no     no    none
   
   Destination table is (14 of 2000) 1% full
   Alias table is (0 of 12000) 0% full
   PPC table is (2 of 10) 20% full
   

   If a proxy point code is not shown in this step, continue the procedure by performing one of these steps.

   • If no more than two routes in the routeset will have the same relative cost value, and the DPC is a member of a cluster, continue the procedure with 6.
   • If no more than two routes in the routeset will have the same relative cost value, and the DPC is not a member of a cluster, continue the procedure with 7.
   • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
     • If the DPC is a member of a cluster, continue the procedure with 6.
     • If the DPC is not a member of a cluster, continue the procedure with 7.
   • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 5.

   If a proxy point code is shown in this step, continue this procedure with 3.

3. Display the linksets that contain the proxy point code that is assigned to the DPC of the route by entering the rtrv-ls command with the proxy point code. For this example, enter this command.

   rtrv-ls:ppca=010-010-010

   This is an example of the possible output.

   rlghncxa03w 07-08-15 09:50:20 EST  37.0.0
   
   PPCA   =    010-010-010
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn3          003-003-003   none 1   1   no  PRX 2    off off off no    off
   lsn5          012-012-012   none 1   1   no  PRX 2    off off off no    off
   lsn15         015-015-015   none 1   1   no  PRX 2    off off off no    off
   
   
   Link set table is (11 of 1024) 1% full.

   The linkset that is being assigned to the DPC of the route must be shown in this step. The APC of this linkset must be the same as the DPC of the route. If this linkset is not shown in this step, perform the Adding an SS7 Linkset procedure to add a linkset that contains these attributes.

   • The APC of the linkset must be the same as the DPC of the route.
   • The linkset type must be PRX.
   • The proxy point code that is assigned to the DPC of the route must be assigned to the linkset.

   After the linkset has been added, continue the procedure with 4.

   If a linkset is shown in this step whose APC is the same as the DPC of the route, continue the procedure with 4.

4. Add the route containing the proxy linkset (the linkset type is PRX) using the ent-rte command. For this example, enter this command.

   ent-rte:dpca=003-003-003:lsn=lsn3:rc=10

   When this command has successfully completed, this message should appear.

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   ENT-RTE: MASP A - COMPLTD
   

   Other routes can be added to this DPC. If you wish to add more routes, continue the procedure by performing one of these steps.

   • If no more than two routes in the routeset will have the same relative cost value, and the DPC is a member of a cluster, continue the procedure with 6.
   • If no more than two routes in the routeset will have the same relative cost value, and the DPC is not a member of a cluster, continue the procedure with 7.
   • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
     • If the DPC is a member of a cluster, continue the procedure with 6.
     • If the DPC is not a member of a cluster, continue the procedure with 7.
   • If more than two routes in the routeset will have the same relative cost value, and routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 5.

   If you do not wish to add more routes to this DPC, continue the procedure with 10.

5. For a routeset to have more than two routes with the same relative cost value, the 6-Way Loadsharing on Routesets feature must be enabled and turned on.

   To verify the status of the 6-Way Loadsharing on Routesets feature, enter this command.

   rtrv-ctrl-feat:partnum=893019801

   The following is an example of the possible output.

   rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   6-Way LS on Routesets     893019801  on      ----
   
   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.
   

   If the 6-Way Loadsharing on Routesets feature is not enabled or not turned on, perform the Activating the 6-Way Loadsharing on Routesets Feature procedure to enable and turn on the 6-Way Loadsharing on Routesets feature.

   After the 6-Way Loadsharing on Routesets feature has been enabled and turned on, or if the rtrv-ctrl-feat output shows that the 6-Way Loadsharing on Routesets feature is enabled and turned on, continue this procedure by performing one of these steps.

   • If the DPC is a member of a cluster, continue the procedure with 6.
   • If the DPC is not a member of a cluster, continue the procedure with 7.
6. Display the ncai parameter value assigned to the cluster point code using the rtrv-dstn command and specifying the cluster point code. If the ncai parameter value is no, then the route to the DPC must be the same as the route to the cluster point code. If the ncai parameter value is yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code. The ncai value is shown in the NCAI field of the rtrv-dstn output. For this example, enter this command.

   rtrv-dstn:dpca=111-011-*

   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
      111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
   
      SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
      -----------  yes          none   off   none     no     no    none
   
   Destination table is (12 of 2000) 1% full
   Alias table is (18 of 8000) 1% full
   

   If the ncai parameter value of the cluster point code is no, and you wish to change the ncai parameter value to yes, perform the Changing the Attributes of a Cluster Point Code procedure. If the ncai parameter value of the cluster point code is no, and you do not wish to change the ncai parameter value to yes, add a new DPC for the route by performing either the Adding a Destination Point Code procedure or the Adding a Network Routing Point Code procedure.
7. Verify that the required linkset for the route is in the database by displaying the linksets in the database with the rtrv-ls command.

   This is an example of the possible output.

   rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.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
   lsn7          002-002-002   none 1   1   no  C   8    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
   
                                    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
   ls7890        7-089-0       none 1   2   no  B   1    off off off ---   off
   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 (12 of 1024) 1% full.
   

   If the required linkset is not in the database, perform the Adding an SS7 Linkset procedure to add the linkset to the database with the ipgwapc=no parameter value. The APC of the linkset cannot be a private point code. Continue the procedure with 8.

8. Display each linkset being assigned to the route to verify the multgc and ipgwapc parameter values with the rtrv-ls command, specifying the name of the linkset that will be assigned to the route.

   If the multgc linkset parameter value is yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the multgc value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route. The multgc value is shown in the MULTGC field of the rtrv-ls output. Linksets that have the ipgwapc=yes parameter value are assigned to routes using the Adding a Route Containing an IPGWx Linkset procedure. If the linkset displayed in this step contains the ipgwapc=yes parameter, repeat this step with another linkset shown in 7. If all the linksets have been displayed, and the ipgwapc value for all the linksets is yes, add the desired linkset by performing Adding an SS7 Linkset with the ipgwapc=no parameter value. The APC of the linkset cannot be a private point code.

   For this example, enter the following commands.

   rtrv-ls:lsn=lsn7

   This is an example of the possible output.

   rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn7          002-002-002   none 1   1   no  C   8    off off off no    off
   
              CLLI         TFATCABMLQ MTPRSE ASL8
              -----------  4          ---    no
   
              IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
              no      ---------- ---   ---      ---       CdPA
   
                                     L2T               PCR  PCR
              LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
              1211 A     0  LIMDS0   1    56000  BASIC ---  -----
              1211 B     1  LIMDS0   1    56000  BASIC ---  -----
              1211 A1    2  LIMDS0   1    56000  BASIC ---  -----
              1211 A2    3  LIMDS0   1    56000  BASIC ---  -----
              1211 B2    4  LIMDS0   1    56000  BASIC ---  -----
              1211 B1    5  LIMDS0   1    56000  BASIC ---  -----
              1211 B3    6  LIMDS0   1    56000  BASIC ---  -----
              1211 A3    7  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (12 of 1024) 1% full.
   

   rtrv-ls:lsn=ls7890

   rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   ls7890        7-089-0       none 1   2   no  B   1    off off off ---   off
   
              CLLI         TFATCABMLQ MTPRSE ASL8 SLSOCBIT SLSRSB MULTGC
              dtaclli      1          no     ---  none     1      no
   
              ITUTFR
              off
   
              IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
              no      ---------- ---   ---      ---       CdPA
   
                                     L2T               PCR  PCR
              LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
              1103 A     0  LIMDS0   11   56000  BASIC ---  -----
   
   Link set table is (12 of 1024) 1% full.
   

9. Add the route using the ent-rte command. For this example, enter these commands.

   ent-rte:dpca=002-002-200:lsn=lsn7:rc=10

   ent-rte:dpci=7-089-0:lsn=ls7890:rc=20

   ent-rte:dpca=003-003-003:lsn=lsn7:rc=20

   These are the rules that apply to adding a route.

   • The force=yes parameter must be specified if the linkset being assigned to the route has no signaling links assigned to it. Otherwise, each linkset must have at least one signaling link assigned to it.
   • A route can contain a maximum of six linksets.
   • A maximum of two linksets can be assigned the same rc parameter value, if the 6-Way Loadsharing on Routesets feature is not enabled or turned on. If the 6-Way Loadsharing on Routesets feature is enabled and turned on, a maximum of six linksets in the route can have the same rc parameter value.
   • If the DPC of the route is a member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then the route to the DPC must be the same as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code.
   • For routes containing 14-bit ITU National DPCs with group codes, if the linkset assigned to the route has the MULTGC value set to yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the MULTGC value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route.
   • The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, routes containing ANSI DPCs must have linksets with ANSI APCs; routes containing ITU-I DPCs must have linksets with ITU-I APCs; routes containing 14-bit ITU-N DPCs must have linksets with 14-bit ITU-N APCs; routes containing 24-bit ITU-N DPCs must have linksets with 24-bit ITU-N APCs. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Alias point codes and secondary point codes cannot be used. True point codes are shown in the output of the rtrv-dstn command in the DPCA, DPCI, DPCN, or DPCN24 fields.
   • Private point codes can be specified as the DPC of a route only if the linkset assigned to the route is an IPGWx linkset (a linkset that has the ipgwapc=yes parameter assigned to it).
   • If the DPC of the route is a network routing point code, the link set type of the linkset assigned to the route must be either B, C, or D.

   When each of these commands have successfully completed, this message should appear.

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   ENT-RTE: MASP A - COMPLTD
   

10. Verify the changes using the rtrv-rte command, specifying the destination point code of the route.

    For this example, enter these commands.

    rtrv-rte:dpca=002-002-200

    This is an example of the possible output.

    rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
    
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       002-002-002 ---------- --------------   lsn7       10    002-002-002
                                                   RTX:No  CLLI=-----------
    

    rtrv-rte:dpci=7-089-0:lsn=ls7890:rc=20

    This is an example of the possible output.

    rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
    
       DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
       7-089-0 --------------   -------------- ls7890     10    7-089-0
                                                   RTX:No  CLLI=dtaclli
    

    rtrv-rte:dpca=003-003-003

    This is an example of the possible output.

    rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
    
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       003-003-003 ---------- --------------   lsn3       10    003-003-003
                                               lsn7       20    002-002-002
                                                   RTX:No  CLLI=-----------
    

11. 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 3-18 Adding a Route Containing an SS7 DPC

Sheet 1 of 7

Sheet 2 of 7

Sheet 3 of 7

Sheet 4 of 7

Sheet 5 of 7

Sheet 6 of 7

Sheet 7 of 7