1. Database Administration - GWS User's Guide
  2. Blocked Originating Point Code (BLKOPC) Screen Configuration
  3. Changing a Blocked OPC Screen

Changing a Blocked OPC Screen

This procedure is used to change the attributes of a blocked originating point code (OPC) screen in the database using the chg-scr-blkopc command. The parameters used by the chg-scr-blkopc 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 002-002-002 for the blocked OPC screen gws7 to 230-230-230.

Note:

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

If the current ni, nc, and ncm are equal to the character “c”, only the next screening function identifier and next screening reference can be changed. The next screening function identifier cannot be equal to fail. If the next screening function identifier is not equal to stop, the next screening reference must be specified. Otherwise, only the point code can be changed.

The blocked OPC screen can reference one of the following screens.

  • Allowed SIO
  • Allowed DPC
  • Blocked DPC
  • Allowed CGPA

Verifying the Gateway Screening Configuration

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

  • rtrv-scr-sio:all=yes
  • rtrv-scr-dpc:all=yes
  • rtrv-scr-blkdpc:all=yes
  • rtrv-scr-cgpa: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.

For the first entry for a specific screening reference, the value for the point code must be c, and the NSFI must be either stop, sio, dpc, blkdpc, or cgpa. If the NSFI is stop, the screening of the message will stop at the specified blocked OPC screen. If the NSFI is either sio, dpc, blkdpc, or cgpa, then any message containing a point code that is not listed in the blocked OPC screen with a NSFI equal to fail, will continue to be screened with either the allowed SIO, allowed DPC, blocked DPC, or the allowed CGPA screen.

All subsequent entries for that screening reference must contain a numeric point code value, the NSFI must be equal to fail, and the nsr parameter cannot be specified. Any message that contains an OPC in the blocked OPC screen with the NSFI equal to fail will be rejected from the network and the screening process is stopped.

The pcst or npcst parameters, specifying whether or not the ITU-I or 14-bit ITU-N point code is a spare point code, cannot be used with the zone=c or npc=c parameters.

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      FAIL    ------
SCR1  241      010      020      FAIL    ------

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

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

Table 11-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 11-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
  1. Display the blocked OPC screens in the database using the rtrv-scr-blkopc command.

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = BLOCKED OPC
SR    REF  RULES
GWS7  YES     2
IEC   YES     6
ISP1  YES     2
WRD2  YES     2
WRD3  NO      4
WRD4  YES    10

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

    rtrv-scr-blkopc:sr=gws7

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED OPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS7  002      002      002      FAIL    ------
GWS7  C        C        C        DPC     GWS9

    If a gateway screening stop action set is to be assigned to the blocked OPC 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 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 FAIL, 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 the blocked OPC screen using the chg-scr-blkopc command.

    If a gateway screening stop action is to be assigned to the blocked OPC screen being changed, enter the chg-scr-blkopc 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, and sp parameters must be entered exactly as shown in the rtrv-scr-blkopc 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, c, or an asterisk (*)
    • nnc – 0 - 255, c, or an asterisk (*)
    • nncm – 0 - 255, c, or an asterisk (*)
    • nzone – 0 - 7, c, or an asterisk (*)
    • narea – 0 - 255, c, or an asterisk (*)
    • nid – 0 - 7, c, or an asterisk (*)
    • nnpc – 1 - 16383, c, or an asterisk (*)
    • nmsa – 0 - 255, c, or an asterisk (*)
    • nssa – 0 - 255, c, or an asterisk (*)
    • nsp – 0 - 255, c, 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-blkopc 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-blkopc 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-blkopc 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-blkopc 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.

    The pcst or npcst parameters cannot be used with the zone=c or npc=c parameters.

    For this example, enter this command.

    chg-scr-blkopc:sr=gws7:ni=002:nc=002:ncm=002:nni=230:nnc=230 :nncm=230

    The following messages appear. 

    rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
CHG-SCR-BLKOPC: SCREEN SET AFFECTED - GWS7  1% FULL
CHG-SCR-BLKOPC: MASP A - COMPLTD

    Note:

    Verify the changes using thertrv-scr-blkopc command with the screening reference name used in step 5. For this example, enter this command.

    rtrv-scr-blkopc:sr=gws7

    The following is an example of the possible output. 

    rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED OPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS7  230      230      230      FAIL    ------
GWS7  C        C        C        DPC     GWS9
  6. 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 11-11 Change a Blocked OPC Screen - Sheet 1 of 5



Figure 11-12 Change a Blocked OPC Screen - Sheet 2 of 5



Figure 11-13 Change a Blocked OPC Screen - Sheet 3 of 5



Figure 11-14 Change a Blocked OPC Screen - Sheet 4 of 5



Figure 11-15 Change a Blocked OPC Screen - Sheet 5 of 5