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

Changing an Allowed OPC Screen

This procedure is used to change the attributes of an allowed originating point code (OPC) screen in the database using the chg-scr-opc command. The parameters used by the chg-scr-opc 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 for the allowed OPC screen wrd2 to 230-230-230, the NSFI to blkopc, and the NSR to wrd6.

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

  • Blocked OPC
  • 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-blkopc:all=yes
  • 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 or change an existing screen in the database.

Specifying a Range of Values

A range of values can be specified for the point code parameters ni, nc, or ncm.

If a range of values is specified for any of these parameters, and the value of the other parameters match existing values for the screening reference name, the range of values for the point code parameter cannot include any values for that parameter that are currently provisioned for the screening reference name.

For example, screening reference name scr1 contains these entries:

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

Another entry for screening reference scr1 with the ni value of 240 and the nc value of 001 cannot be specified if the range of values for the ncm parameter includes the value 010.

The ANSI point code parameter values can be specified as a single value, a range of values, or with an asterisk (*). The asterisk specifies all possible values for the ni, nc, and ncm parameters. Table 12-5 shows the valid combinations of these parameter values.

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

Table 12-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 12-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 allowed OPC screens in the database using the rtrv-scr-opc command.

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
    SCREEN = ALLOWED DPC
    SR    REF  RULES
    GWS4  YES     1
    IEC   YES     6
    ISP1  YES     1
    TUP1  YES     1
    WRD2  YES     1
    WRD4  YES     9
    

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

    rtrv-scr-opc:sr=wrd2

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
    SCREEN = ALLOWED OPC
    SR    NI       NC       NCM      NSFI    NSR/ACT
    WRD2  243      015      001      STOP    ------
    

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

  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 gateway screening stop action set being assigned to theAllowed OPC screen does not contain the redirect stop action, skip step 3 and go to step 4.
  3. Verify the point codes of adjacent nodes by entering the rtrv-ls command.

    The following is an example of the possible output.

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
                                     L3T SLT              GWS GWS GWS
    LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    e1e2         001-207-000   none  1   1   no  B   6    off off off no    off
    ls1305       000-005-000   none  1   1   no  A   1    off off off no    off
    ls1307       000-007-000   none  1   1   no  A   1    off off off no    off
    e1m1s1       001-001-001   none  1   1   no  A   7    off off off no    off
    e1m1s2       001-001-002   none  1   1   no  A   7    off off off no    off
    
                                     L3T SLT              GWS GWS GWS
    LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    e1e2i        1-207-0       none  1   1   no  B   4    off off off ---   on
    ls1315       0-015-0       none  1   1   no  A   1    off off off ---   off
    ls1317       0-017-0       none  1   1   no  A   1    off off off ---   on
    e1m2s1       1-011-1       none  1   1   no  A   7    off off off ---   off
    e1m2s2       1-011-2       none  1   1   no  A   7    off off off ---   off
    
    Link set table is (10 of 1024) 1% full.
    

    Caution:

    RedirectingSLTA/SLTMmessages preventsSLTA/SLTMmessages from being returned to theEAGLE. The signaling link carrying these messages will fail if these messages are not returned to theEAGLE. To preventSLTA/SLTMmessages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned toAllowed OPC screens containing the adjacent point code of a linkset.

    Note:

    If theNSFI of the screen being changed in this procedure will beSTOP, or if theNSFI of the screen is not being changed, skip step 4 and go to step 5.
  4. Enter the commands in the Verifying the Gateway Screening Configuration section to verify that the screen that will be specified by the NSFI/NSR parameter combination in step 6 is in the database.

    If the desired screen is not in the database, perform one of the procedures shown in the Gateway Screening Configuration Procedures section to add the desired screen to the database or change an existing screen in the database.

    Note:

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

  6. Change the attributes for the allowed OPC using the chg-scr-opc command.

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

    RedirectingSLTA/SLTMmessages preventsSLTA/SLTMmessages from being returned to theEAGLE. The signaling link carrying these messages will fail if these messages are not returned to theEAGLE. To preventSLTA/SLTMmessages from being redirected, gateway screening stop action sets containing the redirect stop action should not be assigned toAllowed OPC screens containing the adjacent point code of a linkset, shown in step 3.

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

    The following list contains the values for the nni, nnc, nncm, nzone, narea, nid, and nnpc parameters:

    • nni – 0 - 255 or an asterisk (*)
    • nnc – 0 - 255 or an asterisk (*)
    • nncm – 0 - 255 or an asterisk (*)
    • nzone – 0 - 7 or an asterisk (*)
    • narea – 0 - 255 or an asterisk (*)
    • nid – 0 - 7 or an asterisk (*)
    • nnpc – 1 - 16383 or an asterisk (*)
    • nmsa – 0 - 255 or an asterisk (*)
    • nssa – 0 - 255 or an asterisk (*)
    • nsp – 0 - 255 or an asterisk (*)

    A range of values can be specified for the nni, nnc, and nncm parameters. See the “Specifying a Range of Values” section for more information on how the asterisk and a range of values are used for the nni, nnc, and nncm parameters.

    To change an ITU-I or 14-bit ITU-N spare point code to a non-spare point code, both the pcst=s and npcst=none parameters must be specified with the chg-scr-opc 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-opc 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-opc 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-opc 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-opc:sr=wrd2:ni=243:nc=015:ncm=001:nni=230:nc=230 :ncm=230:nsfi=blkopc:nsr=wrd6

    A message similar to the following should appear.

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

    For this example, enter this command.

    rtrv-scr-opc:sr=wrd2

    The following is an example of the possible output.

    rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
    SCREEN = ALLOWED OPC
    SR    NI       NC       NCM      NSFI    NSR/ACT
    WRD2  230      230      230      BLKOPC  WRD6
    
  8. 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 12-5 Changing an Allowed OPC Screen



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6