1. EAGLE Database Administration - GWS User's Guide
  2. Allowed Calling Party (CGPA) Screen Configuration

6 Allowed Calling Party (CGPA) Screen Configuration

Chapter 6, Allowed Calling Party (CGPA) Screen Configuration, contains the procedures necessary to configure allowed calling party address screens.

Introduction

The allowed calling party address (CGPA) screen is used to screen SCCP messages from another network. The gray shaded areas in Figure 6-4 shows the fields of the SS7 message that are checked by the CGPA screening function. The screening reference contains a list of point codes and subsystem number combinations.

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 CGPA Screening Actions

Any MSU that does not contain a service indicator of 3 in the SIO field and does not contain the SCCP message types 9, 10, 17, or 18 and reaches this screen in the gateway screening process automatically passes gateway screening and is allowed into the EAGLE.

The value of the nsfi parameter is based on the value of the routing indicator (ri) parameter. Table 6-1 through Figure 6-3 show the valid combinations of nsfi values and routing indicator values.

Table 6-1 Valid Parameter Combinations for the Allowed CGPA Screening Function

Routing Indicator (RI) Values Nest Screening Function Identifier (NSFI) Values
GT TT
DPC CDPA
* (asterisk) TT, CDPA

Figure 6-1 shows the screening actions of the allowed CGPA screen.

Figure 6-1 Allowed CGPA Screening Actions - Sheet 1 of 3

img/c_introduction_2_dbags-fig1.jpg

Figure 6-2 Allowed CGPA Screening Actions - Sheet 2 of 3

img/gws_stop_actions_01_140964.jpg

Figure 6-3 Allowed CGPA Screening Actions - Sheet 3 of 3

img/gws_stop_actions_02_140964.jpg

Figure 6-4 Allowed Calling Party Address Screening Function

img/c_introduction_2_dbags-fig3.jpg

Adding an Allowed Calling Party Address Screen

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

Table 6-2 Example Gateway Screening Allowed CGPA Configuration Table

Screening Reference ZONE AREA ID SN RI SCCPMT NSFI NSR
gw11 7 100 4 254 * 010 cdpa gw15
Screening Reference NI NC NCM SSN RI SCCPMT NSFI NSR
gw13 007 007 007 250 gt 017 tt gw16
gw14 006 006 006 253 dpc 009 cdpa gw17

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

  • Allowed TT
  • Allowed CDPA

Verifying the Gateway Screening Configuration

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

  • rtrv-scr-tt:all=yes
  • rtrv-scr-cdpa:all=yes

Gateway Screening Configuration Procedures

If the desired screen is not in the database, perform one of the following 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      SSN      RI   SCCPMT   NSFI    NSR/ACT
SCR1  240      001      010      012      DPC  009      STOP    ------
SCR1  241      010      020      *        GT   017      TT      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 6-3 shows the valid combinations of these parameter values.

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

Table 6-4 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 6-5 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
  1. 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 the rtrv-feat command description in Commands 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.

  2. 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
  3. Display all allowed CGPA screens in the database using the rtrv-scr-cgpa command.

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
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-cgpa 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-cgpa command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-cgpa command with the screening reference name. For example, enter the rtrv-scr-cgpa: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 CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
IEC   240      001      010      012      DPC  009      STOP    ------
IEC   241      010      *        *        GT   017      TT      TT1

    If a gateway screening stop action set is to be assigned to the allowed CGPA 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 not STOP, skip step 4 and go to step 5.

  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: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 is STOP, skip step 5 and go to step 6.
  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 7 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, skip step 6 and to step 7.

    Note:

    If the point code being added in this procedure is a 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 6 and go to step 7.
  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 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.

  7. Add a new allowed CGPA screen to the database using the ent-scr-cgpa command.

    If a gateway screening stop action is to be assigned to the allowed CGPA screen being changed, enter the ent-scr-cgpa 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 the Calling Name Conversion Facility feature from the allowedCGPA 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 CGPA screen. If a gateway screening stop action set containing the RDCT or CNCF stop actions is specified with the ent-scr-cgpa command, unsolicited information message (UIM) 1126 is generated when the attempt is made to redirect MSUs from the allowed CGPA screen. Unsolicited information message (UIM) 1216 is generated whenISUP IAM MSUs are intercepted from the allowed CGPA screen. For more information on UIMs 1126 and 1216, go to Unsolicited Alarm and Information Messages Reference.

    The following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, sp, ssn, ri, and sccpmt 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 (*)
    • ri – gt, dpc or an asterisk (*)
    • sccpmt – 9, 10, 17, 18 or an asterisk (*)

    Note:

    If either theri=gt ornsfi=tt parameter is specified, the other parameter must be specified. If either theri=dpc ornsfi=cdpa parameter is specified, the other parameter must be specified. If theri=* parameter is specified, either thensfi=gt ornsfi=dpc parameters can be specified.

    Note:

    If thesccpmt parameter is not specified, an asterisk will be entered as the value of thesccpmt parameter.

    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 CGPA screen, the pcst=s parameter must be specified. To add a non-spare point code to the allowed CGPA 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-cgpa:sr=gw11:zone=7:area=100:id=4:ssn=254:ri=* :sccpmt=010:nsfi=cdpa:nsr=gw15

    A message similar to the following should appear. 

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

    ent-scr-cgpa:sr=gw13:ni=007:nc=007:ncm=007:ssn=250:ri=gt :sccpmt=017:nsfi=tt:nsr=gw16

    A message similar to the following should appear. 

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

    ent-scr-cgpa:sr=gw14:ni=006:nc=006:ncm=006:ssn=253:ri=dpc :sccpmt=009:nsfi=cdpa:nsr=gw17

    A message similar to the following should appear. 

    rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-CGPA: SCREEN SET AFFECTED - GW14  1% FULL
