Adding an Allowed Called Party Address Screen

This procedure is used to add an allowed called party address (CDPA) screen to the database using the ent-scr-cdpa command. The parameters used by the ent-scr-cdpa 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 CDPA screen data shown in Table 4-1 and based on the example configurations shown in Figure 2-3 through Figure 2-6.

Table 4-1 Example Gateway Screening Allowed CDPA Configuration Table

Screening Reference	ZONE	AREA	ID	SSN	SCMGFID	NSFI	NSR
gw15	5	117	2	254	----	stop	----

Screening Reference	NI	NC	NCM	SSN	SCMGFID	NSFI	NSR
gw17	003	003	003	001	050	aftpc	gw20
gw18	006	006	006	253	----	stop	----
ls03	007	007	007	001	100	aftpc	ls04

Note:

If you using multiple-part ITU national point codes with gateway screening, see the 14-Bit ITU National Point Code Formats section.

The allowed CDPA screen can only reference an allowed AFTPC screen and the allowed AFTPC screen being referenced must be in the database. This can be verified using the rtrv-scr-aftpc:all=yes command. If the desired allowed AFTPC 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 point code parameters ni, nc, or ncm.

If a range of values is specified for any of these parameters, and the value of the other parameters match existing values for the screening reference name, the range of values for the point code parameter cannot include any values for that parameter that are currently provisioned for the screening reference name.

For example, screening reference name scr1 contains these entries:

SR    NI       NC       NCM       SSN      SCMGFID  NSFI    NSR/ACT
SCR1  240      001      010       012      ------   STOP    ------
SCR1  241      010      020       001      002      AFTPC   SCR1

Another entry for screening reference scr1 with the ni value of 240 and the nc value of 001 cannot be specified if the range of values for the ncm parameter includes the value 010.

The ANSI point code parameter values can be specified as a single value, a range of values, or with an asterisk (*). The asterisk specifies all possible values for the ni, nc, and ncm parameters. Table 4-2 shows the valid combinations of these parameter values.

Table 4-2 Valid Value Combinations for ANSI Point Code Parameters

NI	NC	NCM
Single Value	Single Value	Single Value
Single Value	Single Value	Range of Values
Single Value	Single Value	Asterisk
Single Value	Range of Values	Asterisk
Single Value	Asterisk	Asterisk
Range of Values	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

A range of values can also be specified for an ITU-I or 24-bit ITU-N point code parameter using a combination of asterisks (*) and single values for the point code parameters. Table 4-3 shows the valid combinations of the ITU-I parameter values. Table 4-4 shows the valid combinations of the 24-bit ITU-N parameter values.

Table 4-3 Valid Value Combinations for ITU-I Point Code Parameters

ZONE	AREA	ID
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

Table 4-4 Valid Value Combinations for 24-Bit ITU-N Point Code Parameters

