Adding an Allowed ISUP Message Type Screen

This procedure is used to add an allowed ISUP message type (ISUP) screen to the database using the ent-scr-isup command. The parameters used by the ent-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.

Since both ISUP and TUP messages are screened by the allowed ISUP message type screen, the ent-scr-isup command contains a parameter for the ISUP message type (isupmt) and a parameter for the TUP message type (tupmt). Only one of these parameters can be specified for the allowed ISUP screen being entered into the database. The isupmt parameter should be specified in screen sets that contain allowed SIO screens that are screening messages for the service indicator value of 5 (SI=5). The tupmt parameter should be specified in screen sets that contain allowed SIO screens that are screening messages for the service indicator value of 4 (SI=4). If you wish to screen for TUP messages, make sure that the screen set being configured contains an allowed SIO screen that screens messages for the service indicator value of 4 (SI=4). If you do not do this, the EAGLE will treat the message as an ISUP message, even if the message contains the service indicator value of 4.

The examples in this procedure are used to add the allowed ISUP screen data shown in Table 14-1 and based on the example configuration shown in Figure 2-8 and Figure 2-9.

Table 14-1 Example Gateway Screening Allowed ISUP Configuration Table

Screening Reference	ISUPMT	NSFI	ACTNAME
isp1	135	stop	CR
isp2	139	stop	CR
Screening Reference	TUPMT	NSFI	ACTNAME
tup1	100	stop	CR

Verify that the gateway screening feature is on, by entering the rtrv-feat command.
If the gateway screening feature is on, the GWS field is set to on.

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 on, shown by the entry GWS = on in the rtrv-feat command output, skip step 2, and go to step 3.
Turn the gateway screening feature 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.
The gateway screening 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 gateway screening feature, contact your Oracle Sales Representative or Account Representative.

When the chg-feat has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 11:43:04 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
```
Display all 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
WRD2  YES     1
WRD4  YES     1
```
If the screening reference names that you wish to add with this procedure are not shown in the rtrv-scr-isup command output, go to step 4. For this example, the screening reference names are not shown. If these screening reference names are shown in the rtrv-scr-isup command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-isup command with the screening reference name. For example, enter the rtrv-scr-isup:sr=iec command. The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:26:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED ISUP
SR   ISUPMT/   NSFI    NSR/ACT
     TUPMT
iec  100       STOP    cr
iec  197       STOP    cr
```
If a gateway screening stop action set is to be assigned to the allowed ISUP screen being added to the database, go to step 4. Otherwise, go to step 5.

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

Add a new allowed ISUP screen to the database using the ent-scr-isup command.
For this example, enter this command.

ent-scr-isup:sr=isp1:isupmt=135:nsfi=stop:actname=cr
A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-ISUP: SCREEN SET AFFECTED - ISP1  1% FULL
ENT-SCR-ISUP: MASP A - COMPLTD
```
ent-scr-isup:sr=isp2:isupmt=139:nsfi=stop:actname=cr

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-ISUP: SCREEN SET AFFECTED - ISP2  1% FULL
ENT-SCR-ISUP: MASP A - COMPLTD
```
ent-scr-isup:sr=tup1:tupmt=100:nsfi=stop:actname=cr

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-ISUP: SCREEN SET AFFECTED - TUP1  1% FULL
ENT-SCR-ISUP: MASP A - COMPLTD
```
If a gateway screening stop action is to be assigned to the allowed ISUP screen being changed, enter the ent-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 4. The isupmt or tupmt parameters can have these values: 0 - 255, or an asterisk (*). A range of ISUP or TUP message types can be specified with the ent-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.

Verify the changes using the rtrv-scr-isup command with the screening reference name used in step 5.

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 135       STOP    cr

rtrv-scr-isup:sr=isp2

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
isp2 139       STOP    cr

rtrv-scr-isup:sr=tup1

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
tup1 100       STOP    cr

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-3 Adding an Allowed ISUP Message Type Screen

Sheet 1 of 3

Sheet 2 of 3

Sheet 3 of 3