ENT-SCR-CGPA: MASP A - COMPLTD
  8. Verify the changes using the rtrv-scr-cgpa command with the screening reference name used in step 7.

    For this example, enter these commands.

    rtrv-scr-cgpa:sr=gw11

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:32:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR      ZONE   AREA     ID       SSN      RI   SCCPMT   NSFI    NSR/ACT
GW11    7      100      4        254      *    010      CDPA    GW15

    rtrv-scr-cgpa:sr=gw13

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:33:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
GW13  007      007      007      250      SSN  017      CDPA    GW16

    rtrv-scr-cgpa:sr=gw14

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:34:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
GW14  006      006      006      253      GT   009      TT      GW17
  9. 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 6-5 Add an Allowed Calling Party Address Screen - Sheet 1 of 4



Figure 6-6 Add an Allowed Calling Party Address Screen - Sheet 2 of 4



Figure 6-7 Add an Allowed Calling Party Address Screen - Sheet 3 of 4



Figure 6-8 Add an Allowed Calling Party Address Screen - Sheet 4 of 4



Removing an Allowed Calling Party Address Screen

This procedure is used to remove an allowed calling party address (CGPA) screen from the database using the dlt-scr-cgpa command. The parameters used by the dlt-scr-cgpa 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 CGPA screen gw14 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 CGPA screen can be referenced by one of the following screens.

  • Allowed OPC
  • Blocked OPC
  • Allowed SIO
  • Allowed DPC
  • Blocked DPC

Verifying the Gateway Screening Configuration

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

  • rtrv-scr-opc:nsfi=cgpa
  • rtrv-scr-blkopc:nsfi=cgpa
  • rtrv-scr-sio:nsfi=cgpa
  • rtrv-scr-dpc:nsfi=cgpa
  • rtrv-scr-blkdpc:nsfi=cgpa

Gateway Screening Configuration Procedures

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

  1. Display the allowed CGPA screens in the database using the rtrv-scr-cgpa command.

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    REF  RULES
GW11  YES     1
GW13  YES     1
GW14  YES     1
IEC   YES     2
WRD2  YES     1
WRD4  YES     9

    From the rtrv-scr-cgpa output, display the allowed CGPA screen you wish to remove using the rtrv-scr-cgpa command with the screening reference name. For this example, enter the rtrv-scr-cgpa:sr=gw14 command. The following is an example of the possible output.

    rtrv-scr-cgpa:sr=gw14

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
GW14  003      003      003      253      GT   009      TT      GW17
  2. 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.

  3. Remove the allowed CGPA screen from the database using the dlt-scr-cgpa command.

    The current values for the ni, nc, ncm, zone, area, id, npc, msa, ssa, sp, ri, ssn, or sccpmt parameters must be entered exactly as shown in the rtrv-scr-cgpa 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-cgpa 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-cgpa command. If the pcst parameter is specified, the value must be none.

    For this example, enter this command.

    dlt-scr-cgpa:sr=gw14:ni=003:nc=003:ncm=003:ssn=253:sccpmt=009

    A message similar to the following should appear. 

    rlghncxa03w 06-10-25 15:26:30 GMT  EAGLE5 36.0.0
DLT-SCR-CGPA: SCREEN SET AFFECTED - GW14  0% FULL
DLT-SCR-CGPA: MASP A - COMPLTD
  4. Verify the changes using the rtrv-scr-cgpa command with the screening reference name used in step 3.

    For this example, enter this command.

    rtrv-scr-cgpa:sr=gw14

    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-cgpa command in step 3 was successful. If the specified screening reference name contained more than one entry when the dlt-scr-cgpa command was executed in step 3, the rtrv-scr-cgpa:sr= command output would show the remaining entries in the screening reference instead of error message E2573.

  5. 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 6-9 Remove an Allowed Calling Party Address Screen - Sheet 1 of 2



