Adding an Allowed SIO Screen

This procedure is used to add an allowed signaling information octet (SIO) screen to the database using the ent-scr-sio command. The parameters used by the ent-scr-sio 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 examples in this procedure are used to add the allowed SIO screen data shown in Table 10-2 and based on the example configurations shown in Figure 2-4, Figure 2-6, Figure 2-7, Figure 2-8, and Figure 2-9.

Table 10-2 Example Gateway Screening Allowed SIO Configuration Table

Screening Reference	NIC	SI	H0	H1	PRI	NSFI	NSR
fld4	2	0	4	5	3	destfld	fld5
iec	2	3	--	--	1&&3	cgpa	gw11
ls02	2	3	--	--	3	cdpa	ls03
isp1	2	5	--	--	3	isup	isp1
tup1	2	4	--	--	3	dpc	tup1
tup1	2	5	--	--	3	dpc	isp2

The allowed SIO screen can reference one of the following screens.

Allowed DPC
Blocked DPC
Allowed Affected Destination Field
Allowed ISUP Message Type
Allowed CGPA
Allowed CDPA

Verifying the Gateway Screening Configuration

Enter the following commands to verify that these screens are in the database.

rtrv-scr-dpc:all=yes
rtrv-scr-blkdpc:all=yes
rtrv-scr-destfld:all=yes
rtrv-scr-isup:all=yes
rtrv-scr-cgpa:all=yes
rtrv-scr-cdpa:all=yes

Gateway Screening Configuration Procedures

If the desired screen is not in the database, perform one of these procedures to add the desired screen to the database or change an existing screen in the database.

Specifying a Range of Values

A range of values can be specified for the pri, h0, and h1 parameters. If a range of values is specified for any of these parameters and the nic and si values in the screening reference name are not changed, the range of values for the pri, h0, or h1 parameters cannot include any values that are currently provisioned for the screening reference name.

For example, screening reference name scr1 contains these entries:

SR    NIC  PRI  SI  H0     H1     NSFI    NSR/ACT
SCR1  2    3    1    4      5     DPC     LS03
SCR1  2    2    1    2      7     BLKDPC  LS04

Another entry for screening reference scr1 with the same nic and si values cannot be specified if:

The range of values for the pri parameter includes the values 2 or 3
The range of values for the h0 parameter includes the values 2 or 4
The range of values for the h1 parameter includes the values 5 or 7.

Specifying H0 and H1 Values

The h0 and h1 values must be specified if the si value is 0, 1, or 2. If the si value is 3 through 15, the h0 and h1 parameters cannot be specified.

The h0 and h1 parameters must be specified if either parameter is specified.

The H0 and H1 heading code values can be a single value, a range of values with the beginning and end of the range separated by double ampersands (for example, a range of values from 2 to 9, 2&&9), or with an asterisk (*). The asterisk specifies all possible values for the h0 and h1 parameters. Table 10-3 shows the valid combinations of these parameter values.

Table 10-3 Valid Value Combinations for H0 and H1 Parameters

H0	H1
Single Value	Single Value
Single Value	Range of Values
Single Value	Asterisk
Range of Values	Asterisk
Asterisk	Asterisk

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

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 SIO screens in the database using the rtrv-scr-sio command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED SIO
SR    REF  RULES
IEC   YES     5
WRD2  YES     1
WRD4  YES     9
```
If the screening reference names that you wish to add with this procedure are not shown in the rtrv-scr-sio command output, go to either steps 4 or 5.

Step 4 verifies the gateway screening stop action set names in the database. The gateway screening stop action set names are assigned only if the NSFI of the screen being added in this procedure is STOP. If the NSFI of the new screen will be STOP, but a gateway screening stop action set name will not be assigned to the new screen, skip steps 4 and 5 and go to step 6. If the NSFI of the new screen is not STOP, skip step 4 and go to step 5.

If these screening reference names are shown in the rtrv-scr-sio command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-sio command with the screening reference name. In this example, screen iec will have new data added to it. For this example, enter the rtrv-scr-sio: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 SIO
SR    NIC  PRI  SI  H0     H1     NSFI    NSR/ACT
IEC   2    0&&3 0   0      0      BLKDPC  WDB2
IEC   2    0&&2 0   1      1      DPC     WDB3
IEC   2    0&&1 0   2      2      STOP    ------
IEC   2    0&&3 4   --     --     STOP    ------
IEC   2    0&&2 1   *      *      DPC     WDB3
```

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

Note:

If theNSFI of the screen being added in this procedure isSTOP, skip step 5 and go to step 6.

Enter the commands in the Verifying the Gateway Screening Configuration section to verify that the screen that will be specified by the NSFI/NSR parameter combination in step 6 is in the database.
If the desired screen is not in the database, perform one of the procedures shown in the Gateway Screening Configuration Procedures section to add the desired screen to the database or change an existing screen in the database.
Add a new allowed SIO screen to the database using the ent-scr-sio command.
If a gateway screening stop action set is to be assigned to the new allowed SIO screen, enter the ent-scr-sio 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.

Caution:
RedirectingSLTA/SLTMmessages preventsSLTA/SLTMmessages from being returned to theEAGLE. The signaling link carrying these messages will fail if these messages are not returned to theEAGLE. To preventSLTA/SLTMmessages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned toAllowed SIO screens containing the service indicator values 1 (SI=1) or 2 (SI=2).

The following list contains the values for nic, si, pri, h0 and h1 parameters:
- nic – 0 - 3, or an asterisk (*)
- si – 0 - 15
- pri – 0 - 3, or an asterisk (*)
- h0 – 0 - 15, or an asterisk (*)
- h1 – 0 - 15, or an asterisk (*)
A range of values can be specified for the pri, h0, and h1 parameters. See the “Specifying a Range of Values” section for more information. See the “Specifying H0 and H1 Values” section for information on how the asterisk and a range of values are used for the h0 and h1 parameters.

The value of the nsfi parameter is based on the value of the service indicator (si) parameter. Table 10-1 shows the valid combinations of nsfi values and service indicator values. For this example, enter these commands.

ent-scr-sio:sr=fld4:nic=2:si=0:h0=4:h1=5:pri=3:nsfi=destfld :nsr=fld5

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```
ent-scr-sio:sr=iec:nic=2:si=3:pri=1&&3:nsfi=cgpa:nsr=gw11

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```
ent-scr-sio:sr=ls02:nic=2:si=3:pri=3:nsfi=cdpa:nsr=ls03

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```
ent-scr-sio:sr=isp1:nic=2:si=5:pri=3:nsfi=isup:nsr=isp1

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```
ent-scr-sio:sr=tup1:nic=2:si=4:pri=3:nsfi=dpc:nsr=tup1

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```
ent-scr-sio:sr=tup1:nic=2:si=5:pri=3:nsfi=dpc:nsr=isp2

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-SIO: MASP A - COMPLTD
```

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

For this example, enter these commands.

rtrv-scr-sio:sr=iec