Adding an Allowed Translation Type Screen

This procedure is used to add an allowed translation type (TT) screen to the database using the ent-scr-tt command. The parameters used by the ent-scr-tt 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 TT screen data shown in Table 5-1 and based on the example configuration shown in Figure 2-5.

Table 5-1 Example Gateway Screening Allowed TT Configuration Table

Screening Reference	TYPE	NSFI	NSR
gw16	250	cdpa	gw18

The allowed TT screen can only reference an allowed CDPA screen and the allowed CDPA screen being referenced must be in the database. This can be verified using the rtrv-scr-cdpa:all=yes command. If the desired allowed CDPA screen is not in the database, perform one of these procedures to add the required 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 type parameter. The range of values specified for the type parameter cannot include any values currently provisioned for the screen reference name.

For example, screening reference name scr1 contains these entries:

SR   TYPE      NSFI    NSR/ACT
scr1 110       STOP    ------
scr1 125       STOP    ------

Another entry for screening reference scr1 cannot contain a range of values that would include the type parameter values 110 or 125.

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:
The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-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 the chg-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 TT screens in the database using the rtrv-scr-tt command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED TT
SR    REF  RULES
IEC   YES     2
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-tt 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-tt command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-tt command with the screening reference name. For example, enter the rtrv-scr-tt: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 TT
SR    TYPE     NSFI   NSR/ACT
IEC   005&&010 STOP   ------
IEC   012      STOP   ------
IEC   016      CDPA   IEC
WRD2  243      STOP   ------
WRD4  *        STOP   ------
```
If a gateway screening stop action set is to be assigned to the allowed TT screen being added to the database, go to step 4.

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 CDPA, skip step 4 and 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: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 rtrv-scr-cdpa command 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 these procedures to add the desired screen to the database or change an existing screen in the database.
- Adding an Allowed Called Party Address Screen
- Changing an Allowed Called Party Address Screen.
Add a new allowed TT screen to the database using the ent-scr-tt command.
If a gateway screening stop action is to be assigned to the allowed TT screen being changed, enter the ent-scr-tt 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:
The EAGLE does not support redirecting MSUs for the DTA feature or intercepting ISUP IAM messages for the Calling Name Conversion Facility feature from the allowed TT screen. Gateway screening stop action sets containing either the RDCT (redirect) or CNCF (calling name conversion facility) stop actions should not be assigned to the allowed TT screen. If a gateway screening stop action set containing the RDCT or CNCF stop actions is specified with the ent-scr-tt command, unsolicited information message (UIM) 1128 is generated when the attempt is made to redirect MSUs from the allowed TT screen. Unsolicited information message (UIM) 1218 is generated when ISUP IAM MSUs are intercepted from the allowed TT screen. For more information on UIMs 1128 and 1218, go to the Unsolicited Alarm and Information Messages Reference.

The value of the type parameter can be from 0 to 255 or an asterisk (*).

A range of values can be specified for the type parameter. See the Specifying a Range of Values section for more information on how a range of values is used for the type parameter.

For this example, enter this command.

ent-scr-tt:sr=gw16:type=250:nsfi=cdpa:nsr=gw18

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
ENT-SCR-TT: SCREEN SET AFFECTED - GW16  1% FULL
ENT-SCR-TT: MASP A - COMPLTD
```
Verify the changes using the rtrv-scr-tt command with the screening reference name used in step 6.
For this example, enter this command.

rtrv-scr-tt:sr=gw16

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED TT
SR    TYPE     NSFI   NSR/ACT
GW16  250      CDPA   GW18
```

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 5-5 Add an Allowed Translation Type Screen - Sheet 1 of 3

Figure 5-6 Add an Allowed Translation Type Screen - Sheet 2 of 3

Figure 5-7 Add an Allowed Translation Type Screen - Sheet 3 of 3