Configuring TLNP Gateway Screening Stop Action Sets

This procedure is used to add a gateway screening stop action set containing the TLNP gateway screening stop action to the database using the chg-gws-actset command.

The gateway screening stop action sets define the actions that are performed on the MSU when the gateway screening process has stopped.

The database can contain a maximum of 16 gateway screening stop action sets, with each set containing a maximum of 10 gateway screening stop actions. For this procedure only two gateway screening stop actions can be used.

COPY – copy the MSU for the STPLAN feature
TLNP – ISUPIAMs that pass gateway screening are processed either by the ISUP NP with EPAP feature (if the ISUP NP with EPAP feature is enabled and turned on) or by the Triggerless LNP feature (if the LNP feature is enabled and the Triggerless LNP feature is turned on). The ISUP NP with EPAP feature is discussed in more detail in G-Port User's Guide. The Triggerless LNP feature is discussed in more detail in ELAP Administration and LNP Feature Activation Guide.
The status of the ISUP NP with EPAP feature can be verified with the rtrv-ctrl-feat command. The ISUP NP with EPAP feature also requires that the G-Port feature is enabled and that Gateway Screening feature is turned on. The status of the G-Port feature can be verified with the rtrv-ctrl-feat command. The status of the Gateway Screening feature can be verified with the rtrv-feat command. Enabling the G-Port feature is discussed in more detail in G-Port User's Guide.

Caution:
When Gateway Screening is in the screen test mode, as defined by the linkset parametersgwsa=off andgwsm=on, any action in the gateway screening stop action sets created in this procedure will be performed.

The chg-gws-actset command in this procedure uses these parameters.

:actid – The ID number of the gateway screening stop action set. The value of this parameter is from 4 to 16.

:actname – The name of the gateway screening stop action set consisting of 1 alphabetic character followed by up to 5 alphanumeric characters. The word none cannot be used for the actname parameter.

:force – The force=yes parameter must be specified when changing the gateway screening stop actions of an existing gateway screening stop action set.

:act1 and :act2 – Only two gateway screening stop action sets can be defined with the TLNP gateway screening stop action:

One set with only the TLNP gateway Screening stop action (defined with the act1=tlnp parameter).
Another set with the COPY and TLNP gateway screening stop action (defined by the act1=copy and act2=tlnp parameters).

The value of the actname parameter must be unique. The value of this parameter is used by the actname parameter in the gateway screening commands and is shown in the NSR/ACT field of the outputs of the retrieve gateway screening commands to define the action that is performed on the MSU that passes gateway screening.

When a gateway screening stop action set is being entered into the database for the first time, the name of the gateway screening stop action set (actname) must be added to the database before any gateway screening stop actions are assigned to the gateway screening stop action set.

The tlnp gateway screening stop action cannot be specified with either the cncf (calling name conversion facility) or rdct (redirect) gateway screening actions in the same gateway screening action set.

Table 2-12 Sample TLNP Gateway Screening Stop Action Set Configuration

ACTID	ACTNAME	ACT1	ACT2	ACT3
4	TLNP	tlnp	—	—
5	CPNP	copy	tlnp	—

Verify that the gateway screening feature is turned on, by entering the rtrv-feat command.
If the gateway screening feature is turned on, the GWS field should be set to on. In this example, the gateway screening 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 inCommands User's Guide.

If the gateway screening feature is turned on, go to step 3.
If the gateway screening feature is not turned on, shown by the GWS = off entry in the rtrv-feat command output in step 1, turn it on by entering this command.
chg-feat:gws=on

Note:
Once the gateway screening feature is turned on with thechg-feat command, it cannot be turned off.

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-25 15:26:30 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
```
Display the gateway screening stop action sets in the database with the rtrv-gws-actset command.
Action IDs 1, 2, and 3 are predefined and cannot be changed. Action ID 1 contains only the COPY stop action. Action ID 2 contains the RDCT stop action. Action ID 3 contains the COPY and the RDCT stop actions as shown in the following output example.
```
rlghncxa03w 06-10-25 15:27:30 GMT EAGLE5 36.0.0
ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
ID   NAME   1    2    3    4    5    6    7    8    9    10
--   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
1    copy   copy
2    rdct   rdct
3    cr     copy rdct

