1. EAGLE Database Administration - SEAS User's Guide
  2. Configuring Destination Tables

2 Configuring Destination Tables

Chapter 2, Configuring Destination Tables, describes the methods for configuring destination point codes (DPCs) in the database of the EAGLE.

2.1 Adding a Cluster Point Code

This procedure is used to add a cluster point code for the cluster routing and management diversity feature to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, rtrv-stpopts, chg-stpopts, rtrv-ctrl-feat, rtrv-dstn, and chg-db. For more information on this procedure, see “Adding a Cluster Point Code” in Database Administration – SS7 User's Guide.

Note:

Once the cluster routing and management diversity and nested cluster routing features are turned on with the chg-feat command, they cannot be turned off.

The cluster routing and management diversity and nested cluster routing features must be purchased before you turn the features on with the chg-feat command. If you are not sure whether you have purchased the cluster routing and management diversity and nested cluster routing features, contact your Oracle Sales Representative or Account Representative.

Note:

A cluster point code cannot be a proxy point code.

If you wish to use the following parameters of the EAGLE’s ent-dstn command: nprst, rcause, sccpmsgcnv, or splitiam parameters, perform the “Adding a Cluster Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The EAGLE accepts the values for the ncai parameter as a supplier specific parameters. Table 2-1 shows how the EAGLE ncai parameter values are mapped to the SEAS values. For more information on the ncai parameter, see “Adding a Cluster Point Code” in Database Administration - SS7 User's Guide.

Table 2-1 NCAI Supplier Specific Parameter Values

Supplier Specific Parameters EAGLE Parameter Value SEAS Parameter Value Definition

NCAI

YES

NO

1

0

The nested cluster allowed indicator. This parameter specifies whether or not the route to the cluster point code can be different from the route to a point code that is a member of the cluster point code.

The supplier specific parameter is optional. The default value for the supplier specific parameter will be entered if that parameter is not specified when adding a cluster point code. The default value for the NCAI parameter is NO.

To change the attributes of an existing cluster point code, perform the Changing the Attributes of a Cluster Point Code procedure.

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

Figure 2-1 Adding a Cluster Point Code from the SEAS Terminal

Note:

Before executing this procedure, make sure you have purchased the cluster routing and management diversity and nested cluster routing features. If you are not sure if you have purchased the cluster routing and management diversity or nested cluster routing features, contact your Oracle Sales Representative or Account Representative.


Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

2.2 Changing the Attributes of a Cluster Point Code

This procedure is used to change the attributes of a cluster point code for the cluster routing and management diversity feature to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Changing the Attributes of a Cluster Point Code” in Database Administration - SS7 User's Guide.

Note:

Once the nested cluster routing feature is turned on with the chg-feat command, it cannot be turned off.

If you plan to use the supplier specific parameter ncai with this procedure, the nested cluster routing feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure whether you have purchased the nested cluster routing feature, contact your Oracle Sales Representative or Account Representative.

If you wish to use the following parameters of the EAGLE’s chg-dstn command: nprst, rcause, sccpmsgcnv, or splitiam parameters, perform the "Changing the Attributes of a Cluster Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The EAGLE accepts the values for the ncai parameter as a supplier specific parameters. Table 2-2 shows how the EAGLE ncai parameter values are mapped to the SEAS values. For more information on the ncai parameter, see “Changing the Attributes of a Cluster Point Code” in Database Administration - SS7 User's Guide.

Table 2-2 NCAI Supplier Specific Parameter Values

Supplier Specific Parameters EAGLE Parameter Value SEAS Parameter Value Definition

NCAI

YES

NO

1

0

The nested cluster allowed indicator. This parameter specifies whether or not the route to the cluster point code can be different from the route to a point code that is a member of the cluster point code.

The supplier specific parameter is optional. The current value of any supplier specific parameter is not changed if the supplier specific parameter is not specified.

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

Figure 2-2 Changing the Attributes of a Cluster Point Code from the SEAS Terminal

Note:

If you plan to use the supplier specific parameter ncai with this procedure, before executing this procedure, make sure you have purchased the nested cluster routing feature. If you are not sure if you have purchased the nested cluster routing feature, contact your Oracle Sales Representative or Account Representative.


Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

2.3 Adding a Network Routing Point Code

This procedure is used to add a network routing point code for the network routing feature to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, rtrv-dstn, rtrv-ctrl-feat, rtrv-sid, and chg-db. For more information on this procedure, see “Adding a Network Routing Point Code” in Database Administration – SS7 User's Guide.

Notes:
  1. Once the network routing feature is turned on with the chg-feat command, it cannot be turned off.

    The network routing feature must be purchased before you turn the features on with the chg-feat command. If you are not sure whether you have purchased the network routing feature, contact your Oracle Sales Representative or Account Representative.

  2. A network routing point code cannot be a proxy point code.

If you wish to use the following parameters of the EAGLE’s ent-dstn command: nprst, rcause, sccpmsgcnv, or splitiam parameters, perform the “Adding a Network Routing Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

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.

