Allowed Destination Point Code (DPC) Screen Configuration

9 Allowed Destination Point Code (DPC) Screen Configuration

Chapter 9, Allowed Destination Point Code (DPC) Screen Configuration, contains the procedures necessary to configure allowed destination point code screens.

Introduction

The allowed destination point code (DPC) screen identifies a set of DPC's that are allowed to receive SS7 messages from another network. The gray shaded areas in Figure 9-4 shows the fields of the SS7 message that are checked by the allowed DPC screening function.

Gateway Screening Actions

If a match is not found, the message is discarded.

If a match is found, the nsfi is examined to determine the next step in the screening process. If the nsfi value is any value other than stop, the next screening reference (nsr) is identified and the screening process continues to the next screen identified by the nsfi and nsr parameter values.

If the nsfi is equal to stop, the screening process stops and the message is processed. If a gateway screening stop action set is specified with the screen, shown by the actname parameter value, the message is processed according to the gateway screening stop actions that are assigned to the gateway screening stop action set.

If the rdct (redirect) gateway screening stop action is specified,the message is diverted from the original destination and sent to another destination with the Database Transport Access feature, specified by global title translation, for further processing.
If the cncf gateway screening stop action is specified, the PIP parameter in the incoming ISUP IAM message is converted to the GN parameter. The GN parameter in the incoming ISUP IAM message is converted to the PIP parameter. The message is then sent to the node specified by the DPC in the routing label in the message. For more information on the Calling Name Conversion Facility feature, see Calling Name Conversion Facility (CNCF) Configuration.
If the tlnp gateway screening stop action is specified, ISUP IAMs that pass gateway screening are processed either by the ISUP NP with EPAP feature (if the ISUP NP with EPAP feature is enabled and turned on) or by the Triggerless LNP feature (if the Triggerless LNP feature is turned on). The ISUP NP with EPAP feature is discussed in more detail in G-Port User's Guide. The Triggerless LNP feature is discussed in more detail in ELAP Administration and LNP Feature Activation Guide.
If the tinp gateway screening stop action is specified, ISUP IAMs that pass gateway screening are intercepted by the Triggerless ISUP based Number Portability (TINP) feature and converted to include the routing number (RN) if the call is to a ported number. The TINP feature is discussed in more detail in G-Port User's Guide.
If the tif, tif2, or tif3 gateway screening stop actions are specified, TIF processing is applied to the message.
If the sccp gateway screening stop action is specified, MTP routed SCCP UDT/XUDT are forwarded to the service modules for further processing.

Allowed DPC Screening Actions

Figure 9-1 through Figure 9-3 show the screening actions of the allowed DPC screen.

Figure 9-1 Allowed DPC Screening Actions - Sheet 1 of 3

Figure 9-2 Allowed DPC Screening Actions - Sheet 2 of 3

Figure 9-3 Allowed DPC Screening Actions - Sheet 3 of 3

Figure 9-4 Allowed DPC Screening Functions

Adding an Allowed DPC Screen

This procedure is used to add an allowed destination point code (DPC) screen to the database using the ent-scr-dpc command. The parameters used by the ent-scr-dpc 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 DPC screen data shown in Table 9-1 and based on the example configurations shown in Figure 2-3, Figure 2-5, and Figure 2-9.

Table 9-1 Example Gateway Screening Allowed DPC Configuration Table

Screening Reference	NI	NC	NCM	NSFI	NSR
gws9	003	003	003	blkdpc	gw12
iec	070	070	025&&135	blkdpc	gws9
isp2	073	200	059	isup	isp2
tup1	050	034	049	isup	tup1

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 DPC screen can reference one of the following screens.

Blocked DPC
Allowed Affected Destination Field
Allowed CGPA
Allowed ISUP

Verifying the Gateway Screening Configuration

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

rtrv-scr-blkdpc:all=yes
rtrv-scr-destfld:all=yes
rtrv-scr-cgpa:all=yes
rtrv-scr-isup: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 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      NSFI    NSR/ACT
SCR1  240      001      010      CGPA    ------
SCR1  241      010      020      STOP    ------

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 9-2 shows the valid combinations of these parameter values.

Table 9-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 9-3 shows the valid combinations of the ITU-I parameter values. Table 9-4 shows the valid combinations of the 24-bit ITU-N parameter values.

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