GWS action set table is (3 of 16) 19% full
```
If the rtrv-gws-actset output shows that these gateway screening stop action sets: one with ACT1=tlnp and the other with ACT1=copy and ACT2=tlnp, this procedure cannot be performed.

If only one of these gateway screening stop action sets are shown, skip steps 4 through 11, and go to step 12.

If neither of these gateway screening stop action sets are shown, go to step 4.
Verify whether or not the LNP or ISUPNP with EPAP features are enabled, using the rtrv-ctrl-feat command.
If the LNP feature is enabled, the LNP TNs field with a telephone number quantity greater than zero is shown in the rtrv-ctrl-feat output. If the ISUP NP with EPAP feature is enabled, the ISUP NP with EPAP Active field is shown in the rtrv-ctrl-feat output.

This is an example of the possible output.
```
rlghncxa03w 06-10-30 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Command Class Management  893005801  off     ----
Intermed GTT Load Sharing 893006901  off     ----
XGTT Table Expansion      893006101  off     ----
XMAP Table Expansion      893007710  on      3000
Large System # Links      893005910  on      2000
Routesets                 893006401  on      6000
GSM MAP SRI Redirect      893014001  on      ----
ISUP NP with EPAP Active  893013801  on      ----
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.
```
If the ISUP NP with EPAP feature is enabled, skip steps 5 through 10, and go to step 11.

If the LNP feature is enabled, perform the “Configuring the Triggerless LNP Feature” procedure in ELAP Administration and LNP Feature Activation Guide.

If neither the ISUP NP with EPAP or the LNP features are enabled, perform the “Configuring the Triggerless LNP Feature” procedure in ELAP Administration and LNP Feature Activation Guide to use the tlnp gateway screening stop action for the Triggerless LNP feature.

To use the tlnp gateway screening stop action for the ISUP NP with EPAP feature, and neither the ISUP NP with EPAP or the LNP features are enabled, verify that the G-Port feature is enabled. If the G-Port feature is enabled, the entry GPORT is shown in the rtrv-ctrl-feat output. If the G-Port feature is not enabled, go to G-Port User's Guide and enable the G-Port feature. Then go to step 5.

If the G-Port feature is enabled, go to step 5.

Note:
If thertrv-ctrl-feat output in step 4 shows any controlled features, skip steps 5, 6, 7, and 8, and go to step 9.

Note:
If thertrv-ctrl-feat output shows only theHC-MIMSLK Capacity feature with a quantity of 64, then no other features are enabled. Steps 5, 6, 7, and 8 must be performed.
Display the serial number in the database with the rtrv-serial-num command.
This is an example of the possible output.
```
rlghncxa03w 06-10-30 21:15:37 GMT EAGLE5 36.0.0
System serial number = ntxxxxxxxxxxxxx

System serial number is not locked.

rlghncxa03w 06-10-30 21:15:37 GMT EAGLE5 36.0.0
Command Completed
```
Note:
If the serial number is locked, skip step 6 and go to step 7.

Note:
If the serial number is correct and locked, skip steps 6, 7, and 8, and go to step 9. If the serial number is correct but not locked, skip steps 6 and 7, and go to step 8. If the serial number is not correct, but is locked, the ISUP NP with EPAP feature cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer toMy Oracle Support (MOS)for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.
For this example, enter this command.

ent-serial-num:serial=<EAGLE’s correct serial number>

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
```
Verify that the serial number entered into step 6 was entered correctly using the rtrv-serial-num command.
This is an example of the possible output.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked.
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
Command Completed
```
If the serial number was not entered correctly, repeat steps 6 and 7 and re-enter the correct serial number.
Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in step 5, if the serial number shown in step 5 is correct, or with the serial number shown in step 7, if the serial number was changed in step 6, and with the lock=yes parameter.
For this example, enter this command.

ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
```
Enable the ISUP NP with EPAP feature by entering the enable-ctrl-feat command.
For this example, enter this command.