MSA	SSA	SP
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
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 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 CDPA screens in the database using the rtrv-scr-cdpa command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CDPA
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-cdpa 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-cdpa command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-cdpa command with the screening reference name. For example, enter the rtrv-scr-cdpa: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 CDPA
SR    NI       NC      NCM       SSN      SCMGFID  NSFI    NSR/ACT
IEC   240      001     010       012      ------   STOP    ------
SR      ZONE   AREA    ID        SSN      SCMGFID  NSFI    NSR/ACT
IEC     1      134     *         001      002      AFTPC   IEC
```
If a gateway screening stop action set is to be assigned to the allowed CDPA 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 AFTPC, 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-aftpc command to verify that the screen that will be specified by the NSFI/NSR parameter combination in step 7 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 Affected Point Code Screen
- Changing an Allowed Affected Point Code Screen.
Note:
If the point code being added in this procedure is not anITU-I or 14-bitITU-N spare point code, skip step 6 and to step 7.

Note:
If the point code being added in this procedure is anITU-I or 14-bitITU-N spare point code and the screening reference containsITU-I or 14-bitITU-N spare point codes, skip step 6 and go to step 7.
Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number.
Enter this command.

rtrv-ctrl-feat:partnum=893013601

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

Feature Name              Partnum   Status Quantity
Spare Point Code Support  893013601 on     ----

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 ITU National and International Spare Point Code Support feature is enabled, go to step 7.

If the ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support Feature” procedure in Database Administration - SS7 User's Guide to enable the ITU National and International Spare Point Code Support feature as required. After the feature has been enabled, go to step 7.

Add a new allowed CDPA screen to the database using the ent-scr-cdpa command.

If a gateway screening stop action is to be assigned to the allowed CDPA screen being added to the database, enter the ent-scr-cdpa 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:

TheEAGLE does not support redirectingMSUs for theDTA feature or intercepting ISUPIAM messages for theCalling Name Conversion Facility feature from the allowedCDPA screen. Gateway screening stop action sets containing either theRDCT (redirect) orCNCF (calling name conversion facility) stop actions should not be assigned to the allowedCDPA screen. If a gateway screening stop action set containing theRDCT orCNCF stop actions is specified with theent-scr-cdpa command, unsolicited information message (UIM) 1125 is generated when the attempt is made to redirectMSUs from the allowedCDPA screen. Unsolicited information message (UIM) 1215 is generated whenISUP IAMMSUs are intercepted from the allowedCDPA screen. For more information onUIMs 1125 and 1215, go to theUnsolicited Alarm and Information Messages Reference.

The following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, sp, ssn, and scmgfid parameters:

ni – 0 - 255 or an asterisk (*)
nc – 0 - 255 or an asterisk (*)
ncm – 0 - 255 or an asterisk (*)
zone – 0 - 7 or an asterisk (*)
area – 0 - 255 or an asterisk (*)
id – 0 - 7 or an asterisk (*)
npc – 1 - 16383 or an asterisk (*)
msa – 0 - 255 or an asterisk (*)
ssa – 0 - 255 or an asterisk (*)
sp – 0 - 255 or an asterisk (*)
ssn – 0 - 255 or an asterisk (*)
scmgfid – 1 - 255 or an asterisk (*)

Note:

Thescmgfid,ssn,nsfi, andnsr parameters can be specified only as shown inTable 4-5.

Table 4-5 CDPA Parameter Combinations

SSN	SCMGFID	NSFI	NSR
1	1 - 255, *	AFTPC	Must be specified
0, 2-255, *	Cannot be specified	STOP	Cannot be specified

A range of values can be specified for the ni, nc, and ncm parameters. See the “Specifying a Range of Values” section for more information on how the asterisk and a range of values are used for the ni, nc, and ncm parameters.

To add a spare point code to the allowed CDPA screen, the pcst=s parameter must be specified. To add a non-spare point code to the allowed CDPA screen, the pcst parameter does not have to be specified. If the pcst parameter is specified for a screen containing an ITU-I or 14-bit ITU-N non-spare point code, the value must be none.

For this example, enter these commands.

ent-scr-cdpa:sr=gw15:zone=5:area=117:id=2:ssn=254:nsfi=stop

A message similar to the following should appear.

rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
ENT-SCR-CDPA: SCREEN SET AFFECTED - GW15  1% FULL
ENT-SCR-CDPA: MASP A - COMPLTD

ent-scr-cdpa:sr=gw17:ni=003:nc=003:ncm=003:ssn=001:scmgfid=050 :nsfi=aftpc:nsr=gw20

A message similar to the following should appear.

rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-CDPA: SCREEN SET AFFECTED - GW17  1% FULL
ENT-SCR-CDPA: MASP A - COMPLTD

ent-scr-cdpa:sr=gw18:ni=006:nc=006:ncm=006:ssn=253:nsfi=stop

A message similar to the following should appear.

rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-CDPA: SCREEN SET AFFECTED - GW18  1% FULL
ENT-SCR-CDPA: MASP A - COMPLTD

ent-scr-cdpa:sr=ls03:ni=007:nc=007:ncm=007:ssn=001:scmgfid=100 :nsfi=aftpc:nsr=ls04

A message similar to the following should appear.

rlghncxa03w 06-10-25 15:31:30 GMT  EAGLE5 36.0.0
ENT-SCR-CDPA: SCREEN SET AFFECTED - LS03  1% FULL
ENT-SCR-CDPA: MASP A - COMPLTD

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

For this example, enter these commands.

rtrv-scr-cdpa:sr=gw15

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:32:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CDPA
SR      ZONE   AREA    ID        SSN      SCMGFID  NSFI    NSR/ACT
GW15    5      117     2         254      ------   STOP    ------

rtrv-scr-cdpa:sr=gw17

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:33:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CDPA
SR    NI       NC      NCM       SSN      SCMGFID  NSFI    NSR/ACT
GW17  003      003     003       001      050      AFTPC   GW20

rtrv-scr-cdpa:sr=gw18

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:34:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CDPA
SR    NI       NC      NCM       SSN      SCMGFID  NSFI    NSR/ACT
GW18  006      006     006       253      ------  STOP    ------

rtrv-scr-cdpa:sr=ls03

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:35:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CDPA
SR    NI       NC      NCM       SSN      SCMGFID  NSFI    NSR/ACT
LS03  007      007     007       001      100      AFTPC   ------

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 4-3 Adding an Allowed Called Party Address Screen

Sheet 1 of 4

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4