Note:
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 DPC screens in the database using the rtrv-scr-dpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    REF  RULES
IEC   YES     6
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-dpc command output, go to step 2. For this example, the screening reference names are not shown. If these screening reference names are shown in the rtrv-scr-dpc command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-dpc command with the screening reference name. For example, enter the rtrv-scr-dpc: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 DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
IEC   240      001      010      STOP    ------
IEC   241      010      *        CGPA    cg04
SR      NPC                      NSFI    NSR/ACT
IEC     00235                    CGPA    cg04
IEC     00240                    CGPA    cg01
SR      ZONE   AREA     ID       NSFI    NSR/ACT
IEC     1      003      4        BLKDPC  blk1
IEC     1      003      5        STOP    ------
```
If a gateway screening stop action set is to be assigned to the allowed DPC 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, 5, and 6 and go to step 7. If the NSFI of the new screen is not STOP, skip step 4 and 5, and go to step 6.
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 the gateway screening stop action set being assigned to theAllowed DPC screen does not contain the redirect stop action, skip step 5 and go to step 6.

Verify the EAGLE’s point code by entering the rtrv-sid command.

The following is an example of the possible output.

rlghncxa03w 06-10-10 11:43:04 GMT  EAGLE5 36.0.0
PCA              PCI             PCN           CLLI            PCTYPE
100-100-100      3-75-7          7-9-8-1       rlghncxa03w     OTHER

CPCA
002-002-002       002-002-003       002-002-004      002-002-005
002-002-006       002-002-007       002-002-008      002-002-009
004-002-001       004-003-003       050-060-070

CPCA (LNP)
005-005-002       005-005-004       005-005-005      006-006-006

CPCI
1-002-1           1-002-2           1-002-3          1-002-4
2-001-1           7-222-7

CPCN
2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
2-2-3-3           2-2-4-0           10-14-10-1

Caution:

Redirecting SLTA/SLTM messages prevents SLTA/SLTM messages from being returned to the EAGLE. The signaling link carrying these messages will fail if these messages are not returned to the EAGLE. To prevent SLTA/SLTM messages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned to Allowed DPC screens containing the EAGLE’s point code.

Note:

If the NSFI of the screen being added in this procedure is STOP, skip step 6 and go to step 7.

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

Note:
If the point code being added in this procedure is not an ITU-I or 14-bit ITU-N spare point code, continue the procedure with step 8.

Note:
If the point code being added in this procedure is an ITU-I or 14-bit ITU-N spare point code and the screening reference contains ITU-I or 14-bit ITU-N spare point codes, continue the procedure with step 8.
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 8.

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 8.
Add a new allowed DPC screen to the database using the ent-scr-dpc command.

If a gateway screening stop action is to be assigned to the allowed DPC screen being added, enter the ent-scr-dpc 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:
Redirecting SLTA/SLTM messages prevents SLTA/ SLTM messages from being returned to the EAGLE. The signaling link carrying these messages will fail if these messages are not returned to the EAGLE. To prevent SLTA/SLTM messages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned to Allowed DPC screens containing the EAGLE’s point code, shown in step 5.

The following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, and sp 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 (*)
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 DPC screen, the pcst=s parameter must be specified.

To add a non-spare point code to the allowed DPC 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-dpc:sr=gws9:ni=003:nc=003:ncm=003:nsfi=blkdpc:nsr=gw12

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
ENT-SCR-DPC:  SCREEN SET AFFECTED - GWS9  1% FULL
ENT-SCR-DPC:  MASP A - COMPLTD
```
ent-scr-dpc:sr=isp2:ni=073:nc=200:ncm=059:nsfi=isup:nsr=isp2

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-DPC:  SCREEN SET AFFECTED - ISP2  1% FULL
ENT-SCR-DPC:  MASP A - COMPLTD
```
ent-scr-dpc:sr=tup1:ni=050:nc=034:ncm=059:nsfi=isup:nsr=tup1

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-DPC:  SCREEN SET AFFECTED - TUP1  1% FULL
ENT-SCR-DPC:  MASP A - COMPLTD
```
ent-scr-dpc:sr=iec:ni=070:nc=070:ncm=025&&135:nsfi=blkdpc :nsr=gws9

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-DPC:  SCREEN SET AFFECTED - IEC  1% FULL
ENT-SCR-DPC:  MASP A - COMPLTD
```

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

For this example, enter these commands.

rtrv-scr-dpc:sr=gws9

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS9  003      003      003      BLKDPC  GW12

rtrv-scr-dpc:sr=iec

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:31:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
IEC   070      070      025&&135 BLKDPC  GWS9

rtrv-scr-dpc:sr=isp2

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:31:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
ISP2  073      200      059      ISUP    ISP2

rtrv-scr-dpc:sr=tup1

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:31:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
TUP1  050      034      049      ISUP    TUP1

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 9-5 Add an Allowed DPC Screen - Sheet 1 of 5

Figure 9-6 Add an Allowed DPC Screen - Sheet 2 of 5

Figure 9-7 Add an Allowed DPC Screen - Sheet 3 of 5

Figure 9-8 Add an Allowed DPC Screen - Sheet 4 of 5

Figure 9-9 Add an Allowed DPC Screen - Sheet 5 of 5

Removing an Allowed DPC Screen

This procedure is used to remove an allowed destination point code (DPC) screen from the database using the dlt-scr-dpc command. The parameters used by the dlt-scr-dpc 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 removes the allowed DPC screen gws9 from the database.

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 DPC screen can be referenced by one of the following screens.

Screen Set
Allowed OPC
Blocked OPC
Allowed SIO

Verifying the Gateway Screening Configuration

Enter the following commands to verify that none of these screens reference the allowed DPC screen being removed from the database.

rtrv-scrset:nsfi=dpc
rtrv-scr-opc:nsfi=dpc
rtrv-scr-blkopc:nsfi=dpc
rtrv-scr-sio:nsfi=dpc

Gateway Screening Configuration Procedures

To change the NSFI of any of these screens, perform one of these procedures.

Display the allowed DPC screens in the database using the rtrv-scr-dpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED DPC

SR    REF  RULES
GWS9  YES     1
IEC   YES     6
ISP2  YES     1
TUP1  YES     1
WRD2  YES     1
WRD4  YES     9
```
From the rtrv-scr-dpc output, display the allowed DPC screen you wish to remove using the rtrv-scr-dpc command with the screening reference name. For this example, enter this command.