enable-ctrl-feat:partnum=893013801:fak=<feature access key>

Note:
The values for the feature access key (thefak parameter) are provided by Oracle. If you do not have the controlled feature part number or the feature access key for the feature you wish to enable, contact your Oracle Sales Representative or Account Representative.

When the enable-ctrl-feat command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-30 21:15:37 GMT EAGLE5 36.0.0
ENABLE-CTRL-FEAT: MASP B - COMPLTD
```
Verify the changes by entering the rtrv-ctrl-feat command with the part number specified in step 9.
rtrv-ctrl-feat:partnum=893013801

The following is an example of the possible output.
```
rlghncxa03w 06-10-30 21:16:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
ISUP NP with EPAP         893013801  off         ----
```
Note:
If the TLNP feature is on, shown in thertrv-feat output in step 1, skip this step and step 12, and go to step 13.
Turn the TLNP feature on by entering this command.
chg-feat:tlnp=on

Note:
Once the TLNP feature is turned on with thechg-feat command, it cannot be turned off.

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-25 15:26:30 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
```
Add the TLNP gateway screening stop action to the database by using the chg-gws-actset command.
For this example, enter these commands based on the sample configuration shown in Table 2-12.

chg-gws-actset:actid=4:actname=tlnp:act1=tlnp

chg-gws-actset:actid=5:actname=cpnp:act1=copy:act2=tlnp

If an existing gateway screening stop action set is being changed, the force=yes parameter must be specified with the chg-gws-actset command.

The force=yes parameter can be specified with the chg-gws-actset command if a new GWS stop action set is being created, but is not necessary.

The actname parameter must be specified for a new GWS stop action set.

The actname parameter is not required, but can be specified, if an existing stop action set is being changed.

If the actname parameter value is different from what is shown in the rtrv-gws-actset output for the GWS stop action set being changed, the name of the GWS stop action set will be changed to the new actname parameter value (see the first Caution).

Caution:
Changing the name of an existing GWS stop action set will prevent the actions defined in the GWS stop action set from being used to process the MSUs that pass gateway screening. If the name of GWS stop action set is changed, enter the gateway screening retrieve commands shown inTable 2-13with theactname parameter and the old GWS stop action set name to identify the screens that need to be changed to use the new GWS stop action set name. To change these screens, perform the appropriate procedures in this manual.

Table 2-13 Gateway Screening Retrieve Commands

rtrv-scrset rtrv-scr-opc rtrv-scr-blkopc rtrv-scr-sio

rtrv-scr-dpc rtrv-scr-blkdpc rtrv-scr-destfld rtrv-scr-isup

rtrv-scr-cgpa rtrv-scr-tt rtrv-scr-cdpa rtrv-scr-aftpc

Caution:
Caution must be used when changing the stop actions in existing gateway screening stop action sets because these gateway screening stop action sets may be used by one or more gateway screening rules. Changes in the existing gateway screening stop action sets will change howMSUs that pass gateway screening are processed.

When each of these commands have successfully completed, this message should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT EAGLE5 36.0.0
CAUTION: GWS action set may be referenced by one or more GWS rules
CHG-GWS-ACTSET: MASP A - COMPLTD
```

Verify the changes using the rtrv-gws-actset command.

This is an example of the possible output.

rlghncxa03w 06-10-25 15:31:30 GMT EAGLE5 36.0.0
ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
ID   NAME   1    2    3    4    5    6    7    8    9    10
--   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
1    copy   copy      
2    rdct   rdct      
3    cr     copy rdct 
4    tlnp   tlnp
5    cpnp   copy tlnp

GWS action set table is (5 of 16) 31% full

Backup 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-13 Configuring TLNP Gateway Screening Stop Action Sets

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

`rtrv-scrset`	`rtrv-scr-opc`	`rtrv-scr-blkopc`	`rtrv-scr-sio`
`rtrv-scr-dpc`	`rtrv-scr-blkdpc`	`rtrv-scr-destfld`	`rtrv-scr-isup`
`rtrv-scr-cgpa`	`rtrv-scr-tt`	`rtrv-scr-cdpa`	`rtrv-scr-aftpc`