Adding a Network Routing Point Code

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

To change the attributes of an existing network routing point code, perform the Changing a Destination Point Code procedure.

To remove a network routing point code from the database, perform the Removing a Destination Point Code procedure.

The ent-dstn command uses these parameters.

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

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE. Alias point codes (aliasi/aliasn/aliasn24) and secondary point codes (spc/spca) cannot be specified for a network routing point code. An ANSIprivate point code must be a full 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.

The network routing point code must be in the SS7 domain (domain=ss7) and can only be an ANSI point code. ITU point codes cannot be specified as network routing point codes.

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

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

These parameters cannot be specified with a network routing point code.

ncai spc elei bei ipgwapc ppc prx

The ent-dstn command also contains the homescp and homesmsc parameters. The values for these parameters are yes and no. The value no is the default value for these parameters. The value yes for these parameters cannot be specified for a network routing point code. To specify the value yes for these parameters, perform the Adding a Destination Point Code or Changing a Destination Point Code procedures.

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 1 and 2. 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 the dpc/dpca parameter with the ent-dstn command, a point code must be defined in the PCA field of the self ID of the EAGLE. Verify this with the rtrv-sid command.

If no value is shown in the PCA field in the rtrv-sid command output, the self-identification of the EAGLE must be updated with an ANSI point code. Go to Changing the Self-Identification of the EAGLE procedure to change the self-identification of the EAGLE.

Note:

To enter a network routing point code with the network indicator values 1 through 5, the pctype parameter value of the chg-sid command must be set to other. If you attempt to add a network routing point code with the network indicator values 1 through 5 and the pctype parameter value is ansi, the ent-dstn command will be rejected with this error message.

E2169 Cmd Rej: Point code out of range

Destination point codes must be unique in the database.

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.

The examples in this procedure are used to add the network routing point code 007-*-* to the database.

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     SS7
   240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
   240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
   240-012-008   ----------- yes ---    1-113-5         10-13-10-2    SS7

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

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


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

If the addition of the network routing point code will not exceed the current DPC capacity shown in the rtrv-dstn output, continue the procedure with 2.

If the addition of the network routing point code will exceed the current DPC capacity, and the current capacity is less than 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Changing the DPC Quantity procedure to change the DPC quantity. Continue the procedure with 2.

If the addition of the network routing point code will exceed the current DPC capacity, and the current capacity is 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Removing a Destination Point Code procedure to remove a DPC or perform the Removing a Route Exception Entry procedure to remove an exception route. Continue the procedure with 2.

Verify that the network routing feature is on, by entering the rtrv-feat command.
If the network routing feature is on, the NRT field should be set to on. For this example, the network routing feature is off.

Note:
Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, see thertrv-feat command description in Commands User's Guide.

If the network routing feature is on, continue the procedure with 4.
If the network routing feature is not on, shown by the NRT = off entry in the rtrv-feat command output of 2, turn the network routing feature on by entering this command.
chg-feat:nrt=on
Note:
Once the network routing feature is turned on with thechg-feat command, it cannot be turned off.
The network routing feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the network routing feature, contact your Oracle Sales Representative or Account Representative.

When the chg-feat has successfully completed, this message should appear.
```
rlghncxa03w 07-05-07 00:57:31 GMT EAGLE5 37.0.0
CHG-FEAT: MASP A - COMPLTD
```
Continue the procedure by performing one of these steps.
- If you wish to enter a network routing point code with the network indicator values 1 through 5, and the network indicator values 1 through 5 are not shown in the rtrv-dstn output in 1, perform 4 to verify the pctype value.
- If ANSI point codes are not shown in the rtrv-dstn output in 1, perform 4 to verify that an ANSI point code is assigned to the self-identification of the EAGLE.
- If the rtrv-dstn output in 1 shows ANSI point codes or shows ANSI point codes that contain the network indicator values 1 through 5, or you do not wish to provision a network routing point code with the network indicator values 1 through 5, continue the procedure by performing one of these steps.
  - If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 6.
  - If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 5.
Display the self-identification of the EAGLE 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            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          2-0-11-0          2-0-11-2         2-0-12-1
   2-2-3-3           2-2-4-0           10-14-10-1
```
To enter an ANSI destination point code with the ent-dstn command, a point code must be shown in the PCA field of the rtrv-sid command output.

If the required point code is not shown in the PCA field of the rtrv-sid command output, perform the Changing the Self-Identification of the EAGLE procedure to configure the required point codes.

To enter a network routing point code with the network indicator values 1 through 5, the pctype parameter value of the chg-sid command must be set to other. If you wish to enter a network routing point code with a network indicator value 1 through 5, and the pctype parameter value is ansi, perform the Changing the Self-Identification of the EAGLE procedure to change the pctype value to other.
Continue the procedure by performing one of these steps.
- If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 6 .
- If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 5.
Display the features that are enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.
```
rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
HC-MIM SLK Capacity       893012707 on     64
TIF Number Portability    893018901 off    ----


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.
```
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
Perform the procedures in TIF User's Guide to enable these features as required.
Continue the procedure by performing one of these steps.
- Continue the procedure with 8 if any of these conditions are present.
  - The sccpmsgcnv parameter will not be specified for the cluster point code.
  - The sccpmsgcnv parameter will be specified for the cluster point code and the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on. If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT to enable and turn on the XUDT UDT Conversion feature.
- Continue the procedure with 7 if the sccpmsgcnv parameter will be specified for the cluster point code and 5 was not performed.
Enter this command to verify the status of the XUDT UDT Conversion feature.
rtrv-ctrl-feat:partnum=893035301

This is an example of the possible output.
```
rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
XUDT UDT Conversion       893035301 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 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.

If the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure with 8.

Add the network routing destination point code, using the ent-dstn command.

For this example, enter this command.

ent-dstn:dpca=007-*-*:rcause=50:nprst=on:splitiam=25:sccpmsgcnv=sxudt2udt

When this 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), this message should appear.

rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
Destination table is (17 of 2000) 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), 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:   6000
    FULL DPC(s):                   14
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 1
    CLUSTER DPC(s):                 2
    TOTAL DPC(s):                  17
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                  18
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
ENT-DSTN: MASP A - COMPLTD

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

For this example, enter this command.

rtrv-dstn:dpca=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
   007-*-*       ----------- yes --- ----------      --------------   SS7

   SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ----         50     on    25       no     no    sxudt2udt

Destination table is (14 of 2000) 1% full
Alias table is (18 of 8000) 1% full

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-29 Adding a Network Routing Point Code

Sheet 1 of 4

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4