rtrv-scr-dpc:sr=gws9

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS9  003      003      003      BLKDPC  GW12
```
Enter the commands in the Verifying the Gateway Screening Configuration section to verify that the screen being removed is not referenced by other screens in the database.

If the screen being removed is referenced by other screens, perform the procedures shown in the Gateway Screening Configuration Procedures section to change the NSFI of those screens to reference other screens or change the NSFI of these screens to STOP.
Remove the allowed DPC screen from the database using the dlt-scr-dpc command with the screening reference name shown in the rtrv-scr-dpc output in step 1 and with the point code parameter values (ni, nc, ncm, or zone, area, id, or npc, or msa, ssa, sp) of the screen being removed from the database.
The values for these parameters must be entered exactly as shown in the rtrv-scr-dpc output.

To remove an entry containing either an ITU-I or a 14-bit ITU-N spare point code, the pcst=s parameter must be specified with the dlt-scr-dpc command.

To remove an entry containing either an ITU-I or a 14-bit ITU-N non-spare point code, the pcst parameter does not have to be specified with the dlt-scr-dpc command. If the pcst parameter is specified, the value must be none.

For this example, enter this command.

dlt-scr-dpc:sr=gws9:ni=003:nc=003:ncm=003

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:26:30 GMT  EAGLE5 36.0.0
DLT-SCR-DPC:  SCREEN SET AFFECTED - GWS9  0% FULL
DLT-SCR-DPC:  MASP A - COMPLTD
```
Verify the changes using the rtrv-scr-dpc command with the screening reference name used in step 3.
For this example, enter this command.

rtrv-scr-dpc:sr=gws9

The following is an example of the possible output.
```
E2573 Cmd Rej: SR or NSR does not reference an existing SR
```
This message shows that the specified screening reference name is not in the database and the action of the dlt-scr-dpc command in step 3 was successful. If the specified screening reference name contained more than one entry when the dlt-scr-dpc command was executed in step 3, the rtrv-scr-dpc:sr= command output would show the remaining entries in the screening reference instead of error message E2573.

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 9-10 Remove an Allowed DPC Screen

Changing an Allowed DPC Screen

This procedure is used to change the attributes of an allowed destination point code (DPC) screen in the database using the chg-scr-dpc command. The parameters used by the chg-scr-dpc 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 change point code in the allowed DPC screen gws9 to 009-009-009 and change the nsfi to stop.

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 DPC screen can reference one of the following screens.

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

Verifying the Gateway Screening Configuration

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

rtrv-scr-blkdpc:all=yes
rtrv-scr-destfld:all=yes
rtrv-scr-cgpa:all=yes
rtrv-scr-isup: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 point code parameters ni, nc, or ncm.

For example, screening reference name scr1 contains these entries:

SR    NI       NC       NCM      NSFI    NSR/ACT
SCR1  240      001      010      CGPA    ------
SCR1  241      010      020      STOP    ------

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 9-5 shows the valid combinations of these parameter values.

Table 9-5 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 9-6 shows the valid combinations of the ITU-I parameter values. Table 9-7 shows the valid combinations of the 24-bit ITU-N parameter values.

Table 9-6 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 9-7 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

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