Figure 6-10 Remove an Allowed Calling Party Address Screen - Sheet 1 of 2



Changing an Allowed Calling Party Address Screen

This procedure is used to change the attributes of an allowed calling party address (CGPA) screen in the database using the chg-scr-cgpa command. The parameters used by the chg-scr-cgpa 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 003-003-003 for the allowed CGPA screen gw14 to 230-230-230 and change 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.

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

  • Allowed TT
  • Allowed CDPA

Verifying the Gateway Screening Configuration

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

  • rtrv-scr-tt: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 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      RI   SCCPMT   NSFI    NSR/ACT
SCR1  240      001      010      012      DPC  009      STOP    ------
SCR1  241      010      020      *        GT   017      TT      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 6-6 shows the valid combinations of these parameter values.

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

Table 6-7 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 6-8 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
  1. Display the allowed CGPA screens in the database using the rtrv-scr-cgpa command.

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    REF  RULES
GW11  YES     1
GW13  YES     1
GW14  YES     1
IEC   YES        2
WRD2  YES     1
WRD4  YES     9

    From the rtrv-scr-cgpa output, display the allowed CGPA screen you wish to change using the rtrv-scr-cgpa command with the screening reference name. For this example, enter this command.

    rtrv-scr-cgpa:sr=gw14

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
GW14  003      003      003      253      GT   009      TT      GW17

    If a gateway screening stop action set is to be assigned to the allowed CGPA screen being added to 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 and 3 and go to step 4. If the NSFI of the screen will not be STOP, skip step 2 and go to step 3.

  2. 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 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 3 and go to step 4.
  3. 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 5 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 this step and go to step 5:
    • 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.
  4. 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 5.

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

  5. Change the attributes of an allowed CGPA screen using the chg-scr-cgpa command.

    If a gateway screening stop action is to be assigned to the allowed CGPA screen being changed, enter the chg-scr-cgpa 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:

    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 CGPA 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 CGPA screen. If a gateway screening stop action set containing the RDCT or CNCF stop actions is specified with the chg-scr-cgpa command, unsolicited information message ( UIM) 1126 is generated when the attempt is made to redirect MSUs from the allowed CGPA screen. Unsolicited information message (UIM) 1216 is generated when ISUP IAM MSUs are intercepted from the allowed CGPA screen. For more information on UIMs 1126 and 1216, go toUnsolicited Alarm and Information Messages Reference.

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

    The following list contains the values for nni, nnc, nncm, nzone, narea, nid, nnpc, nssn, nmsa, nssa, nsp, nri, and nsccpmt 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 (*)
    • nri – gt, dpc or an asterisk (*)
    • nsccpmt – 9, 10, 17, 18 or an asterisk (*)

    Note:

    Thenri,nsfi, andnsr parameters can be specified only as shown inTable 6-9.

    Table 6-9 CGPA Parameter Combinations

    New or Current RI Value NSFI NSR
    GT TT, STOP Must be specified if NSFI=TT
    DPC CDPA, STOP Must be specified if NSFI=CDPA
    * TT, CDPA, STOP Must be specified if NSFI=TT or NSFI=CDPA

    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-cgpa 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-cgpa 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-cgpa 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-cgpa 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-cgpa:sr=gw14:ni=003:nc=003:ncm=003:ssn=253:sccpmt=009 :nni=230:nnc=230:nncm=230:nssn=150

    A message similar to the following should appear. 

    rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
CHG-SCR-CGPA: SCREEN SET AFFECTED - GW14  1% FULL
CHG-SCR-CGPA: MASP A - COMPLTD
  6. Verify the changes using the rtrv-scr-cgpa command with the screening reference name used in step 5.

    For this example, enter this command.

    rtrv-scr-cgpa:sr=gw14

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
SCREEN = ALLOWED CGPA
SR    NI       NC       NCM      SSN      RI   SCCPMT   NSFI    NSR/ACT
GW14  230      230      230      150      GT   009      TT      GW17
  7. 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 6-11 Change an Allowed Calling Party Address Screen - Sheet 1 of 5



Figure 6-12 Change an Allowed Calling Party Address Screen - Sheet 2 of 5



Figure 6-13 Change an Allowed Calling Party Address Screen - Sheet 3 of 5



Figure 6-14 Change an Allowed Calling Party Address Screen - Sheet 4 of 5



Figure 6-15 Change an Allowed Calling Party Address Screen - Sheet 5 of 5