Note:

Before executing this procedure, make sure you have purchased the network routing feature. If you are not sure if you have purchased the network routing feature, contact your Oracle Sales Representative or Account Representative.

Figure 2-3 Adding a Network Routing Point Code from the SEAS Terminal



Sheet 1 of 2



Sheet 2 of 2

2.4 Changing the Self Identification of the EAGLE

This procedure is used to change the self identification of the EAGLE. For more information on this procedure, see the “Changing the Self Identification of the EAGLE” procedure in Database Administration - SS7 User's Guide. This procedure uses these EAGLE commands.

If you wish to use the cpctype, pctype, pci, pcn, or pcn24 parameters of the EAGLE’s chg-sid command, perform the “Changing the Self Identification of the EAGLE” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Caution:

Use this procedure only during periods of low traffic. If the EAGLE’s point code is changed with the procedure, the EAGLE must be reinitialized with the EAGLE’s init-sys command. The init-sys command reboots the entire EAGLE and reloads all cards with the updated self identification information.

Caution:

When the init-sys command executes, the state of the signaling links, TCP/IP data links, cards, and terminals after the init-sys command executes depends on whether the restore device state option is on or off. The value of this option is shown in the RSTRDEV field of the rtrv-stpopts output.

If the value of the restore device state option is off, the EAGLE does not retain the manually initiated state (for example, OOS-MT-DSBLD) for the signaling links, TCP/IP data links, cards, or the terminals. After the command executes, the EAGLE attempts to bring all provisioned links, cards, and terminals on line, including those that were previously out of service. You will need to manually put each device back into its previous state after the EAGLE is back on line. It is, therefore, advisable to print or electronically capture the output of the EAGLE’s rept-stat-slk, rept-stat-dlk, rept-stat-card, and rept-stat-trm commands for reference prior to issuing the init-sys command. To restore a device to its previous state, issue the appropriate inhibit/deactivate command listed in Commands User's Guide in the Related Commands section for each of the above rept-stat commands.

If the value of the restore device state option is on, the state the signaling links, TCP/IP data links, cards, and terminals is not changed after the init-sys command is performed. No manual intervention is required to put the device back into its previous state after the EAGLE is back on line.

To change the value of the restore device state option, perform the “Changing the Restore Device State Option” procedure in Database Administration - System Management User's Guide.

Figure 2-4 Changing the Self Identification of the EAGLE from the SEAS Terminal



Sheet 1 of 5



Sheet 2 of 5



Sheet 3 of 5



Sheet 4 of 5



Sheet 5 of 5

2.5 Adding a Destination Point Code

This procedure is used to add a destination point code to the database. This procedure uses the EAGLE commands rtrv-feat, rtrv-dstn, rtrv-ctrl-feat, and chg-db. For more information on this procedure, see “Adding a Destination Point Code” in Database Administration - SS7 User's Guide.

If you wish to use the following parameters of the EAGLE’s ent-dstn command: dpci, dpcn, dpcn24, domain, aliasa, aliasi, aliasn, aliasn24, spc, spca, spci, spcn, spcn24, prx=yes, ppc, ppca, ppci, ppcn, ppcn24, nprst, rcause, splitiam, homesmsc, homescp, sccpmsgcnv, or ipgwapc, or if spare point codes are being added, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

If you wish to use the ncai parameter the EAGLE’s ent-dstn command or configure a cluster point code, perform the Adding a Cluster Point Code procedure.

Figure 2-5 Adding a Destination Point Code from the SEAS Terminal



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

2.6 Removing a Destination Point Code

This procedure is used to remove a destination point code from the database. This procedure uses the EAGLE commands rtrv-dstn , rtrv-feat, rtrv-map, rtrv-mrn, rtrv-rmt-appl, rtrv-ctrl-feat, rtrv-rtx, and chg-db. For more information on this procedure, see “Removing a Destination Point Code” in Database Administration - SS7 User's Guide.

If you wish to remove an ITU international, ITU national destination point code, or a proxy point code from the database, perform the “Removing a Destination Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Figure 2-6 Removing a Destination Point Code from the SEAS Terminal



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

2.7 Changing a Destination Point Code

This procedure is used to change a destination point code in the database. This procedure uses the EAGLE commands rtrv-dstn and chg-db. For more information on this procedure, see “Changing a Destination Point Code” in Database Administration - SS7 User's Guide.

If you wish to change the attributes of an ITU international, or ITU national destination point code (either a 14-bit ITU-N or 24-bit ITU-N point code), change the attributes of a proxy point code, or use the ncai, alias, aliasa, aliasi, aliasn, aliasn24, spc, spca, spci, spcn, spcn24, nprst, rcause, splitiam, homesmsc, homescp, sccpmsgcnv, or prx=yes parameters of the EAGLE’s chg-dstn command, perform the “Changing a Destination Point Code” procedure in Database Administration - SS7 User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Figure 2-7 Changing a Destination Point Code from the SEAS Terminal