rtrv-scr-dpc:sr=gws9

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS9  003      003      003      BLKDPC  GW12
```
If a gateway screening stop action set is to be assigned to the allowed DPC screen being changed in the database, go to step 2.

Step 2 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 changed in this procedure is STOP. If the NSFI of the screen will be changed to STOP, but a gateway screening stop action set name will not be assigned to the screen, skip steps 2, 3, and 4, and go to step 5. If the NSFI of the screen will not be STOP, skip step 2 and 3, and go to step 4.
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.

Note:
If the gateway screening stop action set being assigned to theAllowed DPC screen does not contain the redirect stop action, skip step 3 and go to step 4.
Verify the EAGLE’s point code by entering the rtrv-sid command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-10 11:43:04 GMT  EAGLE5 36.0.0
PCA              PCI             PCN           CLLI            PCTYPE
100-100-100      3-75-7          7-9-8-1       rlghncxa03w     OTHER

CPCA
002-002-002       002-002-003       002-002-004      002-002-005
002-002-006       002-002-007       002-002-008      002-002-009
004-002-001       004-003-003       050-060-070

CPCA (LNP)
005-005-002       005-005-004       005-005-005      006-006-006

CPCI
1-002-1           1-002-2           1-002-3          1-002-4
2-001-1           7-222-7

CPCN
2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
2-2-3-3           2-2-4-0           10-14-10-1
```
Caution:
Redirecting SLTA/SLTM messages prevents SLTA/SLTM messages from being returned to the EAGLE. The signaling link carrying these messages will fail if these messages are not returned to the EAGLE. To prevent SLTA/SLTMmessages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned to Allowed DPC screens containing the EAGLE’s point code.

Note:
If the NSFI of the screen being changed in this procedure will be STOP, or if the NSFI of the screen is not being changed, skip step 4 and go to step 5.
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.
Note:
If any of these conditions apply to this procedure, skip step 5 and go to step 6:
- The point code in the screen is not being changed.
- The screen being changed contains either an ANSI or 24-bit ITU-N point code.
- The ITU-I or 14-bit ITU-N non-spare point code in the screen is not being changed to an ITU-I or 14-bit ITU-N spare point code.
- The point code in the screen is an ITU-I or 14-bit ITU-N spare point code or the screening reference contains other screens with ITU-I or 14-bit ITU-N spare point codes.
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 6.

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 6.
Change the attributes of an allowed DPC screen using the chg-scr-dpc command.
If a gateway screening stop action is to be assigned to the allowed DPC screen being changed, enter the chg-scr-dpc 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.

Caution:
Redirecting SLTA/SLTM messages prevents SLTA/SLTM messages from being returned to the EAGLE. The signaling link carrying these messages will fail if these messages are not returned to the EAGLE. To prevent SLTA/ SLTMmessages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned to Allowed DPC screens containing the EAGLE’s point code, shown in step 3.

The current values for the ni, nc, ncm, zone, area, id, npc, msa, ssa, and sp parameters must be entered exactly as shown in the rtrv-scr-dpc output in step 1.

The following list contains the values for the nni, nnc, nncm, nzone, narea, nid, nnpc, nmsa, nssa, and nsp parameters:
- nni - 0-255 or an asterisk (*)
- nnc - 0-255 or an asterisk (*)
- nncm - 0-255 or an asterisk (*)
- nzone - 0-7 or an asterisk (*)
- narea - 0-255 or an asterisk (*)
- nid - 0-7 or an asterisk (*)
- nnpc - 1 - 16383 or an asterisk (*)
- nmsa - 0-255 or an asterisk (*)
- nssa - 0-255 or an asterisk (*)
- nsp - 0-255 or an asterisk (*)
A range of values can be specified for the nni, nnc, and nncm 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 nni, nnc, and nncm parameters.

To change an ITU-I or 14-bit ITU-N spare point code to a non-spare point code, both the pcst=s and npcst=none parameters must be specified with the chg-scr-dpc command.

To change an ITU-I or 14-bit ITU-N non-spare point code to a spare point code, the npcst=s parameter must be specified with the chg-scr-dpc command. The pcst parameter does not have to be specified.

If the current point code in the screen being changed is either an ITU-I or 14-bit ITU-N spare point code, the pcst=s parameter must be specified with the chg-scr-dpc command.

If the current point code in the screen being changed is either an ITU-I or 14-bit ITU-N non-spare point code, the pcst parameter does not have to be specified with the chg-scr-dpc command. If the pcst parameter is specified for a screen containing either an ITU-I or 14-bit ITU-N non-spare point code, the pcst parameter value must be none.

For this example, enter this command.

chg-scr-dpc:sr=gws9:ni=003:nc=003:ncm=003:nni=009:nnc=009 :nncm=009:nsfi=stop

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

rtrv-scr-dpc:sr=gws9

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS9  009      009      009      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 9-11 Change an Allowed DPC Screen - Sheet 1 of 6

Figure 9-12 Change an Allowed DPC Screen - Sheet 2 of 6

Figure 9-13 Change an Allowed DPC Screen - Sheet 3 of 6

Figure 9-14 Change an Allowed DPC Screen - Sheet 4 of 6

Figure 9-15 Change an Allowed DPC Screen - Sheet 5 of 6

Figure 9-16 Change an Allowed DPC Screen - Sheet 6 of 6