Allowed Affected Point Code (AFTPC) Screen Configuration

3 Allowed Affected Point Code (AFTPC) Screen Configuration

Chapter 3, Allowed Affected Point Code (AFTPC) Screen Configuration, contains the procedures necessary to configure allowed affected point code screens.

Introduction

The allowed affected point code (AFTPC) screen is used to identify affected point codes. Messages containing the allowed affected point code in the AFTPC screen are allowed into the EAGLE for further processing. The gray shaded areas in Figure 3-3 shows the fields of the SS7 message that are checked by the AFTPC screening function. Affected point codes are found in subsystem-prohibited (SSP), subsystem-status-test (SST) and subsystem-allowed (SSA) SCCP management messages. This is the last screen in the gateway screening process.

Gateway Screening Actions

The Gateway Screening process stops with this screen. The nsfi parameter value can only be stop.

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

If a match is found, 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 AFTPC Screening Actions

Figure 3-1 and Figure 3-2 show the screening actions of the allowed AFTPC screen.

Figure 3-1 Allowed AFTPC Screening Actions - Sheet 1 of 2

Figure 3-2 Allowed AFTPC Screening Actions - Sheet 2 of 2

Figure 3-3 Allowed Affected Point Code Screening Function

Adding an Allowed Affected Point Code Screen

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

Table 3-1 Example Gateway Screening Allowed AFTPC Configuration Table

Screening Reference	NI	NC	NCM	SSN	NSFI	ACTNAME
gw20	008	008	008	250	stop	COPY
ls04	010	010	010	015	stop	COPY

Note:

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

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      NSFI    NSR/ACT
SCR1  240      001      010      012      STOP    ------
SCR1  241      010      020      015      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 3-2 shows the valid combinations of these parameter values.

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

Table 3-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 3-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 AFTPC screens in the database using the rtrv-scr-aftpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
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-aftpc 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-aftpc command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-aftpc command with the screening reference name. For example, enter the rtrv-scr-aftpc: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 AFTPC
SR    NI       NC       NCM      SSN      NSFI    NSR/ACT
IEC   010      010      011      012      STOP    ------
IEC   010      010      013      012      STOP    ------
```
If a gateway screening stop action set is to be assigned to the allowed AFTPC 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: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 point code being added in this procedure is not an ITU-I or 14-bit ITU-N spare point code, skip step 5 and to step 6.

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, skip step 5 and go to step 6.
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.
Add the new allowed AFTPC screen to the database using the ent-scr-aftpc command.

Caution:
TheEAGLE does not support redirecting MSUs for the DTA feature or intercepting ISUP IAM messages for the Calling Name Conversion Facility feature from the allowed AFTPC 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 AFTPC screen. If a gateway screening stop action set containing the RDCT or CNCF stop actions is specified with the ent-scr-aftpc command, unsolicited information message (UIM) 1127 is generated when the attempt is made to redirect MSUs from the allowed AFTPC screen. Unsolicited information message (UIM) 1217 is generated when ISUP IAM MSUs are intercepted from the allowed AFTPC screen. For more information on UIMs 1127 and 1217, go to Unsolicited Alarm and Information Messages Reference.

If a gateway screening stop action is to be assigned to the allowed AFTPC screen being changed, enter the ent-scr-aftpc 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 following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, sp, and ssn 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 (*)
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 AFTPC screen, the pcst=s parameter must be specified. To add a non-spare point code to the allowed AFTPC 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-aftpc:sr=gw20:ni=008:nc=008:ncm=008:ssn=250:nsfi=stop :actname=copy

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
ENT-SCR-AFTPC: SCREEN SET AFFECTED - GW20  1% FULL
ENT-SCR-AFTPC: MASP A - COMPLTD
```
ent-scr-aftpc:sr=ls04:ni=010:nc=010:ncm=010:ssn=015:nsfi=stop :actname=copy

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

Verify the changes using the

rtrv-scr-aftpc

command with the screening reference name used in step 6.

For this example, enter these commands.

rtrv-scr-aftpc:sr=gw20

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    NI       NC       NCM      SSN      NSFI    NSR/ACT
GW20  008      008      008      250      STOP    COPY

rtrv-scr-aftpc:sr=ls04

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    NI       NC       NCM      SSN      NSFI    NSR/ACT
LS04  010      010      010      015      STOP    COPY

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 3-4 Add an Allowed Affected Point Code Screen - Sheet 1 of 3

Figure 3-5 Add an Allowed Affected Point Code Screen - Sheet 2 of 3

Figure 3-6 Add an Allowed Affected Point Code Screen - Sheet 3 of 3

Removing an Allowed Affected Point Code Screen

This procedure is used to remove an allowed affected point code (AFTPC) screen from the database using the dlt-scr-aftpc command. The parameters used by the dlt-scr-aftpc 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 AFTPC screen wrd0 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.

