Go to primary content
Oracle® Communications EAGLE Database Administration - GWS User's Guide
Release 46.6
E93314 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Adding a Blocked OPC Screen

This procedure is used to add a blocked originating point code (OPC) screen to the database using the ent-scr-blkopc command. The parameters used by the ent-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 examples in this procedure are used to add the blocked OPC screen data shown in Table 11-1 and based on the example configurations shown in Figure 2-3, Figure 2-4, and Figure 2-7.

Table 11-1 Example Gateway Screening Blocked OPC Configuration Table

Screening Reference ZONE AREA ID NSFI NSR
gws5 C C C sio iec
gws5 4 250 3 fail ----
 
Screening Reference NI NC NCM NSFI NSR
fld3 C C C sio fld4
fld3 020 020 020 fail ----
gws3 C C C dpc gws9
gws3 001 002 002 fail ----
isp1 C C C sio isp1
isp1 025 025 025 fail ----

Note:

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

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 the following procedures to add the desired screen to the database or change an existing screen in 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 parameter, 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-2 shows the valid combinations of these parameter values.

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

Table 11-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 11-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
  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 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.

  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 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
    
  3. Display all 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
    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-blkopc 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-blkopc command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-blkopc command with the screening reference name. For example, enter the rtrv-scr-blkopc: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 = BLOCKED OPC
    SR    NI       NC       NCM      NSFI    NSR/ACT
    IEC   240      001      010      FAIL    ------
    IEC   241      010      *        FAIL    ------
    
    SR      ZONE   AREA     ID       NSFI    NSR/ACT
    IEC     1      003      4        FAIL    ------
    IEC     1      003      5        FAIL    ------
    
    SR    NI       NC       NCM      NSFI    NSR/ACT
    IEC   C        C        C        STOP    CR
    SR      NPC                      NSFI    NSR
    IEC     00235                    FAIL    ------
    
    SR    NI       NC       NCM      NSFI    NSR/ACT
    WRD2  243      015      001      STOP    ------
    WRD2  243      105      002      FAIL    ------
    WRD2  C        C        C        STOP    ------
    

    If a gateway screening stop action set is to be assigned to the blocked OPC 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:28:30 GMT EAGLE5 36.0.0
    ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
    ID   NAME   1    2    3    4    5    6    7    8    9    10
    --   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
    1    copy   copy      
    2    rdct   rdct      
    3    cr     copy rdct 
    4    cncf   cncf      
    5    cpcncf copy cncf 
    6    cncfrd cncf rdct 
    7    cpcfrd copy cncf rdct
    
    GWS action set table is (7 of 16) 44% full
    

    If the required gateway screening stop action set is not in the database, perform the Configuring Gateway Screening Stop Action Sets procedure to configure the required gateway screening stop action set.

    Note:

    If theNSFI of the screen being added in this procedure isSTOP orFAIL, 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.

  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.

    Note:

    If the point code being added in this procedure is not anITU-I or 14-bitITU-Nspare point code, skip this step and to step 7.

    Note:

    If the point code being added in this procedure is anITU-I or 14-bitITU-Nspare point code and the screening reference containsITU-I or 14-bitITU-N spare point codes, skip this step and go to step 7.

    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 blocked OPC screen to the database using the ent-scr-blkopc command.

    If a gateway screening stop action is to be assigned to the blocked OPC screen being changed, enter the ent-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 4. The following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, and sp parameters:

    • ni – 0 - 255, c, or an asterisk (*)
    • nc – 0 - 255, c, or an asterisk (*)
    • ncm – 0 - 255, c, or an asterisk (*)
    • zone – 0 - 7, c, or an asterisk (*)
    • area – 0 - 255, c, or an asterisk (*)
    • id – 0 - 7, c, or an asterisk (*)
    • npc – 1 - 16383, c, or an asterisk (*)
    • msa – 0 - 255, c, or an asterisk (*)
    • ssa – 0 - 255, c, or an asterisk (*)
    • sp – 0 - 255, c, 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 blocked OPC screen, the pcst=s parameter must be specified. To add a non-spare point code to the blocked OPC 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. The pcst parameter cannot be used with the zone=c or npc=c parameters.

    For this example, enter these commands.

    ent-scr-blkopc:sr=gws5:zone=c:area=c:id=c:nsfi=sio:nsr=iec

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=gws5:zone=4:area=250:id=3:nsfi=fail

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=gws3:ni=c:nc=c:ncm=c:nsfi=dpc:nsr=gws9

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=gws3:ni=001:nc=002:ncm=002:nsfi=fail

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=fld3:ni=c:nc=c:ncm=c:nsfi=sio:nsr=fld4

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=fld3:ni=020:nc=020:ncm=020:nsfi=fail

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=isp1:ni=c:nc=c:ncm=c:nsfi=sio:nsr=isp1

    A message similar to the following should appear.

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

    ent-scr-blkopc:sr=isp1:ni=025:nc=025:ncm=025:nsfi=fail

    A message similar to the following should appear.

    rlghncxa03w 06-10-25 15:34:30 GMT  EAGLE5 36.0.0
    ENT-SCR-BLKOPC: SCREEN SET AFFECTED - ISP1  1% FULL
    ENT-SCR-BLKOPC: MASP A - COMPLTD
    
  8. Verify the changes using the rtrv-scr-blkopc command with the screening reference name used in step 7. For this example, enter these commands.

    rtrv-scr-blkopc:sr=gws5

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:35:30 GMT  EAGLE5 36.0.0
    SCREEN = BLOCKED OPC
    SR      ZONE   AREA     ID       NSFI    NSR/ACT
    GWS5    4      250      3        FAIL    ------
    GWS5    C      C        C        SIO     IEC
    

    rtrv-scr-blkopc:sr=gws3

    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
    GWS3  002      002      002      FAIL    ------
    GWS3  C        C        C        DPC     GWS9
    

    rtrv-scr-blkopc:sr=fld3

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:36:30 GMT  EAGLE5 36.0.0
    SCREEN = BLOCKED OPC
    SR    NI       NC       NCM      NSFI    NSR/ACT
    FLD3  020      020      020      FAIL    ------
    FLD3  C        C        C        DPC     FLD4
    

    rtrv-scr-blkopc:sr=isp1

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:36:30 GMT  EAGLE5 36.0.0
    SCREEN = BLOCKED OPC
    SR    NI       NC       NCM      NSFI    NSR/ACT
    ISP1  025      025      025      FAIL    ------
    ISP1  C        C        C        SIO     ISP1
    
  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 11-3 Adding a Blocked OPC Screen



Sheet 1 of 5



Sheet 2 of 5



Sheet 3 of 5



Sheet 4 of 5



Sheet 5 of 5