Changing an Allowed ISUP Message Type Screen

This procedure is used to change the attributes of an allowed ISUP message type (ISUP) screen in the database using the chg-scr-isup command. The parameters used by the chg-scr-isup command are shown in the Gateway Screening Attributes section. The general rules that apply to configuring gateway screening entities are shown in the Gateway Screening Configuration section.

The example in this procedure is used to change the ISUP message type 135 for the allowed ISUP screen isp1 to 075 and to redirect the MSU for the DTA feature.

Display the allowed ISUP screens in the database using the rtrv-scr-isup command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED ISUP
SR    REF  RULES
IEC   YES     2
ISP1  YES     3
ISP2  YES     2
TUP1  YES     1
WRD2  YES     1
WRD4  YES     1
```
From the rtrv-scr-isup output, display the allowed ISUP screen you wish to remove using the rtrv-scr-isup command with the screening reference name. For this example, enter this command.

rtrv-scr-isup:sr=isp1

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED ISUP
SR   ISUPMT/   NSFI    NSR/ACT
     TUPMT
isp1 002       STOP    copy
isp1 089       STOP    ------
isp1 135       STOP    cr
```
If a gateway screening stop action set is to be assigned to the allowed ISUP screen being changed in the database, go to step 2.

Step 2 verifies the gateway screening stop action set names in the database. If a gateway screening stop action set name will not be assigned to the screen, skip step 2 and go to step 3.

Display the gateway screening stop action sets in the database with the rtrv-gws-actset command.

This is an example of the possible output.

rlghncxa03w 06-10-25 15:26: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    cncf   cncf      
5    cpcncf copy cncf 
6    cncfrd cncf rdct 
7    cpcfrd copy cncf rdct

GWS action set table is (7 of 16) 44% full

If the required gateway screening stop action set is not in the database, perform the Configuring Gateway Screening Stop Action Sets procedure to configure the required gateway screening stop action set.

Change the attributes of an allowed ISUP screen using the chg-scr-isup command.
If a gateway screening stop action is to be assigned to the allowed ISUP screen being changed, enter the chg-scr-isup command with the nsfi=stop parameter and the actname parameter with the name of a gateway screening stop action set shown in the output of the rtrv-gws-actset command executed in step 2.

The value of the isupmt or tupmt parameter must be entered exactly as shown in the rtrv-scr-isup output in step 1.

The nisupmt or ntupmt parameter can have these values: 0 - 255, or an asterisk (*).

A range of ISUP or TUP message types can be specified with the chg-scr-isup command. If a range of ISUP message types is specified, the range of ISUP message types cannot include any ISUP message types that are currently provisioned for the screening reference name. If a range of TUP message types is specified, the range of TUP message types cannot include any TUP message types that are currently provisioned for the screening reference name.

For example, screening reference name scr1 contains these entries:
```
SR   ISUPMT/   NSFI    NSR/ACT
     TUPMT
scr1 115       STOP    cr
scr1 203       STOP    cr
```
Another entry for screening reference scr1 cannot be specified if the range of ISUP message types includes the values 115 and 203. For this example, enter this command.

chg-scr-isup:sr=isp1:isupmt=135:nisupmt=075:actname=rdct

The following messages appear.
```
rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
CHG-SCR-ISUP: SCREEN SET AFFECTED - ISP1  1% FULL
CHG-SCR-ISUP: MASP A - COMPLTD
```
Verify the changes using the rtrv-scr-isup command with screening reference name used in step 3.
For this example, enter this command.

rtrv-scr-isup:sr=isp1

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED ISUP
SR   ISUPMT/   NSFI    NSR/ACT
     TUPMT
isp1 002       STOP    copy
isp1 075       STOP    rdct
isp1 089       STOP    ------
```

Backup the new changes using the chg-db:action=backup:dest=fixed command.

The following 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 14-5 Changing an Allowed ISUP Message Type Screen

Sheet 1 of 2

Sheet 2 of 2