Display the allowed AFTPC screens in the database using the rtrv-scr-aftpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    REF  RULES
GW20  YES     1
IEC   YES     2
LS04  YES     1
WRD0  YES     1
WRD2  YES     1
WRD4  YES     9
```
From the rtrv-scr-aftpc output, display the allowed AFTPC screen you wish to remove using the rtrv-scr-aftpc command with the screening reference name. For this example, enter the rtrv-scr-aftpc:sr=wrd0 command. The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR      ZONE   AREA     ID       SSN      NSFI    NSR/ACT
WRD0    1      004      6        023      STOP    ------
```
An allowed AFTPC screen can only be referenced by an allowed CDPA screen.
Verify any references to the allowed AFTPC screen being removed from the database using the rtrv-scr-cdpa:nsfi=aftpc 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      ZONE   AREA    ID        SSN      SCMGFID  NSFI    NSR/ACT
IEC     1      134     *         001      002      AFTPC   IEC

SR      ZONE   AREA    ID        SSN      SCMGFID  NSFI    NSR/ACT
WRD1    1      004     6         001      005      AFTPC   WRD0

SR      NPC                      SSN      SCMGFID  NSFI    NSR/ACT
WRD4    12345                    001      100      AFTPC   IEC
```
If the screen being removed is referenced by any CDPA screens, perform the Changing an Allowed Called Party Address Screen procedure to change the NSFI of those CDPA screens to reference other AFTPC screens or change the NSFI of these screens to STOP.
Remove the allowed AFTPC screen from the database using the dlt-scr-aftpc command with the screening reference name shown in the rtrv-scr-aftpc output in step 1 and with the point code parameter values (ni, nc, ncm, or zone, area, id, or npc, or msa, ssa, sp) and the ssn parameter value of the screen being removed from the database.
The values for these parameters must be entered exactly as shown in the rtrv-scr-aftpc 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-aftpc 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-aftpc command. If the pcst parameter is specified, the value must be none.

For this example, enter this command.

dlt-scr-aftpc:sr=wrd0:zone=1:area=004:id=6:ssn=023

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

rtrv-scr-aftpc:sr=wrd0

The following message should appear.
```
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-aftpc command in step 5 was successful. If the specified screening reference name contained more than one entry when the dlt-scr-aftpc command was executed in step 4, the rtrv-scr-aftpc: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 3-7 Remove an Allowed Affected Point Code Screen

Changing an Allowed Affected Point Code Screen

This procedure is used to change the attributes of an allowed affected point code (AFTPC) screen in the database using the chg-scr-aftpc command. The parameters used by the chg-scr-aftpc 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 is used to change the point code 009-009-009 for the allowed AFTPC screen gw21 to 100-100-100, and the subsystem number from 253 to 150.

Note:

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

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      SSN      NSFI    NSR/ACT
SCR1  240      001      010      012      STOP    ------
SCR1  241      010      020      015      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 3-5 shows the valid combinations of these parameter values.

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

Table 3-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 3-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 AFTPC screens in the database using the rtrv-scr-aftpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    REF  RULES
GW20  YES     1
GW21  YES     1
IEC   YES     2
LS04  YES     1
WRD0  YES     1
WRD2  YES     1
WRD4  YES     9
```
From the rtrv-scr-aftpc output, display the allowed AFTPC screen you wish to change using the rtrv-scr-aftpc command with the screening reference name. For this example, enter this command.

rtrv-scr-aftpc:sr=gw21

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    NI       NC       NCM      SSN      NSFI    NSR/ACT
GW21  009      009      009      253      STOP    ------
```
If a gateway screening stop action set is to be assigned to the allowed AFTPC screen being changed in this procedure, go to step 2. Otherwise, skip step 2 and go to step 3.

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.

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.
Note:
If any of these conditions apply to this procedure, skip this step and go to step 4:
- 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.
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 4.

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

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

The following list contains the values for the nni, nnc, nncm, nzone, narea, nid, nnpc, nmsa, nssa, nsp, and nssn 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 (*)
- nssn – 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-aftpc 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-aftpc 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-aftpc 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-aftpc 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-aftpc:sr=gw21:ni=009:nc=009:ncm=009:ssn=253:nni=100 :nnc=100:nncm=100:nssn=150

Caution:
TheEAGLE does not support redirecting MSUs for theDTA feature or intercepting ISUP IAM messages for the Calling Name Conversion Facility feature from the allowed AFTPC 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 allowedAFTPC screen. If a gateway screening stop action set containing the RDCT or CNCF stop actions is specified with the chg-scr-aftpc command, unsolicited information message (UIM) 1127 is generated when the attempt is made to redirect MSUs from the allowed AFTPC screen. Unsolicited information message (UIM) 1217 is generated when ISUP IAM MSUs are intercepted from the allowed AFTPC screen. For more information on UIMs 1127 and 1217, go toUnsolicited Alarm and Information Messages Reference.

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

rtrv-scr-aftpc:sr=gw21

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED AFTPC
SR    NI       NC       NCM      SSN      NSFI    NSR/ACT
GW21  100      100      100      150      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 3-8 Change an Allowed Affected Point Code Screen - Sheet 1 of 4

Figure 3-9 Change an Allowed Affected Point Code Screen - Sheet 2 of 4

Figure 3-10 Change an Allowed Affected Point Code Screen - Sheet 3 of 4

Figure 3-11 Change an Allowed Affected Point Code Screen - Sheet 4 of 4