1. EAGLE Database Administration - Features User's Guide
  2. GSM MAP Screening Configuration

5 GSM MAP Screening Configuration

Chapter 6, GSM MAP Screening Configuration, describes the GSM MAP Screening feature and the procedures necessary to configure the EAGLE to support this feature.

Introduction

Traditionally, STP message screening has been limited to the MTP and SCCP levels; this has been sufficient to meet operators' needs. However, GSM mobile operators have an increasing need for screening at the Mobile Application Part (MAP) level. This need is driven by advanced network capabilities and proliferating roaming agreements.

New features that require this enhanced screening capability are Inter-operator Short Message Service (SMS) and Any Time Interrogation (ATI). The GSM MAP Screening feature focuses on solving the screening needs associated with ATI, which is defined in MAP version 3. An ATI message allows an external server to interrogate an HLR and obtain information about the location and/or state of a GSM subscriber. It may be desirable to control which external entities can request this information, and what information they can request before allowing the message to pass through to the HLR.

This feature allow the user to provision which MAP SSNs are affected, which MAP operations codes to screen, which origination points are allowed, and which error messages to use.

Note:

GSM MAP Screening can be used with linksets containing ITU international or ITU national adjacent point codes whether or not the Enhanced GSM MAP Screening feature is enabled and on. GSM MAP Screening can be used with linksets containing ANSI adjacent point codes only if the Enhanced GSM MAP screening feature is enabled and on.

GSM MAP Screening Overview

An SCCP MSU arrives at the EAGLE on a linkset with the gsmscrn parameter value set to on. If the DPC of the MSU is the EAGLE’s point code, the MSU is processed by Global Title Translation and Gateway Screening on the called party address (CDPA). Any applicable SCCP/MTP conversions are also performed on the MSU. The MSU is passed on to GSM MAP Screening. GSM MAP screening is then performed on the MSU before forwarding it to the destination. If the gsmscrn parameter of the linkset is set to off, GSM MAP Screening is not performed on the MSU.

If the DPC of the MSU is not the EAGLE’s point code, the message is routed to its destination using MTP routing. GSM MAP Screening is not performed on the MSU.

If the MTP MAP Screening feature is enabled and turned on, and the DPC of the MSU is not the EAGLE’s point code, the MSU (SCCP message types 9 - UDT, or 10 - UDTS only) is sent to GSM MAP Screening without being processed by Global Title Translation and Gateway Screening on the called party address. GSM MAP screening is then performed on the MSU before forwarding the MSU to its destination.

When GSM MAP Screening on the message has completed, the EAGLE performs one of the following actions:

  • Route the message to destination

  • Discard the message

  • Forward the message to a new destination

  • Duplicate the message. Send the original message to the original destination, and send the duplicate message to a new destination.

  • Duplicate the message and send the duplicate message to a new destination. Discard the original message.

  • Return an error message to the originator.

GSM MAP screening first checks to see whether the calling party SSN and called party SSN are present and targeted to be screened or not.

If both SSNs are targeted, it then checks for the MAP operations code of the message to know whether it is targeted to be screened or not. If the MAP operations code is not targeted to be screened, then the EAGLE either discards or routes the message, defined by the GSMDFLT parameter of the chg-stpopts command. If the MAP operations code is targeted to be screened, GSM MAP screening checks the calling party address of the message to know whether it is targeted for screening or not.

If the CGPA (calling party address) of the message is not targeted for GSM MAP Screening, then the screening action defined in the MAP operations code table by the dfltact parameter of the ent-gsms-opcode command is performed on the message.

If the CGPA of the message is targeted for screening and the Enhanced GSM MAP Screening feature is enabled and on, GSM MAP Screening checks the CDPA (called party address) of the message to know whether or not it is targeted for screening. If the CDPA of the message is targeted for screening, GSM MAP screening checks to see if the ATI request contains the forbidden parameter value provisioned for the CDPA. If there is no forbidden parameter in the ATI request, the message is not an ATI request, or the provisioned forbidden parameter value for the CDPA is none, the message is routed to the destination. If the message is an ATI request and contains the forbidden parameter value provisioned for the CDPA, or the provisioned forbidden parameter value is all, GSM MAP screening performs the screening action defined in the CDPA screening table by the action parameter of the ent-gsmmap-scrn command.

If the CDPA of the message is not targeted for screening, GSM MAP screening checks to see if the ATI request contains the forbidden parameter value provisioned for the CGPA. If there is no forbidden parameter in the ATI request, the message is not an ATI request, or the provisioned forbidden parameter value for the CGPA is none, the message is routed to the destination. If the message is an ATI request and contains the forbidden parameter value provisioned for the CGPA, or the provisioned forbidden parameter value is all, GSM MAP screening performs the screening action defined in the CGPA screening table by the action parameter of the ent-gsmmap-scrn command.

If the CGPA of the message is targeted for screening and the Enhanced GSM MAP Screening feature is not enabled and off, GSM MAP Screening checks the CGPA (calling party address) of the message to know whether or not it is targeted for screening. If the CGPA of the message is targeted for screening, GSM MAP screening checks to see if the ATI request contains the forbidden parameter value provisioned for the CGPA. If there is no forbidden parameter in the ATI request, the message is not an ATI request, or the provisioned forbidden parameter value for the CGPA is none, the message is routed to the destination. If the message is an ATI request and contains the forbidden parameter value provisioned for the CGPA, or the provisioned forbidden parameter value is all, GSM MAP screening performs the screening action defined in the CGPA screening table by the action parameter of the ent-gsmmap-scrn command.

Figure 5-1 shows overview of GSM MAP screening functionality.

Figure 5-1 GSM MAP Screening Overview


img/gsm-map-screening.jpg

Sheet 1 of 2



Sheet 2 of 2

GSM MAP Screening Details

GSM MAP screening verifies the MAP message format and performs screening before the message is routed to the destination. The following database tables are used in performing GSM MAP screening:

  • SSN table
  • MAP operations code table
  • STP option table
  • MAP screening table

GSM MAP Screening is performed in the following stages.

  1. The following fields from SCCP message are decoded:
    • The SSN from the calling party address
    • The SSN from the called party address
    • The global title address from the calling party address

    • The global title address from the called party address (only if the Enhanced GSM MAP Screening feature is enabled and turned on).

    Note:

    If the MTPMAP Screening is enabled and turned on, the MSU (SCCP message types 9 - UDT, or 10 - UDTS only) is sent to GSMMAP Screening even if the MSU does not require GTT and is MTP routed.
  2. GSMMAP Screening performs a lookup in the origination SSN table for an entry with the SSN of calling party address. If an entry is not found, GSMMAP screening is stopped and the message is routed to its destination using global title translation.
  3. GSMMAP Screening performs a lookup in the destination SSN table for an entry with the SSN of called party address. If an entry is not found, GSMMAP screening is stopped and the message is routed to its destination using global title translation.
  4. GSMMAP Screening checks to see if the CGPA and CDPAGTI values are supported in the EAGLE. The EAGLE supports only these GTI values: for an ANSI message - GTI value of 2; for an ITU message - GTI values of 2 or 4. If the CGPA and CDPAGTI values are supported, the GTA values are decoded. If the GTI values are not supported in the EAGLE, the GTA, NAI, and NP values for the CGPA or CDPA are set to asterisk (*). The asterisk (*) values for the GTA, NAI, and NP parameters allows the action of the provisioned wildcard entries for the CGPA/CDPAMAP screening tables to be performed, or the action for the OPCODE table to be performed (if no wildcard entries are provisioned for the CGPA or CDPA in the GSMMAP screening table).
  5. The MAP operations code and parameters are extracted from the MAP message. If the TCAP Package Type of the message is ITUTC-BEGIN, GSMMAP Screening continues.

    If the GMSTCAPCE SCCP option is set to on and the TCAP Package Type is either ITU TC-CONTINUE or ITU TC-END, GSM MAP Screening continues. In order for GSM MAP Screening to be performed on these messages, the messages must meet the following requirements:

    • ITUTC-CONTINUE messages must have an Invoke component type.
    • ITUTC-END messages must have a Return-Result (Test) type.

    If the TCAP Package Type of the message is not ITU TC-BEGIN, GSM MAP Screening is stopped and the message is routed to its destination using global title translation, as if the message passed GSM MAP screening.

    If the GMSTCAPCE SCCP option is set to on, and the TCAP Package Type of the message is not ITU TC-CONTINUE or ITU TC-END, GSM MAP Screening is stopped and the message is routed to its destination using global title translation, as if the message passed GSM MAP screening.

    If the TCAP portion is not in a valid format, the action defined by the GSM MAP screening decode error action from the STP option table (pass or discard) is performed and a UIM is generated indicating that an Invalid TCAP message received.

  6. GSMMAP Screening performs a lookup in the MAP screening table for an entry with the MAP operations code of the MAP message. If an entry is not found, the default action from the STP option table is performed. If the default action parameter value is pass, the message is routed to its destination. If the default action parameter value is discard, the message is discarded.
  7. GSMMAP Screening performs a lookup in the GSMMAP screening table for an entry containing the global title address of the calling party address. If an entry is not found in the GSMMAP screening table, the screening action defined in the GSMMAP operations code table by the dfltact parameter of the ent-gsms-opcode command is performed.
  8. If the Enhanced GSMMAP Screening feature is enabled and turned on, GSMMAP Screening performs a lookup for an entry for the called party address in the GSMMAP screening table.
  9. If an entry is found in the MAP screening table, the forbidden parameter from the GSMMAP screening table is checked. If the forbidden parameter value is none, the message is routed to its destination. If the forbidden parameter value is all, the screening action defined in the GSMMAP screening table by the action parameter of the ent-gsmmap-scrn command is performed. For any other forbidden parameter, the parameter list of the message is examined. If the message is an ATI request and the forbidden parameter is found in the parameter list, then the screening action defined in the GSMMAP screening table by the action parameter of the ent-gsmmap-scrn command is performed.

    The screening actions defined by the dfltact parameter of the ent-gsms-opcode command and the action parameter of the ent-gsmmap-scrn command are:

    • DISCARD – do not route the MSU. The MSU is discarded (thrown away) and the appropriate UIM is issued. This is the default action value.
    • PASS – route the message as normal to the destination and the appropriate UIM is issued.
    • ATIERR – do not route the MSU and send a rejection message back to the originator.
    • ROUTE – route the message as normal to the original destination node, defined by global title translation.
    • FORWARD – route the original message to the forward node. The original message is not sent to the original node. If, however, the forwarded node is not available for routing then the MSU is routed to the original node, defined by global title translation.
    • DUPLICATE – route the message as normal to the original destination, defined by global title translation, and route a copy of the original message to the duplicate node. If the MSU fails to route to the duplicate node, then a UIM is generated indicating the duplicate routing failure.
    • DUPLICATE AND DISCARD – route the original message to the duplicate node. The original message is not sent to the original node. If, however, the duplicate node is not available for routing then the MSU is discarded.

    Figure 5-2 shows how GSM MAP screening is performed.

Figure 5-2 GSM MAP Screening Details



Sheet 1 of 15



Sheet 2 of 15



Sheet 3 of 15



Sheet 4 of 15



Sheet 5 of 15



Sheet 6 of 15



Sheet 7 of 15



Sheet 8 of 15



Sheet 9 of 15



Sheet 10 of 15



Sheet 11 of 15



Sheet 12 of 15



Sheet 13 of 15



Sheet 14 of 15



Sheet 15 of 15

GSM MAP Screening Example

Table 5-1 shows an example of the GSM MAP screening table.

Table 5-1 Example GSM MAP Screening Table

Authorized Origination Point (E.164 address)

Numbering Plan

Nature of Address Indicator

MAP Operations Code

Forbidden Parameters

Screening Action

6611273888

1

4

ATI_Request

All

Discard

6611273444

1

4

SRI_for_SM

All

Discard

6611273444

1

4

ATI_Request

Subscriber state

ATI-error

5431111888

1

4

FW_SM

None

----

5431111777

1

4

ATI_Request

All

Pass

In this example,

  • Any ATI_Request message from 6611273888 containing the numbering plan value of 1 and nature of address indicator value of 4 would be discarded.

  • Any SRI_for_SM from 6611273444 containing the numbering plan value of 1 and nature of address indicator value of 4 would be discarded.

  • An ATI_Request message from 6611273444 containing the numbering plan value of 1 and nature of address indicator value of 4 requesting the Location only would be routed. An ATI_Request message from 6611273444 requesting both the Location and Subscriber state would result in an ATI-error message being sent back to the originator. An ATI_Request message from 6611273444 requesting the Subscriber state only would result in an ATI-error message being sent back to the originator.

  • A FW_SM message from 5431111888 containing the numbering plan value of 1 and nature of address indicator value of 4 would be routed successfully, because no parameters are forbidden.

  • Any ATI_Request from 5431111777 containing the numbering plan value of 1 and nature of address indicator value of 4 would be routed successfully because of the “Pass” screening action. This could be used for testing purposes prior to screening.

Table 5-2 shows an example of the system-wide screening table. It specifies the action to be taken in the event that a MAP operations code was defined for MAP screening, but no specific entry was found in the MAP screening table.

Table 5-2 System-Wide Screening Table

MAP Operations Code

Operations Code Specific Screening Action

ATI

ATI-error

SRI_for_SM

Discard

GSM MAP Screening Procedures

The following procedures describe the steps needed to add, remove, or change GSM MAP Screening data in the database.

The items administered in this section are:

  • Linkset with GSMMAP Screening enabled
  • STP options for GSMMAP Screening
  • GSM SSN
  • GSM Opcodes
  • GSMMAP Screening entries
  • An option to enable or disable the processing of GSMMAP Screening TCAP Continue and TCAP End messages.

The procedures shown in this chapter use a variety of commands. For more information on these commands, refer to Commands User's Guide.

Figure 5-3 shows the relationships of the database elements that are configured in these procedures.

The following is a brief description of the GSM MAP Screening entities. These entities must be configured in the order that they are shown.

  1. The Global Title Translation (GTT) feature must be turned on with the chg-feat command using the gtt=on parameter. The global title translation feature must be on before the GSMMAP Screening feature can be enabled and turned on. Verify that the GTT feature is on using the rtrv-feat command.

    Note:

    Once the Global Title Translation (GTT) feature is turned on with the chg-feat command, it cannot be turned off.

    The GTT feature must be purchased before turning on the GTT feature. If you are not sure whether you have purchased the GTT feature, contact your Sales Representative or Account Representative.

  2. The GSMMAP Screening feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Verify the status of the GSMMAP Screening feature with the rtrv-ctrl-feat command.

    Note:

    Once the GSMMAP Screening feature is enabled and turned on, it cannot be disabled or turned off.

  3. GSM MAP Screening can process TCAP Continue and TCAP End messages in addition to TCAP Begin messages by setting the SCCP option parameter GMSTCAPCE to on with the chg-sccpopts command. Setting the SCCP option parameter GMSTCAPCE to off disables the processing of the TCAP Continue and TCAP End messages. The current value of the GMSTCAPCE parameter is shown in the rtrv-sccpopts output. For more information on setting the SCCP option parameter GMSTCAPCE, see the Changing the GSM MAP Screening TCAP Continue and End Message Processing Option procedure.

  4. To use GSMMAP Screening on all types of linksets including ANSI linksets, or to provision CDPA entries in the GSMMAP Screening table, the Enhanced GSMMAP Screening feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Verify the status of the Enhanced GSMMAP Screening features with the rtrv-ctrl-feat command.

    Note:

    Once the Enhanced GSMMAP Screening feature is enabled and turned on, it cannot be disabled or turned off.
  5. MSUs that do not require global title translation and are MTP routed can be sent to GSMMAP Screening only of the MTPMAP Screening feature is enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. The Enhanced GSMMAP Screening feature must be enabled and turned on to enable and turn on the MTPMAP Screening feature.
  6. Linksets containing the gsmscrn=on parameter must be in the database. The gsmscrn=on parameter allows the messages on these linksets to be screened by the GSMMAP Screening feature. Verify this with the rtrv-ls command. If the necessary linksets are not in the database, add them with the ent-ls command, specifying the gsmscrn=on parameter. If the necessary linksets are in the database, but do not contain the gsmscrn=on parameter, change these linksets with the chg-ls command, specifying the gsmscrn=on parameter. If the Enhanced GSMMAP screening feature is enabled and on, the adjacent point code of the linkset can be any type. If the Enhanced GSMMAP screening feature is not enabled and off, the adjacent point code of the linkset can be either an ITU international, ITU international spare, or 14 bit ITU national, 14-bit ITU national spare, or 24-bit ITU national point code. The EAGLE can contain either 14 bit or 24-bit ITU national point codes, but not both at the same time.
  7. The GSMMAP screening options, gsmdflt (GSMMAP screening default action) and gsmdecerr (GSMMAP screening decode error action), can be changed with the chg-stpopts command. The current values for these options can be verified with the rtrv-stpopts command. The GSMDFLT parameter allows the user to specify the default screening action (PASS or DISCARD) that occurs when a MAP operations code contained in the MSU is not found in the GSMMAP operations code table. The gsmdecerr parameter allows the user to specify the default screening action (PASS or DISCARD) that occurs when an error is detected in the TCAP layer of the MSU being screened. Such errors included an invalid value for a parameter, length error, missing data, and so on.
  8. The origination and destination subsystem numbers that are being screened using the GSMMAP screening feature need to be provisioned in the database. These subsystem numbers are shown in the rtrv-gsmssn-scrn command and provisioned using the ent-gsmssn-scrn command.
  9. The concerned GSMMAP screening operation codes and the default screening action for the operation code need to be provisioned in the database. These operation codes are shown in the rtrv-gsms-opcode command and provisioned using the ent-gsms-opcode command. The ent-gsms-opcode allows the user to provision a list of all operation codes that the EAGLE uses in performing GSM screening. If a point code and subsystem number is provisioned for the GSMMAP screening operation code, the point code and subsystem number must be shown in the rtrv-map output. If the flexible GTTLoad Sharing feature is enabled, a MAP set containing the point code and subsystem number must be assigned to the GSMMAP screening operation code. For more information on provisioning GSMMAP screening operation codes, see the Adding a GSM MAP Screening Operation Code procedure.
  10. The GSMMAP screening entries that filter or allow TCAP messages for certain MAP operation codes need to be provisioned in the database. The GSMMAP screening entries are shown in the rtrv-gsmmap-scrn command and provisioned using the ent-gsmmap-scrn command. The messages are filtered or allowed based on the origination addresses (saddr/eaddr), numbering plan value (npv), nature of address indicator value (naiv), MAP opnames (opname), and forbidden (forbid) parameters. If the Enhanced GSMMAP Screening feature is enabled and on, the CGPA and CDPA of the messages are checked by the GSMMAP Screening table. If the Enhanced GSMMAP Screening feature is not enabled and off, only the CGPA of the messages are checked by the GSMMAP Screening table. If a point code and subsystem number is provisioned for the GSMMAP screening entry, the point code and subsystem number must be shown in the rtrv-map output. If the Flexible GTTLoad Sharing feature is enabled, a MAP set containing the point code and subsystem number must be assigned to the GSMMAP screening entry. For more information on provisioning GSMMAP screening operation entries, see the Adding a GSM MAP Screening Entry procedure.

Figure 5-3 GSM MAP Screening Database Relationships



Sheet 1 of 2



Sheet 2 of 2

Activating the GSM MAP Screening Feature

The GSM MAP screening feature is activated by enabling the GSM MAP Screening feature with the enable-ctrl-feat command, then by turning the feature on with the chg-ctrl-feat command. The status of the GSM MAP Screening feature can be verified with the rtrv-ctrl-feat command. Before the GSM MAP Screening feature is activated, the global title translation feature must be on. This can be verified with the rtrv-feat command.

Note:

Once the global title translation feature is turned on with the chg-feat command, it cannot be turned off.

The global title translation feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure if you have purchased the global title translation feature, contact your Sales Representative or Account Representative.

This procedure can also be used to enable and turn on the Enhanced GSM MAP Screening feature. The enable-ctrl-feat and chg-ctrl-feat commands are used to enable and turn on the Enhanced GSM MAP Screening feature. The GSM MAP Screening feature must be enabled and turned on before the Enhanced GSM MAP Screening feature is enabled and turned on.

The enable-ctrl-feat command enables the feature by inputting the feature’s access key and the feature’s part number with these parameters:

:fak – The feature access key supplied by Oracle. The feature access key contains 13 alphanumeric characters and is not case sensitive.

:partnum – The Oracle-issued part number of the GSM MAP Screening and Enhanced GSM MAP Screening features.

  • The GSMMAP Screening feature, 893013201
  • The Enhanced GSMMAP Screening feature, 893012401

The enable-ctrl-feat command requires that the database contain a valid serial number for the EAGLE, and that this serial number is locked. This can be verified with the rtrv-serial-num command. The EAGLE is shipped with a serial number in the database, but the serial number is not locked. The serial number can be changed, if necessary, and locked once the EAGLE is on-site, with the ent-serial-num command. The ent-serial-num command uses these parameters.

:serial – The serial number assigned to the EAGLE. The serial number is not case sensitive.

:lock – Specifies whether or not the serial number is locked. This parameter has only one value, yes, which locks the serial number. Once the serial number is locked, it cannot be changed.

Note:

To enter and lock the EAGLE’s serial number, the ent-serial-num command must be entered twice, once to add the correct serial number to the database with the serial parameter, then again with the serial and the lock=yes parameters to lock the serial number. You should verify that the serial number in the database is correct before locking the serial number. The serial number can be found on a label affixed to the control shelf (shelf 1100).

The GSM MAP Screening and Enhanced GSM MAP Screening features cannot be temporarily enabled (with the temporary feature access key).

Once these features have been enabled, the features must be turned on with the chg-ctrl-feat command. The chg-ctrl-feat command uses these parameters:

:partnum – The Oracle-issued part number of the GSMMAP Screening and Enhanced GSM MAP Screening features.

  • The GSMMAP Screening feature, 893013201
  • The Enhanced GSMMAP Screening feature, 893012401

    :status=on – used to turn on the features that customer has purchased and enabled.

    Note:

    Once the GSMMAP Screening and Enhanced GSMMAP Screening features are turned on, they cannot be turned off.

The status of the features in the EAGLE is shown with the rtrv-ctrl-feat command.

The GSM MAP Screening feature requires that (5-SM4G cards are installed and provisioned in the EAGLE. The Enhanced GSM MAP Screening feature requires that Service Module cards (E5-SM4G cards) are installed and provisioned in the EAGLE. E5-SM4G cards are shown by the entry DSM in the TYPE column of the rtrv-card output and SCCP in the APPL column of the rtrv-card output.

  1. Display the status of the controlled features by entering the rtrv-ctrl-feat command. 
    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
HC-MIM SLK Capacity       893012707  on      64
Command Class Management  893005801  on      ----
LNP Short Message Service 893006601  on      ----
Intermed GTT Load Sharing 893006901  on      ----
XGTT Table Expansion      893006101  on      400000
XMAP Table Expansion      893007710  off     ----
Large System # Links      893005910  on      2000
Routesets                 893006401  on      6000

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 GSM MAP Screening feature (shown in the rtrv-ctrl-feat output as GSM Map Screening (GMS)) is enabled and on, no further action is necessary. This procedure does not need to be performed.

    If you wish to use the Enhanced GSM MAP Screening feature, and the Enhanced GSM MAP Screening feature (shown in the rtrv-ctrl-feat output as Enhanced GMS (EGMS)) is enabled and on, no further action is necessary. This procedure does not need to be performed.

    If the GSM MAP Screening feature is enabled and off, skip steps 2 through 7 and go to step 8.

    If the Enhanced GSM MAP Screening feature is enabled and off, skip steps 2 through 10 and go to step 11.

  2. Display the cards in the EAGLE using the rtrv-card command.
    The GSMMAP Screening feature requires that Service Module cards are in the database. The Enhanced GSMMAP Screening feature requires that E5-SM4G/E5-SM8G cards are in the database.
    
rlghncxa03w 09-05-25 09:58:31 GMT EAGLE5 45.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1113   E5-MCAP   OAMHC
1114   E5-TDM-A
1115   E5-MCAP   OAMHC
1116   E5-TDM-B
1117   E5-MDAL
1201   LIMDS0    SS7ANSI   sp2           A    0   sp1           B    0
1203   LIMDS0    SS7ANSI   sp3           A    0   
1204   LIMDS0    SS7ANSI   sp3           A    1   
1206   LIMDS0    SS7ANSI   nsp3          A    1   nsp4          B    1    
1308   LIMDS0    SS7ANSI   sp6           A    1   sp7           B    0
1314   LIMDS0    SS7ANSI   sp7           A    1   sp5           B    1

    DSM and E5-SM4G cards are shown by the entry DSM in the TYPE column and VSCCP in the APPL column of the rtrv-card output.

    If no Service Module cards are shown in the rtrv-card output, perform the “Adding a Service Module” procedure in Database Administration - GTT User's Guide and add the required Service Module cards to the database.

    If E5-SM4G cards are in the EAGLE, go to step 3.

    Note:

    If the rtrv-ctrl-feat output in step 1 shows any controlled features, skip steps 3 through 6, and go to step 7. If the rtrv-ctrl-feat output shows only the HC-MIMSLK Capacity feature with a quantity of 64, steps 3 through 6 must be performed.
  3. Display the serial number in the database with the rtrv-serial-num command.

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
Command Completed

    Note:

    If the serial number is correct and locked, skip steps 4, 5, and 6, and go to step 7. If the serial number is correct but not locked, skip steps 4 and 5, and go to step 6. If the serial number is not correct, but is locked, the GSMMAP Screening and Enhanced GSMMAP Screening features cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to unresolvable-reference.html#GUID-3FA61F5C-C612-4DBC-B090-8EF65AD958FD for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
  4. Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.

    For this example, enter this command.

    ent-serial-num:serial=<EAGLE’s correct serial number>

  5. Verify that the serial number entered into step 4 was entered correctly using the rtrv-serial-num command. 
    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
Command Completed

    If the serial number was not entered correctly, repeat steps 4 and 5 and re-enter the correct serial number.

  6. Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in step 3, if the serial number shown in step 3 is correct, or with the serial number shown in step 5, if the serial number was changed in step 4, and with the lock=yes parameter.

    For this example, enter this command.

    ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

  7. Enable the GSMMAP Screening feature with the enable-ctrl-feat command specifying the part number for the GSMMAP Screening feature and the feature access key.
    Enter this command.

    enable-ctrl-feat:partnum=893013201:fak=<GSM MAP Screening feature access key>

    Note:

    A temporary feature access key cannot be specified to enable this feature.

    Note:

    The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the GSMMAP Screening feature, contact your Oracle Sales Representative or Account Representative.
  8. Turn the GSMMAP Screening feature on with the chg-ctrl-feat command specifying the part number for the GSMMAP Screening feature and the status=on parameter.
    Enter this command.

    chg-ctrl-feat:partnum=893013201:status=on

    Note:

    Once the GSMMAP Screening feature is turned on, it cannot be turned off.
  9. Verify the changes by entering the rtrv-ctrl-featcommand with the GSMMAP Screening feature part number.

    Enter this command.

    rtrv-ctrl-feat:partnum=893013201 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
GSM Map Screening (GMS)   893013201  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.
  10. Enable the Enhanced GSMMAP Screening feature with the enable-ctrl-feat command specifying the part number for the Enhanced GSMMAP Screening feature and the feature access key.

    Note:

    If you do not wish to enable and turn on the Enhanced GSMMAP Screening feature, skip steps 10, 11, and 12, and go to step 13.
    Enter this command.enable-ctrl-feat:partnum=893012401:fak=<Enhanced GSM MAP Screening feature access key>

    Note:

    A temporary feature access key cannot be specified to enable this feature.

    Note:

    The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the Enhanced GSMMAP Screening feature, contact your Oracle Sales Representative or Account Representative.
  11. Turn the Enhanced GSMMAP Screening feature on with the chg-ctrl-feat command specifying the part number for the Enhanced GSMMAP Screening feature and the status=on parameter.
    Enter this command.

    chg-ctrl-feat:partnum=893012401:status=on

    Note:

    After the Enhanced GSMMAP Screening feature is turned on, it cannot be turned off.
  12. Verify the changes by entering the rtrv-ctrl-featcommand with the Enhanced GSMMAP Screening feature part number.
    Enter this command.

    rtrv-ctrl-feat:partnum=893012401 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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.
  13. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-4 Activating the GSM MAP Screening Feature



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6

Configuring the MTP MAP Screening Feature

Note:

When MTP routed messages are routed through SCCP Service Modules for MTP MAP screening, Eagle may replace the original OPC in message with secondary point code provisioned for the DPC (if a secondary point code is already provisioned for the DPC in the destination table), or with secondary point code provisioned for the linkset (if the linkset is uses MLS feature and the linkset is direct route to the destination), even if messages pass (no MAP screening action is performed) MAP screening.

The MTP MAP screening feature is enabled with the enable-ctrl-feat command. Once enabled, the feature can be turned on or off with the chg-ctrl-feat command. If the feature is already on, it can only be turned off. If the feature is off, it can only be turned on.

Before the MTP MAP Screening feature is enabled and turned on, the Enhanced GSM MAP Screening feature must be enabled and on. The Measurements Platform must be enabled if MTP MAP Screening measurements is desired.

The status of the MTP MAP Screening and Enhanced GSM MAP Screening features can be verified with the rtrv-ctrl-feat command. The rtrv-measopts command shows whether the Measurements Platform is enabled or not.

The enable-ctrl-feat command enables the feature by inputting the feature’s access key and the feature’s part number with these parameters:

Note:

As of Release 46.3, the fak parameter is no longer required. This parameter is only used for backward compatibility.

:fak – The feature access key supplied by Oracle. The feature access key contains 13 alphanumeric characters and is not case sensitive.

:partnum – The Oracle-issued part number of the MTP MAP Screening feature, 893013501

The MTP MAP Screening feature cannot be temporarily enabled (with a temporary feature access key).

The chg-ctrl-feat command uses these parameters:

:partnum – The Oracle-issued part number of the MTP MAP Screening feature, 893013501.

:status=on – used to turn the MTP MAP Screening feature on.

:status=off – used to turn the MTP MAP Screening feature off.

Note:

Turning the MTPMAP Screening feature on allows GSMMAP Screening to be performed on all SCCP messages, even if these messages do not require Global Title Translation and are MTP routed. The value of the GSMSCRN parameter of the linkset carrying these SCCP messages must be YES.

Note:

Turning the MTPMAP Screening feature off allows GSMMAP Screening to be performed only on those SCCP messages, on linksets with the GSMSCRN=YES value, that have passed Global Title Translation and Gateway Screening.

Note:

When MTP routed messages are routed through SCCP Service Modules for MTP MAP Screening, Eagle may replace the original OPC in the message with a secondary point code provisioned for the DPC (if a secondary point code is already provisioned for the DPC in the destination table), or with a secondary point code provisioned for the linkset (if the linkset is uses MLS feature and the linkset is a direct route to the destination), even if messages pass (no MAP screening action is performed) MAP screening.
  1. Display the status of the controlled features by entering the rtrv-ctrl-feat command.

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
HC-MIM SLK Capacity       893012707  on      64
Command Class Management  893005801  on      ----
LNP Short Message Service 893006601  on      ----
Intermed GTT Load Sharing 893006901  on      ----
XGTT Table Expansion      893006101  on      400000
XMAP Table Expansion      893007710  off     ----
Large System # Links      893005910  on      2000
Routesets                 893006401  on      6000

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 MTP MAP Screening feature (shown in the rtrv-ctrl-feat output as MTP Map Screening) is enabled and on, and you do not wish to turn the feature off, no further action is necessary. If you wish to turn this feature off, skip steps 2 through 4, and go to step 5.

    If the MTP MAP Screening feature is enabled and off, skip steps 2 through 4 and go to step 5 to turn the feature on.

  2. If the rtrv-ctrl-feat in step 1 shows that the Enhanced GSMMAP Screening feature is enabled and on, skip this step and go to step 3.

    If the rtrv-ctrl-feat in step 1 shows that the Enhanced GSM MAP Screening feature is not enabled or off, perform the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSM MAP Screening feature.

  3. Verify whether or nor the Measurements Platform option is enabled (PLATFORMENABLE = on) using the rtrv-measopts command. 
    
rlghncxa03w 06-10-01 16:02:05 GMT  EAGLE5 36.0.0 

PLATFORMENABLE = on
COLLECT15MIN     = off
CLLIBASEDNAME    = off
----------------------
SYSTOTSTP        = off
SYSTOTTT         = off

    Note:

    The rtrv-measopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-measopts command, see the rtrv-measopts command description in the Commands User's Guide.

    If the Measurements Platform is not enabled, perform the “Configuring the Measurements Platform Feature” procedure in Database Administration - System Management User's Guide to enabled the Measurements Platform.

  4. Enable the MTPMAP Screening feature with the enable-ctrl-feat command specifying the part number for the MTPMAP Screening feature and the feature access key.

    Enter this command.

    enable-ctrl-feat:partnum=893013501:fak=<MTP MAP Screening feature access key>

    Note:

    A temporary feature access key cannot be specified to enable this feature.

    Note:

    The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the Enhanced GSMMAP Screening feature, contact your Oracle Sales Representative or Account Representative.
  5. Turn the MTPMAP Screening feature on or off with the chg-ctrl-feat command specifying the part number for the Enhanced GSMMAP Screening feature and either the status=on or status=off parameter.

    To turn the MTP MAP Screening feature on, enter this command.

    chg-ctrl-feat:partnum=893013501:status=on

    To turn the MTP MAP Screening feature off, enter this command.

    chg-ctrl-feat:partnum=893013501:status=off

  6. Verify the changes by entering the rtrv-ctrl-featcommand with the MTPMAP Screening feature part number.
    Enter this command.

    rtrv-ctrl-feat:partnum=893013501

    In the following example, the feature Status is on. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
MTP MAP Screening         893013501  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.

    In the following example, the feature Status is off 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
MTP MAP Screening         893013501  off     ----

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.
  7. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-5 Configuring the MTP MAP Screening Feature



Sheet 1 of 2



Sheet 2 of 2

Configuring a Linkset for the GSM MAP Screening Feature

This procedure is used to configure SS7 linksets for the GSM MAP Screening feature using the gsmscrn parameter of either the ent-ls or chg-ls command.

The gsmscrn parameter specifies whether or not GSM MAP screening is applied to messages arriving on the linkset. This parameter can be applied to all linksets, but this parameter can be specified for linksets with ANSI adjacent point codes only if the Enhanced GSM MAP Screening feature is enabled and on. The values for this parameter are on (GSM MAP screening is applied to the linkset) or off (GSMMAP screening is not applied to the linkset). GSM MAP screening is used to screen GSM MAP messages to control which external entities can request information about a GSM subscriber and the specific information these entities can request before allowing the GSM MAP message to pass through to the HLR.

Before the gsmscrn parameter can be specified for a specific linkset, the GSM MAP screening feature must be enabled and on. The status of the GSM MAP Screening feature, and if applicable the Enhanced GSM MAP screening feature, is shown in the rtrv-ctrl-feat command output with the entries GSM Map Screening (GMS) (for the GSM MAP Screening feature) and Enhanced GMS (EGMS) (for the Enhanced GSM MAP Screening feature). Perform the Activating the GSM MAP Screening Feature procedure to enable and turn on either of these features as required.

The value of the gsmscrn parameter is only displayed in the rtrv-ls command output when a specific linkset is being displayed with the rtrv-ls:lsn=<linkset name> command.

To configure a linkset for the GSM MAP Screening feature, the ent-ls or chg-ls commands uses these mandatory parameters in addition to the gsmscrn parameter.

  • :lsn – The name of the linkset. The linkset name can contain up to 10 characters, with the first character being a letter.
  • :apc/apca/apci/apcn/apcn24 – Adjacent point code – the point code identifying the node that is next to the EAGLE. This parameter is only mandatory for the ent-ls command.

Note:

See Chapter 2, Configuring Destination Tables in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

Note:

The EAGLE can contain a 14-bit ITU-N point code (apcn) or a 24-bit ITU-N point code (apcn24), but not both at the same time.
  • :lst – The linkset type of the specified linkset This parameter is only mandatory for the ent-ls command.

The ent-ls and chg-ls commands contain other optional parameters that can be used to configure a linkset. These parameters are not shown here because they are not necessary for configuring a linkset for the GSMMAP Screening feature. These parameters are explained in more detail in the Adding an SS7 Linkset procedure or in the Changing an SS7 Linkset procedure in Database Administration - SS7 User's Guide, or in the ent-ls and chg-ls command descriptions in Commands User's Guide.

The EAGLE can contain 1024 linksets, with a maximum of 255 of these linksets being gateway linksets. A gateway linkset is a linkset that contains routes to a different network.

This examples used in this procedure are based on the examples shown in Table 5-3.

Table 5-3 GSM MAP Screening Linkset Configuration Table

Linkset Names Linkset APC LST GSMSCRN

New Linksets Being Added

lsn5

10685

a

on

lsi7

3-150-4

a

on

Existing Linkset Being Changed

lsn4

N/A

N/A

on

The linkset to be added cannot be in the database. This can be verified in step 1 of this procedure.

Canceling the RTRV-LS and RTRV-DSTN Commands

Because the rtrv-ls and rtrv-dstn commands used in this procedure can output information for a long period of time, the rtrv-ls and rtrv-dstn commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls and rtrv-dstn commands can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-ls or rtrv-dstn commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls or rtrv-dstn commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls or rtrv-dstn commands were entered, from another terminal other that the terminal where the rtrv-ls or rtrv-dstn commands were entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the current linkset configuration using the rtrv-ls command.

    This is an example of the possible output. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsa1         240-020-000   scr1  1   1   yes a   1    off off off no    off
lsa2         240-030-000   scr2  1   2   no  c   3    on  on  on  yes   off
lsa3         240-040-000   scr3  1   3   yes c   5    off off off yes   off
ls04         001-002-003   scr2  1   1   no  a   4    on  off on  yes   off

                                 L3T SLT              GWS GWS GWS
LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsi1         1-111-1       scr1  1   1   yes a   1    off off off ---   ---
lsi2         1-111-2       scr2  1   2   no  c   3    on  on  on  ---   ---
lsi3         1-111-3       scr3  1   3   yes c   5    off off off ---   ---

                                 L3T SLT              GWS GWS GWS
LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn1         11111         scr1  1   1   yes a   1    on  off off ---   off
lsn2         11112         scr2  1   2   no  c   3    on  on  on  ---   off
lsn3         11113         scr3  1   3   yes c   5    on  off off ---   off
lsn5         10685         scr1  1   3   yes a   4    on  off off ---   off

Link set table is ( 10 of 1024)  1% full
  2. Display the point code and capability point code of the EAGLE by using the rtrv-sid command.

    Note:

    If the APC of an existing linkset is not being changed, skip steps 2, 3, and 4, and go to step 5.

    This is an example of the possible output. 

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
PCA              PCI             PCN           CLLI            PCTYPE
001-001-001      3-150-4         13482         rlghncxa03w     OTHER
               s-3-150-4       s-13482
CPCA
002-002-002       002-002-003       002-002-004      002-002-005
002-002-006       002-002-007       002-002-008      002-002-009
004-002-001       004-003-003       144-212-003

CPCA (LNP)
005-005-002      005-005-004      005-005-005

CPCI
1-001-1           1-001-2           1-001-3          1-001-4

CPCN
02091             02092             02094             02097
02191             02192             11177

    If you wish to use ITU-I or ITU-N spare point codes with GSMMAP Screening, and the rtrv-sid output does not show any ITU-I or ITU-N spare point codes, add ITU-I and ITU-N spare point codes, as necessary, to the self identification of the EAGLE by performing the “Changing the Self-Identification of the EAGLE” procedure in Database Administration - SS7 User's Guide.

  3. Display the point codes in the destination point code table by using the rtrv-dstn command with the linkset’s adjacent point code.

    For this example, enter these commands.

    rtrv-dstn:dpci=3-150-4

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
3-150-4       lsi7clli    yes --- --------------   --------------   SS7

SPCI         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
-----------  ----         none   off   none     no     no    none

Destination table is (28 of 2000) 1% full
Alias table is (5 of 8000) 1% full

    rtrv-dstn:dpcn=10685

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
DPCN          CLLI        BEI ELEI   ALIASA           ALIASI        DMN
10685         lsn5clli    yes --- --------------   --------------   SS7

SPCI         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
-----------  ----         none   off   none     no     no    none

Destination table is (28 of 2000) 1% full
Alias table is (5 of 8000) 1% full

    If the point code specified in the rtrv-dstn command in this step is not in the database, the following message is displayed. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

No destinations meeting the requested criteria were found

Destination table is (28 of 2000) 1% full
Alias table is (5 of 8000) 1% full

    If a linkset is being added to the database, or the adjacent point code of the linkset is being changed, and the adjacent point code is not shown in the rtrv-dstn command output, go to the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the adjacent point code to the destination point code table.

    Note:

    An ANSI point code can be used as the APC of a linkset for GSMMAP Screening only if the Enhanced GSMMAP Screening feature is enabled and on.
  4. The adjacent point code of the linkset cannot be the DPC of any exception route.

    Note:

    If the adjacent point code was added in step 3, skip step 4 and go to step 5.

    Verify that the adjacent point code of the new linkset is not the DPC of any exception route by entering the rtrv-rtx command with the dpc/dpca/dpci/dpcn/dpcn24 parameter. The dpc/dpca/dpci/dpcn/ dpcn24 parameter value is the adjacent point code value that will be specified for the new linkset. For this example, enter this command.

    rtrv-rtx:dpci=3-150-4

    This is an example of the possible output. 

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
    DPCI          RTX-CRITERIA              LSN        RC    APC
    3-150-4       OPCI
                  4-050-1                   lsi2       20    1-111-2
 DESTINATION ENTRIES ALLOCATED:   2000
     FULL DPC(s):                   13
     EXCEPTION DPC(s):               5
     NETWORK DPC(s):                 0
     CLUSTER DPC(s):                 1
     TOTAL DPC(s):                  19
     CAPACITY (% FULL):              1%
 ALIASES ALLOCATED:               12000
     ALIASES USED:                   0
     CAPACITY (% FULL):              0%
 X-LIST ENTRIES ALLOCATED:         500

    If the adjacent point code of the linkset is not the DPC of a route exception table entry, no entries are displayed in the rtrv-rtx output, but a summary of the point code quanties is displayed, as shown in the following output example. 

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   15
        EXCEPTION DPC(s):               5
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  21
        CAPACITY (% FULL):              1%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   0
        CAPACITY (% FULL):              0%
    X-LIST ENTRIES ALLOCATED:         500

    If the point code specified in this step is shown in the DPCA/DPCI/DPCN/ DPCN24 columns in this step, the point code value cannot be used as an adjacent point code unless one of two actions are taken:

    • Choose another adjacent point code value and repeat steps 2, 3, and 4.
    • Remove all the entries displayed in this step by performing the “Removing a Route Exception Entry” procedure in Database Administration - SS7 User's Guide.
  5. Verify that the GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the GSMMAP Screening feature.

    Enter this command.

    rtrv-ctrl-feat:partnum=893013201

    The following is an example of the possible output. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
GSM Map Screening (GMS)   893013201  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 GSM MAP screening feature is not enabled or off, go to the Activating the GSM MAP Screening Feature procedure to enable and turn on the GSM MAP screening feature.

  6. Verify that the Enhanced GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.

    Note:

    If ANSI point codes are not being used, skip step 6 and go to step 7.

    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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 Enhanced GSM MAP screening feature is not enabled or off, go to the Activating the GSM MAP Screening Feature procedure to enable and turn on the Enhanced GSM MAP screening feature.

  7. Display the current linkset configuration of the linkset to be changed using the rtrv-ls command with the linkset name.

    Note:

    If no existing linksets are being changed, skip step 7 and go to step 8.

    For this example, enter this command.

    rtrv-ls:lsn=lsn4

    This is an example of the possible output. 

    rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0

LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn4         09786         scr3  1   2   no  a   2    on  off off no    on

           CLLI         TFATCABMLQ MTPRSE ASL8 SLSRSB ITUTFR GSMSCRN
           lsn4clli     1          ---    ---  1      on     on

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ---   ---      ---       CdPA

                                  L2T               PCR  PCR
           LOC   LINK SLC TYPE    SET  BPS    ECM   N1   N2
           1205  b    0   LIMDS0  1    56000  BASIC ---  -----
           1211  a    2   LIMDS0  1    56000  BASIC ---  -----

Link set table is ( 21 of 1024)  2% full
  8. Add the new linkset to the database using the ent-ls command.

    Note:

    If you are not adding a new linkset to the database, skip step 8 and go to step 9.

    For this example, enter these commands.

    ent-ls:lsn=lsn5:apcn=10685:lst=a:gsmscrn=on

    ent-ls:lsn=lsi7:apci=3-150-4:lst=a:gsmscrn=on

    Note:

    An ANSI point code can be used as the APC of a linkset for GSMMAP Screening only if the Enhanced GSMMAP Screening feature is enabled and on.

    The apci parameter value can be either an ITU-I point code or an ITU-I spare point code.

    The apcn parameter value can be either an ITU-N point code or an ITU-N spare point code.

    When each of these commands have successfully completed, this message should appear. 

    rlghncxa03w 06-10-17 16:23:21 GMT  EAGLE5 36.0.0
Link set table is ( 21 of 1024)  2% full
ENT-LS: MASP A - COMPLTD
  9. Change the gsmscrn parameter value in the existing linkset in the database using the chg-ls command.

    Note:

    If you are not changing an existing linkset in the database, skip step 9 and go to step 10.

    For this example, enter this command.

    chg-ls:lsn=lsn4:gsmscrn=on

    Note:

    The gsmscrn parameter can be specified for a linkset with an ANSIAPC only if the Enhanced GSMMAP Screening feature is enabled and on.

    When this commands has successfully completed, this message should appear. 

    rlghncxa03w 06-10-17 16:23:21 GMT  EAGLE5 36.0.0
Link set table is ( 21 of 1024)  2% full
CHG-LS: MASP A - COMPLTD
  10. Verify the changes using the rtrv-ls command specifying the linkset name specified in either steps 8 or 9 with the lsn parameter.

    For this example, enter these commands.

    rtrv-ls:lsn=lsn4

    This is an example of the possible output. 

    rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0

                                     L3T SLT          GWS GWS GWS
LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn4         09786         scr3  1   2   no  a   2    on  off off no    on

           CLLI         TFATCABMLQ MTPRSE ASL8 SLSRSB ITUTFR GSMSCRN
           lsn4clli     1          ---    ---  1      on     on

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ---   ---      ---       CdPA

                                  L2T               PCR  PCR
           LOC   LINK SLC TYPE    SET  BPS    ECM   N1   N2
           1205  b    0   LIMDS0  1    56000  BASIC ---  -----
           1211  a    2   LIMDS0  1    56000  BASIC ---  -----

Link set table is ( 21 of 1024)  2% full

    rtrv-ls:lsn=lsn5

    This is an example of the possible output. 

    rlghncxa03w 06-10-17 11:43:04 GMT EAGLE5 36.0.0

                                     L3T SLT          GWS GWS GWS
LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn5         10685         none  1   2   no  a   0    off off off no    off

           CLLI         TFATCABMLQ MTPRSE ASL8 SLSRSB ITUTFR GSMSCRN
           lsn5clli     1          ---    ---  1      on     on

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ---   ---      ---       CdPA

Link set table is ( 21 of 1024)  2% full

    rtrv-ls:lsn=lsi7

    This is an example of the possible output. 

    rlghncxa03w 06-10-17 11:43:04 GMT EAGLE5 36.0.0

                                     L3T SLT          GWS GWS GWS
LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsi7         3-150-4       none  1   2   no  a   0    off off off no    off

           CLLI         TFATCABMLQ MTPRSE ASL8 SLSRSB ITUTFR GSMSCRN
           lsn7clli     1          ---    ---  1      off    on

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ---   ---      ---       CdPA

Link set table is ( 21 of 1024)  2% full
  11. Back up the new changes using the chg-db:action=backup:dest=fixed command. 
    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 5-6 Configuring a Linkset for the GSM MAP Screening Feature



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

Changing the System-Wide GSM MAP Screening Options

The GSM MAP screening options can be changed with the chg-stpopts command after the GSM MAP screening feature has been activated. The chg-stpopts command contains two options for GSM MAP screening.

  • GSMDFLT – GSM MAP screening default action – Allows the user to specify the default screening action (PASS or DISCARD) that occurs when a MAP operations code contained in the MSU is not found in the GSM MAP operations code table.

  • gsmdecerr – GSM MAP screening decode error action – Allows the user to specify the default screening action (PASS or DISCARD) that occurs when an error is detected in the TCAP layer of the MSU being screened. Such errors included an invalid value for a parameter, length error, missing data, and so on.

The GSM MAP Screening feature must be enabled and on before performing this procedure. Use the rtrv-ctrl-feat command to verify the status of the GSM MAP Screening feature. If the GSM MAP Screening feature is not enabled and off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSM MAP screening feature.

When the GSM MAP screening feature is activated, the values for the gsmdflt and gsmdecerr parameters are set to pass. The current values for these options can be verified with the rtrv-stpopts command.

  1. Verify that the GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893013201

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
GSM Map Screening (GMS)   893013201  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 GSMMAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSMMAP screening feature.

  2. Display the existing values for the gsmdflt and gsmdecerr parameters by entering the rtrv-stpopts command.
    The value for the gsmdflt parameter is shown in the GSMSDFLT field. The value for the gsmdecerr parameter is shown in the GSMDECERR field. This is an example of the possible output. 
    
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0
STP OPTIONS
-----------------------
GSMDFLT            PASS
GSMDECERR          PASS

    Note:

    The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in the Commands Manual.

  3. Change either the GSMMAP screening default action (gsmdflt) and GSMMAP screening decode error action (gsmdecerr) options using the chg-stpopts command.

    If you wish to change both options, enter the chg-stpopts command with the gsmdflt and gsmdecerr parameters as shown in this example.

    chg-stpopts:gsmdflt=discard:gsmdecerr=discard

    If you wish to change only one option, enter the chg-stpopts command with either the gsmdflt and gsmdecerr parameters as shown in these examples.

    chg-stpopts:gsmdflt=discard

    chg-stpopts:gsmdecerr=discard

    For this example, the GSMMAP screening error code action is being changed.

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 00:22:57 GMT  EAGLE5 36.0.0
CHG-STPOPTS: MASP A - COMPLTD
  4. Verify the changes using the rtrv-stpopts command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0
STP OPTIONS
-----------------------
GSMDFLT            PASS
GSMDECERR       DISCARD

    Note:

    The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in the Commands Manual.

  5. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-7 Changing the System-Wide GSM MAP Screening Options



Adding a GSM Subsystem Number Screening Entry

Use this procedure to provision the origination and destination SSNs (subsystem numbers) to be screened with the GSM MAP screening feature using the ent-gsmssn-scrn command.

The ent-gsmssn-scrn command uses these parameters.

:ssn – The subsystem number contained in either the calling party address (CGPA) or the called party address (CDPA) contained in the MAP message.

:type – The type of SSN, either an origination SSN (orig) or a destination SSN (dest). The origination SSN is found in the calling party address of the message. The destination SSN is found in the called party address of the message.

The GSM MAP Screening feature must be enabled and on before performing this procedure. Use the rtrv-ctrl-feat command to verify the status of the GSM MAP Screening feature. If the GSM MAP Screening feature is not enabled and off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSM MAP screening feature.

You cannot specify an ssn and type parameter combination that already exists in the database.

This examples used in this procedure are based on the examples shown in Table 5-4.

Table 5-4 Example GSM MAP Screening SSN Configuration Table

SSN TYPE

250

orig

251

dest
  1. Verify that the GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893013201

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
GSM Map Screening (GMS)   893013201  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 GSMMAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSMMAP screening feature.

  2. Display the GSMMAP Screening subsystem numbers in the database using the rtrv-gsmssn-scrn command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-07 00:28:31 GMT EAGLE5 36.0.0
SSN  ORIG  DEST
  2   Yes   No
 10   Yes   Yes
GSM Map Screening table is (2 of 512) 1% full
RTRV-GSMSSN-SCRN: MASP A - COMPLTD
  3. Add the new subsystem numbers to be screened to the database with the ent-gsmssn-scrn command.
    For this example, enter these commands:

    ent-gsmssn-scrn:ssn=250:type=orig

    ent-gsmssn-scrn:ssn=251:type=dest

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-07 00:29:31 GMT EAGLE5 36.0.0
ENT-GSMSSN-SCRN: MASP A - COMPLTD
  4. Verify the changes using the rtrv-gsmssn-scrn command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-07 00:28:31 GMT EAGLE5 36.0.0
SSN  ORIG  DEST
  2  Yes   No
 10  Yes   Yes
250  Yes   No
251  No    Yes
GSM Map Screening table is (4 of 512) 1% full
RTRV-GSMSSN-SCRN: MASP A - COMPLTD
  5. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-8 Adding a GSM Subsystem Number Screening Entry



Removing a GSM Subsystem Number Screening Entry

Use this procedure to remove an SSN (subsystem number) from the GSM MAP SSN screening table using the dlt-gsmssn-scrn command.

The dlt-gsmssn-scrn command uses these parameters.

:ssn – The subsystem number contained in either the calling party address (CGPA) or the called party address (CDPA) contained in the MAP message.

:type – The type of SSN, either an origination SSN (orig) or a destination SSN (dest). The origination SSN is found in the calling party address of the message. The destination SSN is found in the called party address of the message.

The ssn and type parameter combination specified in the dlt-gsmssn-scrn command must be in the database.

  1. Display the GSMMAP Screening subsystem numbers in the database using the rtrv-gsmssn-scrn command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-07 00:28:31 GMT EAGLE5 36.0.0
SSN  ORIG  DEST
  2  Yes   No
 10  Yes   Yes
250  Yes   No
251  No    Yes
GSM Map Screening table is (4 of 512) 1% full
RTRV-GSMSSN-SCRN: MASP A - COMPLTD
  2. Remove the subsystem number from the database with the dlt-gsmssn-scrn command.
    For this example, enter this command.

    dlt-gsmssn-scrn:ssn=010:type=orig

    dlt-gsmssn-scrn:ssn=251:type=dest

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-07 00:29:31 GMT EAGLE5 36.0.0
DLT-GSMSSN-SCRN: MASP A - COMPLTD
  3. Verify the changes using the rtrv-gsmssn-scrn command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-07 00:28:31 GMT EAGLE5 36.0.0
SSN  ORIG  DEST
  2  Yes   No
 10  No    Yes
250  Yes   No
GSM Map Screening table is (3 of 512) 1% full
RTRV-GSMSSN-SCRN: MASP A - COMPLTD
  4. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-9 Removing a GSM Subsystem Number Screening Entry



Adding a GSM MAP Screening Operation Code

Use this procedure to provision the concerned GSM MAP screening operation codes and the default screening action for the operation code in the database using the ent-gsms-opcode command. This procedure allows the user to provision a list of all operation codes that the EAGLE uses in performing GSM screening.

The ent-gsms-opcode command uses these parameters.

:opcode – The MAP operation code. This parameter refers to the actual decimal value of the MAP operation codes from the TCAP layer of GSM MAP messages.

:opname – The name of operation code. This parameter lets the user give a meaningful name to the MAP operation code (opcode) entered. This name is used by subsequent commands such as dlt-/chg-gsms-opcode and ent-/chg-/dlt-/rtrv-gsmmap-scrn.

:dfltact – The default screening action. This parameter lets the user define a default screening action for the MAP operation code (opcode) entered. The default screening action is used when a matching CGPA (calling party) address is not found in the GSM MAP screening table or when a CGPA address is found but does not have the correct npv and naiv parameters as defined by the ent-gsmmap-scrn command. One of these actions can be assigned.

  • pass – Route the message as normal to the destination.

  • discard – The MSU is to be discarded.

  • atierr – An ATI (Any Time Interrogation) reject message is generated. This option is only valid for ATI MAP operation codes.

  • route – Route the message as normal to the original destination node.

  • forward – Route the original message to the forward node. The original message is not sent to the original node. If, however, the forwarded node is not available for routing then the MSU is routed to the original node.

  • duplicate – Route the message as normal to the original destination and route a copy of the original message to the duplicate node.

  • dupdisc – Duplicate and discard – Route the original message to the duplicate node. The original message is not sent to the original node.

:pc/pca/pci/pcn/pcn24 – The ANSI point code (pc/pca), ITU-I point code or ITU-I spare point code (pci), 14-bit ITU-N point code or 14-bit ITU-N spare point code (pcn), or 24-bit ITU-N point code (pcn24) of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both. To specify the pc/pca parameters, the Enhanced GSM MAP Screening feature must be enabled and on.

:ssn – The subsystem number of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The values for this parameter are 2 to 255, or the value none. The default value for this parameter is none.

:force – The mated application override. Is the GSM MAP screening operation code to be entered without a mated application in the database (yes or no)?

:mapset – The MAP set ID, shown in the rtrv-map command. This parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform the “Activating the Flexible GTT Load Sharing Feature” procedure in Database Administration - GTT User's Guide.

If the Flexible GTT Load Sharing feature is not enabled:

  • The mapset parameter cannot be used.

  • The pc/pca/pci/pcn/pcn24 and ssn values must be shown in the rtrv-map output, or else the force=yes parameter must be specified.

If the Flexible GTT Load Sharing feature is enabled:

  • The mapset parameter can be specified only for GSM OPCODE entries that contain point code and subsystem entries. The dfltact parameter value for these GSM OPCODE entries can be either forward, duplicate, or dupdisc.

  • If the dfltact parameter value for the GSM OPCODE entry will be forward, duplicate, or dupdisc, and the pc/pca/pci/pcn/pcn24 and ssn parameters will be specified for the GSM OPCODE entry, the mapset parameter must be specified.

  • The force=yes parameter can be used only if the MAP set assigned to the GSM OPCODE entry is the default MAP set.

  • If the MAP set assigned to the GSM OPCODE entry is a MAP set other than the default MAP set, the force=yes parameter cannot be used. The point code and subsystem contained in the GSM OPCODE entry must be in the MAP set assigned to the GSM OPCODE entry.

  • If the default MAP set is assigned to the GSM OPCODE entry and the force=yes parameter is not specified, the point code and subsystem contained in the GSM OPCODE entry must be in the default MAP set.

:ri - The routing indicator parameter. This parameter specifies whether a subsequent global title translation is required. This parameter has two values.
  • gt - subsequent global title translation is required.
  • ssn - subsequent global title translation is not required. This is the default value for the ri parameter.

:tt - the translation type that will be assigned to the GSM OPCODE entry. The values for this parameter are 0 to 255, or the value none which specifies that no translation type will be assigned to the GSM OPCODE entry.

The GSM MAP Screening feature must be enabled and on before performing this procedure. Use the rtrv-ctrl-feat command to verify the status of the GSM MAP Screening feature. If the GSM MAP Screening feature is not enabled and off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSM MAP screening feature.

The opcode parameter value must be a number between 0 and 255 or an asterisk (*). The opcode=* parameter can be specified only if the Enhanced GSM MAP Screening feature is enabled and on. Use the rtrv-ctrl-feat command to verify the status of the Enhanced GSM MAP Screening feature. If the Enhanced GSM MAP Screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSM MAP screening feature.

The opname parameter value must be no more than 8 alphanumeric characters.

The word none cannot be used as a value for the opname parameter.

The dfltact=atierr parameter cannot be specified unless the value of the operation code (opcode) referenced by the opname parameter value is 71. The atierr option is only valid for ATI MAP operation codes; opcode=71 signifies an ATI MAP operation code.

The value specified for the opcode parameter cannot already exist in the GSM MAP operation code table.

The value specified for the opname parameter cannot already be used in the GSM MAP operation code table.

The pc/pca/pci/pcn/pcn24 and ssn values must be shown in the rtrv-map output, or else the force=yes parameter must be specified. If the pc/pca/pci/pcn/pcn24 and ssn values are not shown in the rtrv-map output, and a new mated application is to be added, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required mDatabaseated application with the pc/pca/pci/pcn/pcn24 and ssn values:

The force=yes parameter can be specified only with the pc/pca/pci/pcn/pcn24 and ssn parameters.

The dfltact=forward, dfltact=duplicate, or dfltact=dupdisc parameters can be specified only with the pc/pca/pci/pcn/pcn24 and ssn parameters. If the pc/pca/pci/pcn/pcn24 and ssn parameters are specified, the dfltact=forward, dfltact=duplicate, or dfltact=dupdisc parameters must be specified.

The pc/pca/pci/pcn/pcn24 and ssn parameters must be specified together.

The pc/pca/pci/pcn/pcn24 parameter values must be the DPC of a route and a proxy point code cannot be assigned to the point code. The pc/pca parameter value must be a full point code. The pc/pca parameter value can be a member of a cluster point code when that cluster point code is the DPC of a route. This can be verified with the rtrv-rte command. If the pc/pca/pci/pcn/pcn24 value is not shown in the rtrv-rte as the DPC of a route, go to the “Adding a Route Containing an SS7 DPC” procedure in Database Administration - SS7 User's Guide and add a new route containing the pc/pca/pci/pcn/pcn24 value. To verify whether or not a proxy point code is assigned to the pc/pca/pci/pcn/pcn24 value, enter the rtrv-dstn command with the point code value. If a proxy point code is assigned to the point code, choose another point code.

This examples used in this procedure are based on the examples shown in Table 5-5.

Table 5-5 Example GSM MAP Screening Operation Code Configuration Table

OPCODE OPNAME DFLTACT PC/PCA/PCI/ PCN/PCN24 SSN MAPSET

100

pass100

pass

N/A

N/A

N/A

150

discard1

discard

N/A

N/A

N/A

71

ati

atierr

N/A

N/A

N/A

25

route25

route

N/A

N/A

N/A

139

fwd139

forward

3-159-7

128

dflt

187

dup187

duplicate

11519

79

10

93

dd93

dupdisc

5-25-3

200

20

36

for1

forward

002-002-002

10

25

*

star

pass

N/A

N/A

N/A
  1. Verify that the GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893013201

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
GSM Map Screening (GMS)   893013201  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 GSMMAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSMMAP screening feature.

    Note:

    If the opcode=* or the pc/pca parameters are not being used in this procedure, continue the procedure with 3.
  2. Verify that the Enhanced GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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 Enhanced GSMMAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSMMAP screening feature.

  3. Display the GSMMAP screening operation codes in the database using the rtrv-gsms-opcode command.
    This is an example of the possible output. 
    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   RI  TT

OPCODE  OPNAME    DFLTACT    PCI          SSN   RI  TT

OPCODE  OPNAME    DFLTACT    PCN          SSN   RI  TT

OPCODE  OPNAME    DFLTACT    PCN24        SSN   RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 50     pass50    pass

GSMMS OPCODE Table (2 of 257) is 1% full

    If the Flexible GTTLoad Sharing feature is enabled, the MAPSET field is shown in the rtrv-gsms-opcode output. This is an example of the possible output 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT    PCI          SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT    PCN          SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT    PCN24        SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 50     pass50    pass

GSMMS OPCODE Table (2 of 257) is 1% full
  4. Perform one of these actions.
    • If the dfltact parameter value will be either pass, discard, route, or atierr, continue the procedure with 9.
    • If the dfltact parameter value will be either forward, duplicate, or dupdisc, perform one of these actions.
      • To use a point code and a MAP set from the mated application table, and MAP sets are not shown in the rtrv-gsms-opcode output in 3 , the Flexible GTT Load Sharing Feature must be enabled. Perform the “Activating the Flexible GTTLoad Sharing Feature” procedure in Database Administration - GTT User's Guide and enable the Flexible GTTLoad Sharing feature. After enabling the Flexible GTTLoad Sharing feature, continue the procedure with 7.
      • To use a point code and a MAP set from the mated application table, and MAP sets are shown in the rtrv-gsms-opcode output in 3 , continue the procedure with 7.
      • To use a point code in the mated application table, but without using a MAP set, and MAP sets are not shown in the rtrv-gsms-opcode output in 3 , skip continue the procedure with 7.
      • To use a point code that is not in the mated application table, the force=yes parameter must be specified with the ent-gsms-opcode command. A proxy point code cannot be assigned to this point code. If the Flexible GTT Load Sharing feature is enabled, the force=yes parameter can be used only if the default MAP set is assigned to the GSM OPCODE entry. Continue the procedure with 5.
  5. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   001-207-000   ----------- no  --- --------------   --------------   SS7
   001-001-001   ----------- no  --- --------------   --------------   SS7
   001-001-002   ----------- no  --- --------------   --------------   SS7
   001-005-000   ----------- no  --- --------------   --------------   SS7
   001-007-000   ----------- no  --- --------------   --------------   SS7
   008-012-003   ----------- no  --- --------------   --------------   SS7
   003-002-004   ----------- no  --- --------------   --------------   SS7
   009-002-003   ----------- no  --- --------------   --------------   SS7
   010-020-005   ----------- no  --- --------------   --------------   SS7

   DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
   1-207-0       ----------- no  --- --------------   --------------   SS7
   0-015-0       ----------- no  --- --------------   --------------   SS7
   0-017-0       ----------- no  --- --------------   --------------   SS7
   1-011-1       ----------- no  --- --------------   --------------   SS7
   1-011-2       ----------- no  --- --------------   --------------   SS7

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 9.

  6. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   010-020-005   ----------- no  --- --------------   --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   009-002-003  ---- no      50     on    20       no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the adjacent point code is not shown in the rtrv-dstn command output, the following output is displayed. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

No destinations meeting the requested criteria were found

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If the point code is not shown in the rtrv-dstn output, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the adjacent point code to the destination point code table.

    After the new point code has been added, perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 9.

  7. The point code and subsystem number being assigned to the GSMOPCODE must be in the mated application table.
    Enter the rtrv-map command with the pc/pca/pci/pcn/pcn24 and ssn values that will be specified with the ent-gsms-opcode command in 9 .

    If the Flexible GTT Load Sharing feature is not enabled, for this example, enter these commands.

    rtrv-map:pci=3-159-7:ssn=128

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
3-159-7                   128 10  SOL *N  *N  GRP01    OFF

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pcn=11519:ssn=79

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCN          Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
11519                      79 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pci=5-25-3:ssn=200

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
5-025-3                   200 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pca=002-002-002:ssn=10

    This is an example of the possible output. 

    
rlghncxa03w 06-10-25 09:42:31  GMT  EAGLE5 36.0.0
E2452 Cmd Rej: Remote point code does not exist in MAP table

    If the Flexible GTT Load Sharing feature is enabled:

    • The mapset parameter must be specified with the ent-gsms-opcode command in 9 .
    • The point code and subsystem contained in the GSM OPCODE entry must be in the MAP set assigned to the GSM OPCODE entry.

    For this example, enter these commands.

    rtrv-map:pci=3-159-7:ssn=128

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=DFLT
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
3-159-7                   128 10  SOL *N  *N  GRP01    OFF

MAP TABLE IS (20 of 36000) 1 % FULL

    rtrv-map:pcn=11519:ssn=79

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=10
PCN          Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
11519                      79 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 36000) 1 % FULL

    rtrv-map:pci=5-25-3:ssn=200

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=20
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
5-025-3                   200 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 36000) 1 % FULL

    rtrv-map:pca=002-002-002:ssn=10

    This is an example of the possible output. 

    
rlghncxa03w 06-10-25 09:42:31  GMT  EAGLE5 36.0.0
E2452 Cmd Rej: Remote point code does not exist in MAP table

    If the point code and subsystem number is not shown in the rtrv-map output, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required point code and subsystem number to the mated application table.

  8. The point code specified with the ent-gsms-opcode command must be the DPC of a route.
    If the point code specified with the ent-gsms-opcode command is an ANSI point code, the point code can be a member of a cluster point code when that cluster point code is the DPC of a route.

    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the ent-gsms-opcode command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

    rtrv-rte:dpci=3-159-7

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
3-159-7    12111            240-111-111 ls100001   10    1-234-5
                                        ls100002   10    1-234-6
                                        ls100003   20    1-234-7
                                        ls100004   30    1-234-1
                                        ls100005   40    1-234-2
                                        ls100006   50    1-234-3
                                            RTX:No  CLLI=idp1

    rtrv-rte:dpcn=11519

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCN             ALIASA         ALIASI  LSN        RC    APC
11519            011-222-111    0-001-1 ls200001   10    11111
                                        ls200002   10    11112
                                        ls200003   20    11113
                                        ls200004   30    11114
                                        ls200005   40    11115
                                        ls200006   50    11116
                                            RTX:No  CLLI=ndp1

    rtrv-rte:dpci=5-25-3

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
5-25-3     07659            240-039-150 ls100001   10    5-25-3
                                        ls100002   10    3-250-6
                                        ls100003   20    7-34-7
                                        ls100004   30    6-98-1
                                        ls100005   40    3-142-2
                                        ls100006   50    1-178-3
                                            RTX:No  CLLI=idp1

    rtrv-rte:dpca=002-002-002

    
rlghncxa03w 06-10-25 09:42:31  GMT  EAGLE5 36.0.0
DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
002-002-002 ---------- --------------   lsn1       10    002-002-002
                                            RTX:No  CLLI=-----------

    If the point code is not shown in the rtrv-rte output, or, if the point code is an ANSI point code, the point code is not a member of a cluster point code when that cluster point code is the DPC of a route, go to the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database.

  9. Add the new GSMMAP screening operation codes to the database with the ent-gsms-opcode command.
    For this example, enter these commands:

    ent-gsms-opcode:opcode=100:opname=pass100:dfltact=pass

    ent-gsms-opcode:opcode=150:opname=discard1:dfltact=discard

    ent-gsms-opcode:opcode=71:opname=ati:dfltact=atierr

    ent-gsms-opcode:opcode=25:opname=route25:dfltact=route

    ent-gsms-opcode:opcode=139:opname=fwd139:dfltact=forward :pci=3-159-7:ssn=128:mapset=dflt

    ent-gsms-opcode:opcode=187:opname=dup187:dfltact=duplicate :pcn=11519:ssn=79:mapset=10

    ent-gsms-opcode:opcode=93:opname=dd93:dfltact=dupdisc :pci=5-25-3:ssn=200:mapset=20

    ent-gsms-opcode:opcode=36:opname=for1:dfltact=forward :pca=002-002-002:ssn=10:mapset=25

    ent-gsms-opcode:opcode=*:opname=star1:dfltact=pass

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
ENT-GSMS-OPCODE: MASP A - COMPLTD
    These are the rules that apply to adding a GSM MAP screening operation code.
    1. The word "none" cannot be used as a value for the opname parameter.
    2. The pc/pca/pci/pcn/pcn24 value must be shown in the rtrv-rte output on 8 as the DPC of a route. The pc/pca value must be a full point code value. The pc/pca value can be a member of a cluster point code when that cluster point code is the DPC of a route. A proxy point code cannot be assigned to the point code.
    3. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both.
    4. To specify the opcode=* or pc/pca parameters, the Enhanced GSM MAP Screening feature must be enabled and on.
    5. If the Flexible GTT Load Sharing feature is not enabled, shown on 3, the mapset parameter cannot be used. The pc/pca/pci/pcn/pcn24 and ssn values must be shown in the rtrv-map output on 7, otherwise, the force=yes parameter must be specified.
    6. If the Flexible GTT Load Sharing feature is enabled, shown on 3, the mapset parameter must be used. The force=yes parameter can be used only if the MAP set assigned to the GSM OPCODE entry is the default MAP set. If the MAP set assigned to the GSM OPCODE entry is a MAP set other than the default MAP set, the force=yes parameter cannot be used. The point code and subsystem contained in the GSM OPCODE entry must be in the MAP set assigned to the GSM OPCODE entry. If the default MAP set is assigned to the GSM OPCODE entry and the force=yes parameter is not specified, the point code and subsystem contained in the GSM OPCODE entry must be in the default MAP set.
    7. If the ri or tt parameters are not specified, the default values for these parameters are assigned to the GSM OPCODE entry. The default values for these parameters are:
      • ri – ssn
      • tt – no value is specified. A dash is shown in the TT column of the rtrv-gsms-opcode output.
    8. If the ri=ssn parameter is specified, a numerical value must be specified for the ssn parameter.
  10. Verify the changes using the rtrv-gsms-opcode command and specifying the opcode parameter value used in 9 .
    For this example, enter these commands.

    rtrv-gsms-opcode:opcode=025

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
 25     route25   route

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=071

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
 71     ati       atierr

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=093

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0
OPCODE  OPNAME    DFLTACT    PCI          SSN   MAPSET RI  TT
 93     dd93      dupdc      5-25-3       200   20     ssn -

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=100

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
 100    pass100   pass

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=139

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0
OPCODE  OPNAME    DFLTACT    PCI          SSN   MAPSET RI  TT
 139    fwd139    fwd        3-159-7      128   DFLT   ssn -

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=150

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
 150    discard1  disc

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=187

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0
OPCODE  OPNAME    DFLTACT    PCN          SSN   MAPSET RI  TT
 187    dup187    dupl       11519        79    10     ssn -

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=36

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0
OPCODE  OPNAME    DFLTACT    PCA          SSN   MAPSET RI  TT
 36     for1      fwd        002-002-002  10    25     ssn -

GSMMS OPCODE Table (11 of 257) is 4% full

    rtrv-gsms-opcode:opcode=*

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
 *      star      pass

GSMMS OPCODE Table (11 of 257) is 4% full
  11. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-10 Adding a GSM MAP Screening Operation Code



Sheet 1 of 7



Sheet 2 of 7



Sheet 3 of 7



Sheet 4 of 7



Sheet 5 of 7



Sheet 6 of 7



Sheet 7 of 7

Removing a GSM MAP Screening Operation Code

Use this procedure to remove GSM MAP screening operation codes and the default screening action for that operation code using the dlt-gsms-opcode command.

The dlt-gsms-opcode command uses only one parameter, opname. The value for the opname parameter is the user-defined name for the operation code shown in the rtrv-gsms-opcode command output.

The opname value being removed cannot be referenced by any GSM MAP screening entries (shown in the rtrv-gsmmap-scrn command output). Use the Removing a GSM MAP Screening Entry procedure to remove any GSM MAP screening entries that reference the opname name value being removed from the database.

  1. Display the GSMMAP screening opcodes in the database using the rtrv-gsms-opcode command.

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   RI  TT
 36     for1      fwd        002-002-002  10    gt  40

OPCODE  OPNAME    DFLTACT    PCI          SSN   RI  TT
 93     dd93      dupdc      5-25-3       200   ssn 10
 139    fwd139    fwd        3-159-7      128   ssn -

OPCODE  OPNAME    DFLTACT    PCN          SSN   RI  TT
 187    dup187    dupl       11519        79    gt  50

OPCODE  OPNAME    DFLTACT    PCN24        SSN   RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 100    pass100   pass
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (11 of 257) is 4% full
  2. Display the GSMMAP screening entries that reference the opname value being removed from the database using the rtrv-gsmmap-scrn command specifying the opname parameter with the opname value being removed from the database. For this example, enter this command.

    rtrv-gsmmap-scrn:opname=sri

    This is an example of the possible output if the rtrv-gsmmap-scrn output contains no entries that reference the opname value being removed. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: sri
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    This is an example of the possible output if the rtrv-gsmmap-scrn output contains entries that reference the opname value being removed.

    rtrv-gsmmap-scrn:opname=sri 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR
919462000000005 1  0   none  pass  sri1

Range CgPA Entries for OPNAME: sri
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR
919461888888888 919461900000000 4  1   all   pass  sri2
919462000000000 919463000000000 *  *   all   disc  sri3

GSM Map Screening table is (1500 of 4000) 38% full

    If the GSM MAP screening entry in this step contains any CGPA entries, go to the Removing a GSM MAP Screening Entry procedure to remove the CGPA entries shown in this step.

  3. Remove the GSMMAP opname value from the database using the dlt-gsms-opcode command.
    For this example, enter this command.

    dlt-gsms-opcode:opname=sri

    When this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-07 00:29:31 GMT EAGLE5 36.0.0
DLT-GSMS-OPCODE: MASP A - COMPLTD
  4. Verify the changes using the rtrv-gsms-opcode command with the opname parameter value specified in step 3. For this example, enter this command.

    rtrv-gsms-opcode:opname=sri

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
E3892 Cmd Rej: OPNAME does not exist in the database
  5. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-11 Removing a GSM MAP Screening Operation Code



Changing a GSM MAP Screening Operation Code

Use this procedure to change the attributes of the GSM MAP screening operation codes using the chg-gsms-opcode command. The procedure allows you to change the default screening action and the operation-code name for a specific operation code. The chg-gsms-opcode command uses these parameters.

:opname – The user-defined name for the operation code shown in the rtrv-gsms-opcode command output.

:nopname – The new user-defined name for the operation code.

:ndfltact – The new default screening action.

  • pass – Route the message as normal to the destination.

  • discard – The MSU is to be discarded.

  • atierr – An ATI (Any Time Interrogation) reject message is generated. This option is only valid for ATI MAP operation codes.

  • route – Route the message as normal to the original destination node.

  • forward – Route the original message to the forward node. The original message is not sent to the original node. If, however, the forwarded node is not available for routing then the MSU is routed to the original node.

  • duplicate – Route the message as normal to the original destination and route a copy of the original message to the duplicate node.

  • dupdisc – Duplicate and discard – Route the original message to the duplicate node. The original message is not sent to the original node.

:npc/npca/npci/npcn/npcn24 – The new ANSI point code (npc/npca), new ITU-I point code or ITU-I spare point code (npci), new 14-bit ITU-N point code or 14-bit ITU-N spare point code (npcn), or new 24-bit ITU-N point code (npcn24) of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both. The npc/npca parameters can be specified only if the Enhanced GSM MAP Screening feature is enabled and on.

:nssn – The new subsystem number of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions

:force – The mated application override. Is the GSM MAP screening operation code to be entered without a mated application in the database (yes or no)?

:nmapset – The new MAP set ID, shown in the rtrv-map command. This parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform the “Activating the Flexible GTT Load Sharing Feature” procedure in Database Administration - GTT User's Guide.

If the Flexible GTT Load Sharing feature is not enabled:

  • The nmapset parameter cannot be used.

  • The npc/npca/npci/npcn/npcn24 and nssn values must be shown in the rtrv-map output, or else the force=yes parameter must be specified.

If the Flexible GTT Load Sharing feature is enabled:

  • If the current dfltact parameter value is either pass, route, discard, or atierr, and the dfltact parameter value is changed to either forward, duplicate, or dupdisc, the GSM OPCODE entry must be assigned to a MAP set with the nmapset=dflt parameter (to assign the GSM OPCODE entry to the default MAP set), or with the nmapset=<numbered MAP set ID> parameter (to assign the GSM OPCODE entry to a MAP set other the default MAP set).

  • If the default MAP set will be assigned to the GSM OPCODE entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in the default MAP set in the rtrv-map output. If the npc/npca/npci/npcn /npcn24 or nssn values are not shown in the default MAP set in the rtrv-map output, the force=yes parameter must be specified.

  • If a MAP set other than the default MAP set will be assigned to the GSM OPCODE entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in that MAP set in the rtrv-map output. The force=yes parameter cannot be specified with the chg-gsms-opcode command.

  • If the point code and subsystem values are not being changed, the nmapset parameter does not have to be specified unless the MAP set ID assigned to the GSM OPCODE entry is being changed. The new MAP set must contain the point code and subsystem values in the GSM OPCODE entry.

:nri - The new routing indicator parameter. This parameter specifies whether a subsequent global title translation is required. This parameter has two values.
  • gt - subsequent global title translation is required.
  • ssn - subsequent global title translation is not required.

:ntt - the new translation type that will be assigned to the GSM OPCODE entry. The values for this parameter are 0 to 255, or the value none which removes and existing translation type that is assigned to the GSM OPCODE entry.

The nopname parameter value must be no more than 8 alphanumeric characters.

The reserved word none cannot be used as a value for the nopname parameter.

The ndfltact=atierr parameter cannot be specified unless the value of the operation code (opcode) referenced by the opname parameter value is 71. The atierr option is only valid for ATI MAP operation codes; opcode=71 signifies an ATI MAP operation code.

The npc/npca/npci/npcn/npcn24 and nssn values must be shown in the rtrv-map output, or else the force=yes parameter must be specified. If the npc/npca/npci/npcn/npcn24 and nssn values are not shown in the rtrv-map output, and a new mated application is to be added, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required mated application with the npc/npca/npci/npcn/npcn24 and nssn values.

The force=yes parameter can be specified only with the npc/npca/npci/ npcn/npcn24 and nssn parameters.

The ndfltact=forward, ndfltact=duplicate, or ndfltact=dupdisc parameters can be specified only with the npc/npca/npci/npcn/npcn24 and nssn parameters. If the npc/npca/npci/npcn/npcn24 and nssn parameters are specified, the ndfltact=forward, ndfltact=duplicate, or ndfltact=dupdisc parameters must be specified.

The npc/npca/npci/npcn/npcn24 and nssn parameters must be specified together.

The npc/npca/npci/npcn/npcn24 parameter values must be the DPC of a route or a member of a cluster route, and a proxy point code cannot be assigned to the point code. This can be verified with the rtrv-rte command. If the npc/npca/npci/npcn/npcn24 value is not shown in the rtrv-rte as the DPC of a route, go to the “Adding a Route Containing an SS7 DPC” procedure in Database Administration - SS7 User's Guide and add a new route containing the npc/npca/npci/npcn/npcn24 value. To verify whether or not a proxy point code is assigned to the npc/npca/npci/npcn/npcn24 value, enter the rtrv-dstn command with the point code value. If a proxy point code is assigned to the point code, choose another point code.

  1. Display the GSM MAP screening operation codes in the database using the rtrv-gsms-opcode command.

    If the Flexible GTT Load Sharing feature is not enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN  RI  TT
 36     for1      fwd        002-002-002  10   gt  10

OPCODE  OPNAME     DFLTACT   PCI          SSN  RI  TT
 93     dd93       dupdc     5-025-3      200  ssn 40
 139    fwd139     fwd       3-159-7      128  ssn -

OPCODE  OPNAME     DFLTACT   PCN          SSN  RI  TT
 187    dup187     dupl      11519        79   gt  50

OPCODE  OPNAME     DFLTACT   PCN24        SSN

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    If the Flexible GTT Load Sharing feature is enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   MAPSET RI  TT
 36     for1      fwd        002-002-002  10    25     gt  10

OPCODE  OPNAME     DFLTACT   PCI          SSN   MAPSET RI  TT
 93     dd93       dupdc     5-025-3      200   20     ssn 40
 139    fwd139     fwd       3-159-7      128   DFLT   ssn -

OPCODE  OPNAME     DFLTACT   PCN          SSN   MAPSET RI  TT
 187    dup187     dupl      11519        79    10     gt  50

OPCODE  OPNAME     DFLTACT   PCN24        SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    Note:

    If the default action parameter value will be changed to either pass, discard, route, or atierr, or the npc/npca/npci/npcn/npcn24 and nssn parameters are not to be specified, continue the procedure with 8.

    Note:

    If the npc/npca parameters are not being used in this procedure, or if the rtrv-gsms-opcode output in 1 shows ANSI point code values (pc/pca parameter values) or the opcode=* parameter value, continue the procedure with 3.
  2. Verify that the Enhanced GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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 Enhanced GSM MAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSM MAP screening feature.

  3. Perform one of these actions.
    • If the ndfltact parameter value will be either pass, discard, route, or atierr, continue the procedure with 8.
    • If the point code is not being changed, continue the procedure with 8. If the point code and subsystem values are not being changed, and the Flexible GTT Load Sharing feature is enabled, the nmapset parameter does not have to be specified unless the MAP set ID assigned to the GSM OPCODE entry is being changed. The new MAP set must contain the point code and subsystem values in the GSM OPCODE entry.
    • If the ndfltact parameter value will be either forward, duplicate, or dupdisc, perform one of these actions.
      • To use a point code and a MAP set from the mated application table, and MAP sets are not shown in the rtrv-gsms-opcode output in 1 , the Flexible GTT Load Sharing Feature must be enabled. Perform the “Activating the Flexible GTT Load Sharing Feature” procedure in the Database Administration - GTT User's Guide and enable the Flexible GTT Load Sharing feature. After enabling the Flexible GTT Load Sharing feature, continue the procedure with 6.
      • To use a point code and a MAP set from the mated application table, and MAP sets are shown in the rtrv-gsms-opcode output in 1 , skip steps 4 and 5 and continue the procedure with 6.
      • To use a point code in the mated application table, but without using a MAP set, and MAP sets are not shown in the rtrv-gsms-opcode output in 1 , continue the procedure with 6.
      • To use a point code that is not in the mated application table, the force=yes parameter must be specified with the chg-gsms-opcode command. A proxy point code cannot be assigned to this point code. If the Flexible GTT Load Sharing feature is enabled, the force=yes parameter can be used only if the default MAP set is assigned to the GSM OPCODE entry. Continue the procedure with 4 .
  4. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   001-207-000   ----------- no  --- --------------   --------------   SS7
   001-001-001   ----------- no  --- --------------   --------------   SS7
   001-001-002   ----------- no  --- --------------   --------------   SS7
   001-005-000   ----------- no  --- --------------   --------------   SS7
   001-007-000   ----------- no  --- --------------   --------------   SS7
   008-012-003   ----------- no  --- --------------   --------------   SS7
   003-002-004   ----------- no  --- --------------   --------------   SS7
   009-002-003   ----------- no  --- --------------   --------------   SS7
   010-020-005   ----------- no  --- --------------   --------------   SS7

   DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
   1-207-0       ----------- no  --- --------------   --------------   SS7
   0-015-0       ----------- no  --- --------------   --------------   SS7
   0-017-0       ----------- no  --- --------------   --------------   SS7
   1-011-1       ----------- no  --- --------------   --------------   SS7
   1-011-2       ----------- no  --- --------------   --------------   SS7

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in the Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 8 .

  5. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   010-020-005   ----------- no  --- --------------   --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   009-002-003  ---- no      50     on    20       no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the adjacent point code is not shown in the rtrv-dstn command output, the following output is displayed. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

No destinations meeting the requested criteria were found

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If the point code is not shown in the rtrv-dstn output, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the adjacent point code to the destination point code table.

    After the new point code has been added, perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 8 .

  6. The point code and subsystem number being assigned to the GSM operations code must be in the mated application table.
    Enter the rtrv-map command with the npc/npca/npci/npcn/npcn24 and nssn values that will be specified with the chg-gsms-opcode command in 8 .

    If the Flexible GTT Load Sharing feature is not enabled, for this example, enter these commands.

    For this example, enter this command.

    rtrv-map:pci=4-038-1:ssn=50

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
4-038-1                    50 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    Note:

    If the point code and subsystem number is not shown in the rtrv-map output, and is not added to the database in one of these procedures, the force=yes parameter must be specified with the chg-gsms-opcode command in 8 .

    If the Flexible GTT Load Sharing feature is enabled and the current dfltact parameter value is either pass, route, discard, or atierr, and the dfltact parameter value is changed to either forward, duplicate, or dupdisc, the GSM OPCODE entry must be assigned to a MAP set with the nmapset=dflt parameter (to assign the GSM OPCODE entry to the default MAP set), or with the nmapset=<numbered MAP set ID> parameter (to assign the GSM OPCODE entry to a MAP set other the default MAP set).

  7. The point code specified with the chg-gsms-opcode command must be the DPC of a route.
    If the point code specified with the chg-gsms-opcode command is an ANSI point code, the point code can be a member of a cluster point code when that cluster point code is the DPC of a route.

    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the chg-gsms-opcode command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

    rtrv-rte:dpci=4-038-1

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
4-038-1    12111            240-111-111 ls300001   10    4-038-1
                                        ls300002   10    2-066-7
                                        ls300003   20    5-087-4
                                            RTX:No  CLLI=idp1

    If the point code is not shown in the rtrv-rte output, if the point code is an ANSI point code, the point code is not a member of a cluster point code when that cluster point code is the DPC of a route, go to the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database.

  8. Change the attributes of GSMMAP screening operation codes in the database with the chg-gsms-opcode command.
    For this example, enter these commands:

    chg-gsms-opcode:opname=pass100:ndfltact=discard

    chg-gsms-opcode:opname=discard1:nopname=pass1:ndfltact=pass

    chg-gsms-opcode:opname=sri:nopname=irs

    chg-gsms-opcode:opname=fwd139:nopname=fwd1000:npci=4-038-1:nssn=50 :nmapset=18:nri=gt:ntt=60

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
GSM Map Op-Code Table is (8 of 256) 3% full
CHG-GSMS-OPCODE: MASP A - COMPLTD
    These are the rules that apply to changing a GSM MAP screening operation code.
    1. The word "none" cannot be used as a value for the opname or nopname parameters.
    2. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both.
    3. If the point code and subsystem number values are not being changed, the npc/npca/npci/npcn/npcn24 and nssn parameters must be specified with the current values for these parameters.
    4. The npc/npca/npci/npcn/npcn24 value must be shown in the rtrv-rte output on 7 as the DPC of a route. The npc/npca value must be a full point code value. The npc/npca value can be a member of a cluster point code when that cluster point code is the DPC of a route. A proxy point code cannot be assigned to the point code.
    5. If the Flexible GTT Load Sharing feature is not enabled, shown on 1, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in the rtrv-map output on 6. If the npc/npca/npci/npcn/npcn24 or nssn values are not shown in the rtrv-map output, the force=yes parameter must be specified.
    6. If the Flexible GTT Load Sharing feature is enabled, shown on 1, and the current dfltact parameter value is either pass, route, discard, or atierr, and the dfltact parameter value is changed to either forward, duplicate, or dupdisc, the GSM OPCODE entry must be assigned to a MAP set with the nmapset=dflt parameter (to assign the GSM OPCODE entry to the default MAP set), or with the nmapset=<numbered MAP set ID> parameter (to assign the GSM OPCODE entry to a MAP set other the default MAP set).
    7. If the Flexible GTT Load Sharing feature is enabled, shown on 1, and the default MAP set will be assigned to the GSM OPCODE entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in the default MAP set in the rtrv-map output on 6. If the npc/npca/npci/npcn/npcn24 or nssn values are not shown in the default MAP set in the rtrv-map output, the force=yes parameter must be specified.
    8. If the Flexible GTT Load Sharing feature is enabled, shown on 1, and a MAP set other than the default MAP set will be assigned to the GSM OPCODE entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in that MAP set in the rtrv-map output on 6.
    9. To specify the npc/npca parameters, the Enhanced GSM MAP Screening feature must be enabled and turned on.
    10. If only the point code or subsystem number value is being changed, the point code or subsystem number value being changed must be specified with the new value for the parameter being changed. The current value for the point code or subsystem number parameter not being changed must be specified. The ndfltact parameter does not have to be specified. For example, if the current point code is pca=002-002-002 and the subsystem number is 50, and the point code is being changed to pca=003-003-003 and the subsystem number is not changing, the npca parameter value would be the new point code value (003-003-003) and the nssn parameter value would be the current value (50).
    11. If the Flexible GTT Load Sharing feature is enabled, shown on 1, and the point code and subsystem values are not being changed, the nmapset parameter does not have to be specified unless the MAP set ID assigned to the GSM OPCODE entry is being changed. The new MAP set must contain the point code and subsystem values in the GSM OPCODE entry.
    12. If an optional parameter is not specified, the value for that parameter is not changed.
    13. The value none for the tt parameter removes the existing tt parameter value that is assigned to the GSM OPCODE entry. A dash is shown in the TT column of the rtrv-gsms-opcode output when the tt value is removed.
    14. If, when the chg-gsms-opcode command is completed, the ri parameter value is ssn, then a numerical value must be assigned to the ssn parameter.
  9. Verify the changes using the rtrv-gsms-opcode command with the opname parameter value specified in 8 .
    If the opname parameter value was changed in 8 , the new opname parameter value should be specified with the rtrv-gsms-opcode command. For this example, enter these commands.

    rtrv-gsms-opcode:opname=pass100

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
100     pass100   discard

GSMMS OPCODE Table (10 of 257) is 4% full

    rtrv-gsms-opcode:opname=pass1

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
150     pass1     pass

GSMMS OPCODE Table (10 of 257) is 4% full

    rtrv-gsms-opcode:opname=irs

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
OPCODE  OPNAME    DFLTACT
22      irs       disc

GSMMS OPCODE Table (10 of 257) is 4% full

    rtrv-gsms-opcode:opname=fwd1000

    This is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0
OPCODE  OPNAME    DFLTACT    PCI          SSN   MAPSET RI  TT
139     fwd1000   fwd        4-38-1       50    18     gt  60

GSMMS OPCODE Table (10 of 257) is 4% full
  10. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-12 Changing a GSM MAP Screening Operation Code



Sheet 1 of 7



Sheet 2 of 7



Sheet 3 of 7



Sheet 4 of 7



Sheet 5 of 7



Sheet 6 of 7



Sheet 7 of 7

Adding a GSM MAP Screening Entry

Use this procedure to provision the GSM MAP screening entries that filter or allow TCAP messages for certain MAP operation codes in the database using the ent-gsmmap-scrn command. The messages are filtered or allowed based on the origination addresses (saddr/eaddr), numbering plan value (npv), nature of address indicator value (naiv), MAP opnames (opname), and forbidden (forbid) parameters.

The ent-gsmmap-scrn command uses these parameters.

:saddr – The origination address (1 - 15 decimal digits, 1 - 15 hex digits, or *) for a single entry or the starting origination address for a range of entries of the CGPA/CDPA entry to be screened.

:eaddr – The ending origination address (1 - 15 decimal digits or 1 - 15 hex digits) for a range of entries of the CGPA/CDPA entry to be screened.

:action – The screening action to take if a message is forbidden as defined by the forbid parameter. One of these actions can be assigned.

  • pass – Route the message as normal to the destination.
  • discard – The MSU is to be discarded.
  • atierr – An ATI (Any Time Interrogation) reject message is generated. This option is only valid for ATIMAP operation codes.
  • route – Route the message as normal to the original destination node.
  • forward – Route the original message to the forward node. The original message is not sent to the original node. If, however, the forwarded node is not available for routing then the MSU is routed to the original node.
  • duplicate – Route the message as normal to the original destination and route a copy of the original message to the duplicate node.
  • dupdisc – Duplicate and discard – Route the original message to the duplicate node. The original message is not sent to the original node.

:pc/pca/pci/pcn/pcn24 – The ANSI point code (pc/pca), ITU-I point code or ITU-I spare point code (pci), 14-bit ITU-N point code or 14-bit ITU-N spare point code (pcn), or 24-bit ITU-N point code (pcn24) of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both. To specify the pc/pca parameters, the Enhanced GSMMAP Screening feature must be enabled and on.

:ssn – The subsystem number of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The values for this parameter are 2 to 255, or the value none. The default value for this parameter is none.

:force – The mated application override. Is the GSMMAP screening operation code to be entered without a mated application in the database (yes or no)?

:forbid – The forbidden parameter value. If a forbidden parameter is detected, the message is rejected by the action defined by the action parameter. One of four forbidden parameter values can be specified.

  • all – All parameters are forbidden. Take the specified screening action defined by the action parameter for incoming messages that contain the entered address and operation code combination.
  • none – No parameters are forbidden. Take the specified screening action defined by the action parameter for incoming messages that contain the entered address and operation code combination.
  • state – Take the specified screening action defined by the action parameter for incoming messages that contain state as the forbidden parameter for the entered address and operation code combination.
  • location – Take the specified screening action defined by the action parameter for incoming messages that contain location as the forbidden parameter for the entered address and operation code combination.

Note:

The state and location values are valid only for GSMATI messages.

:naiv – The nature of address value (0 - 15 or *).

:npv – The numbering plan value (0 - 127 or *).

:opname – The user-defined name for the operation code. The opname value references the operation code (opcode) shown in the rtrv-gsms-opcode command. GSMMAP screening is performed on the specified address or addresses for the referenced operation code.

:cgsr – The CGPA screening reference name consisting of 1 alphabetic character and 3 optional alphanumeric characters.

:cdsr – The CDPA screening reference name consisting of 1 alphabetic character and 3 optional alphanumeric characters.

:mapset – The MAP set ID, shown in the rtrv-map command. This parameter can be specified only if the Flexible GTTLoad Sharing feature is enabled. The status of the Flexible GTTLoad Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTTLoad Sharing feature, perform the “Activating the Flexible GTTLoad Sharing Feature” procedure in Database Administration - GTT User's Guide.

:ri - The routing indicator parameter. This parameter specifies whether a subsequent global title translation is required. This parameter has two values.
  • gt - subsequent global title translation is required.
  • ssn - subsequent global title translation is not required. This is the default value for the ri parameter.

:tt - the translation type that will be assigned to the GSM MAP screening entry. This parameter specifies the value that the translation type for the CdPA is set to as a result of GSM MAP screening. The values for this parameter are 0 to 255, or the value none which specifies that no translation type will be assigned to the GSM MAP screening entry.

Table 5-6 shows the parameter combinations that can be used in this procedure.

Table 5-6 Add GSM MAP Screening Entry Parameter Combinations

Entry Containing a Point Code and SSN (See Note 1) Enhanced GSM MAP Screening Feature Enabled and On Entry Without a Point Code and SSN (See Note 1) Enhanced GSM MAP Screening Feature Enabled and On Entry containing the Action ATIERR (See Note 1) Enhanced GSM MAP Screening Feature Enabled and On Entry Containing a Point Code and SSN (See Note 1) GSM MAP Screening Feature Enabled and On Only Entry Without a Point Code and SSN (See Note 1) GSM MAP Screening Feature Enabled and On Only Entry containing the Action ATIERR (See Note 1) GSM MAP Screening Feature Enabled and On Only

Mandatory Parameters

:opname = opname value (See Note 2)

:opname = opname value (See Note 2)

:opname = opname value containing opcode=71 (See Note 2)

:opname = opname value (See Note 2)

:opname = opname value (See Note 2)

:opname = opname value containing opcode=71 (See Note 2)

:cgsr = CGSR name (See Note 3)

:cgsr = CGSR

name (See Note 3)

:cgsr = CGSR

name (See Note 3)

:cgsr = CGSR name (See Note 3)

:cgsr = CGSR name (See Note 3)

:cgsr = CGSR name (See Note 3)

saddr = 0 - 15 decimal digits (See Notes 4, 5, and 6)

saddr = 0 - 15 decimal digits (See Notes 4, 5, and 6)

saddr = 0 - 15 decimal digits (See Notes 4, 5, and 6)

Optional Parameters

:saddr = 0 - 15 hex digits, or * (See Notes 4, 5, and 6)

:saddr = 0 - 15 hex digits, or * (See Notes 4, 5, and 6)

:saddr = 0 - 15 hex digits, or * (See Notes 4, 5, and 6)

:eaddr = 0 - 15

decimal digits (See Notes 4, 5, and 6)

:eaddr = 0 - 15

decimal digits (See Notes 4, 5, and 6)

:eaddr = 0 - 15

decimal digits (See Notes 4, 5, and 6)

:eaddr = 0 - 15 hex digits (See Notes 4, 5, 6, and 7)

:eaddr = 0 - 15 hex digits (See Notes 4, 5, 6, and 7)

:eaddr = 0 - 15 hex digits (See Notes 4, 5, 6, and 7)

:forbid = all

:forbid = all, none (See Note 15)

:forbid = state, location

:cdsr = CDSR name (See Note 3)

:cdsr = CDSR

name (See Note 3)

:cdsr = CDSR

name (See Note 3)

:action = forward, duplicate, dupdisc (See Note 9)

:action = pass, discard, route (See Note 15)

:action = atierr

:forbid = all

:forbid = all, none (See Note 15)

:forbid = state, location

:npv = 0 - 15, or * (See Note 8)

:npv = 0 - 15, or * (See Note 8)

:npv = 0 - 15, or * (See Note 8)

:action = forward, duplicate, dupdisc (See Note 9)

:action = pass, discard, route (See Note 15)

:action = atierr

:naiv = 0 - 127, or * (See Note 8)

:naiv = 0 - 127, or * (See Note 8)

:naiv = 0 - 127, or * (See Note 8)

:npv = 0 - 15, or * (See Note 8)

:npv = 0 - 15, or * (See Note 8)

:npv = 0 - 15, or * (See Note 8)

:pci/pcn/pcn24 = point code

value (See Notes 10, 11, 12, 13, and 14)

   

:naiv = 0 - 127, or * (See Note 8)

:naiv = 0 - 127, or * (See Note 8)

:naiv = 0 - 127, or * (See Note 8)

:ssn = 0 - 255, none (See Notes 13, 14, and 16)

:pc/pca/pci/pcn/

pcn24 = point code value (See Notes 10, 11, 12, 13, and 14)

   

:force=yes (See Notes 13 and 14)

:mapset= dflt or numbered MAP set

ID (See Notes 13 and 14)

:ssn = 0 - 255, none (See Notes 13, 14, and 16)

:ri = gt, ssn (See Note 16)

:force=yes (See Notes 13 and 14)

:tt = 0 - 255, none

:mapset = dflt or numbered MAP set ID (See Notes 13 and 14)

 
:ri = gt, ssn (See Note 16)
:tt = 0 - 255, none

Notes:

1. When a CGPA entry (cgsr parameter is specified without the cdsr parameter) is added to the GSM MAP Screening table, a default wild card entry is created for the CGPA entry, thus adding two entries to the GSM MAP Screening table. The default wild card CDPA entry is not shown in the rtrv-gsmmap-scrn output. As a result, the GSM MAP Screening table must have at least two free entries in order to provision a CGPA entry in the GSM MAP Screening table. When the first provisioned wildcard (*) CDPA entry is added to a CGPA entry, the number of entries in the GSM MAP Screening table, shown in the GSM MAP Screening command outputs, does not change.

2. The opname parameter value must be shown in either the rtrv-gsms-opcode or rtrv-gsmmap-scrn output.

3. The cgsr and cdsr parameter values consist of 1 alphabetic character and up to 3 optional alphanumeric characters. If the cdsr parameter is not specified, a CGPA entry with a default wild card CDPA entry is created in the GSM MAP Screening table (see Note 1). If the cdsr parameter is specified, a CDPA entry is created in the GSM MAP Screening table.

4. If a single entry is specified for the CGPA/CDPA (that is, the eaddr parameter is not specified) then the saddr/npv/naiv/opname parameter combination cannot exist in the GSM MAP Screening table.

5. If a range of entries is specified for the CGPA/CDPA (that is, the eaddr parameter is specified) then the saddr/eaddr/npv/naiv/opname parameter combination cannot exist in the GSM MAP Screening table or overlap with another range entry in the GSM MAP Screening table.

6. The eaddr parameter value must contain the same number of digits as the saddr parameter value. The eaddr parameter value must be greater than the saddr parameter value. The saddr parameter must be specified with the eaddr parameter.

7. The eaddr parameter cannot be specified with the saddr=* parameter.

8. If the Enhanced GSM MAP Screening feature is not enabled or off, and either the npv or naiv parameters are specified, both the npv and naiv parameters must be specified. If the asterisk (*) is specified for either the npv or naiv parameters, the asterisk must be specified for both the npv and naiv parameters. If numbers are specified for either the npv or naiv parameters, numbers must be specified for both the npv and naiv parameters.

9. If the action parameter values are either forward, duplicate, or dupdisc, the point code and ssn parameters must be specified with the ent-gsmmap-scrn command. A proxy point code cannot be assigned to this point code.

10. The point code value must be the DPC of a route or a member of a cluster route. The pc/pca value must be a full point code, The pc/pca value can be a member of a cluster point code when that cluster point code is the DPC of a route. This can be verified with the rtrv-rte command. If the point code value is not shown in the rtrv-rte output as the DPC of a route, go to the “Adding a Route Containing an SS7 DPC” procedure in Database Administration - SS7 User's Guide and add a new route containing the point code value.

11. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both at the same time.

12. If either the point code or ssn parameters are specified, then both the point code and ssn parameters must be specified.

13. If the Flexible GTT Load Sharing feature is not enabled:

  • The mapset parameter cannot be specified.

  • The point code and subsystem number values specified with the ent-gsmmap-scrn command must be shown in the rtrv-map output, or else the force=yes parameter must be specified. If the point code and subsystem number values are not shown in the rtrv-map output, and a new mated application is to be added, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required mated application with the point code and subsystem number values.

14. If the Flexible GTT Load Sharing feature is enabled:

  • The mapset parameter must be specified.

  • • The force=yes parameter can be used only if the default MAP set assigned to the GSM MAP screening entry.

  • If the MAP set assigned to the GSM MAP screening entry is a MAP set other than the default MAP set, the force=yes parameter cannot be used. The point code and subsystem contained in the GSM MAP screening entry must be in the MAP set assigned to the GSM MAP screening entry.

  • If the default MAP set is assigned to the GSM MAP screening entry and the force=yes parameter is not specified, the point code and subsystem contained in the GSM MAP screening entry must be in the default MAP set.

15. If the forbid=none parameter is specified, then the action=pass parameter must be specified.

16. If the ri=ssn parameter is specified, a numerical value must be specified for the ssn parameter.

GSM screening entries can either be single entries or range entries. Single entries have precedence in screening over range entries. Thus the single entry table is searched first and if a match is found, the range table is never searched. Range entries may overlap single entries.

If a message is screened and does not contain matching GTA, NPV, and NAIV values, the message is rejected. The message is rejected with the default action defined by the ent-gsms-opcode command for the operation code (opcode) parameter entry referenced by the operation name (opname) parameter.

This examples used in this procedure are based on the examples shown in Table 5-7 and Table 5-8.

Table 5-7 Example CGPA GSM MAP Screening Configuration Table

CGSR SADDR EADDR NPV NAIV OPNAME FORBID

cg01

9194600000

---

5

75

pass50

none

cg02

252555100000

252700000000

12

37

discard1

all

cg03

8284540000

8284600000

---

---

ati

state

cg04

2416546464

---

0

127

route25

none

cg05

854000000

857000000

3

99

dd93

all

cg06

154363000000

155000000000

8

86

sri

all

cg07

368900000

369000000

9

111

dup187

none

CGSR

ACTION

PC/PCA/PCI/

PCN/PCN24

SSN

MAPSET

   

cg01

pass

N/A

N/A

N/A

   

cg02

discard

N/A

N/A

N/A

   

cg03

atierr

N/A

N/A

N/A

   

cg04

route

N/A

N/A

N/A

   

cg05

forward

3-201-7

100

DFLT

   

cg06

duplicate

9384

30

10

   

cg07

dupdisc

4-102-6

150

20

   

Table 5-8 Example CDPA GSM MAP Screening Configuration Table

CGSR CDSR SADDR EADDR OPNAME NPV NAIV FORBID

cg01

cd01

---

---

pass50

6

15

all

cg02

cd15

---

---

discard1

10

15

all

cg07

cd10

---

---

dup187

11

57

all

CGSR

CDSR

ACTION

PC/PCA/

PCI/PCN/

PCN24

SSN

MAPSET

   

cg01

cd01

pass

N/A

N/A

N/A

   

cg02

cd15

discard

N/A

N/A

N/A

   

cg07

cd10

dupdisc

5-97-2

135

30

   
  1. Display the GSMMAP screening operation codes in the database using the rtrv-gsms-opcode command.

    If the Flexible GTT Load Sharing feature is not enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   RI  TT
 36     for1      fwd        002-002-002  10    gt  40

OPCODE  OPNAME    DFLTACT    PCI          SSN   RI  TT
 93     dd93      dupdc      5-25-3       200   ssn 10
 139    fwd139    fwd        3-159-7      128   ssn -

OPCODE  OPNAME    DFLTACT    PCN          SSN   RI  TT
 187    dup187    dupl       11519        79    gt  50

OPCODE  OPNAME    DFLTACT    PCN24        SSN   RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    If the Flexible GTT Load Sharing feature is enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   MAPSET RI  TT
 36     for1      fwd        002-002-002  10    25     gt  40

OPCODE  OPNAME     DFLTACT   PCI          SSN   MAPSET RI  TT
 93     dd93       dupdc     5-025-3      200   20     ssn 10 
 139    fwd139     fwd       3-159-7      128   DFLT   ssn -

OPCODE  OPNAME     DFLTACT   PCN          SSN   MAPSET RI  TT
 187    dup187     dupl      11519        79    10     gt  50

OPCODE  OPNAME     DFLTACT   PCN24        SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    Note:

    If the desired GSM MAP screening operation code entry is not shown in the rtrv-gsms-opcode output, go to the “Adding a GSMMAP Screening Operation Code” procedure and add the required entry. Skip step 2 and go to step 3.

    If either the forbid=state, forbid=location, or action=atierr parameters are to be assigned to the GSM MAP screening entry, the GSM MAP screening operation code table must contain an entry containing the operation code value 71.

  2. Enter the rtrv-gsmmap-scrn command with an opname value shown in the rtrv-gsms-opcode command output in step 1 to display the GSMMAP screening entries in the database.
    For this example, enter these commands.

    rtrv-gsmmap-scrn:opname=pass50 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: pass50
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: pass50
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    This is an example of the possible output.

    rtrv-gsmmap-scrn:opname=discard1

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: discard1
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: discard1
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=ati

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: ati
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT   CGSR
919462000000005 1  0   locat atier ati1

Range CgPA Entries for OPNAME: ati
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR
919461888888888 919461900000000 4  1   locat atier ati2
919462000000000 919463000000000 *  *   locat atier ati3

GSM Map Screening table is (1500 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=route25

    This is an example of the possible output.

    rtrv-gsmmap-scrn:opname=dd93

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dd93
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dd93
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=sri

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: sri
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dup187

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dup187
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dup187
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    If the Flexible GTT Load Sharing feature is enabled, the MAPSET field is shown in the rtrv-gsmmap-scrn output as shown in the following output example. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dup187
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dup187
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1500 of 4000) 38% full

    Note:

    If any of the following parameters or values are not being used in this procedure, skip step 3 and go to step 4.

    • saddr=*
    • cdsr
    • pc/pca
    • The saddr or eaddr parameter values containing hex digits.

    If the rtrv-gsmmap-scrn output in this step shows any of the parameters or values listed above, skip step 3, and go to step 4.

  3. Verify that the Enhanced GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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 Enhanced GSM MAP screening feature is not enabled or off, go to the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSM MAP screening feature.

  4. Perform one of these actions.
    • If the action parameter value will be either pass, discard, route, or atierr, skip steps 4 through 8, and continue the procedure with step 9.
    • If the action parameter value will be either forward, duplicate, or dupdisc, perform one of these actions.
      • To use a point code and a MAP set from the mated application table, and MAP sets are not shown in the rtrv-gsmmap-scrn output in step 2, the Flexible GTT Load Sharing Feature must be enabled. Perform the “Activating the Flexible GTTLoad Sharing Feature” procedure in Database Administration - GTT User's Guide and enable the Flexible GTTLoad Sharing feature. After enabling the Flexible GTTLoad Sharing feature, skip steps 5 and 6 and continue the procedure with step 7.
      • To use a point code and a MAP set from the mated application table, and MAP sets are shown in the rtrv-gsmmap-scrn output in step 2, skip steps 5 and 6 and continue the procedure with step 7.
      • To use a point code in the mated application table, but without using a MAP set, and MAP sets are not shown in the rtrv-gsmmap-scrn output in step 2, skip steps 5 and 6 and continue the procedure with step 7.
      • To use a point code that is not in the mated application table, the force=yes parameter must be specified with the ent-gsmmap-scrn command. A proxy point code cannot be assigned to this point code. If the Flexible GTT Load Sharing feature is enabled, the force=yes parameter can be used only if the default MAP set is assigned to the GSM MAP screening entry. Continue the procedure with step 5.
  5. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output. 
    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   001-207-000   ----------- no  --- --------------   --------------   SS7
   001-001-001   ----------- no  --- --------------   --------------   SS7
   001-001-002   ----------- no  --- --------------   --------------   SS7
   001-005-000   ----------- no  --- --------------   --------------   SS7
   001-007-000   ----------- no  --- --------------   --------------   SS7
   008-012-003   ----------- no  --- --------------   --------------   SS7
   003-002-004   ----------- no  --- --------------   --------------   SS7
   009-002-003   ----------- no  --- --------------   --------------   SS7
   010-020-005   ----------- no  --- --------------   --------------   SS7

   DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
   1-207-0       ----------- no  --- --------------   --------------   SS7
   0-015-0       ----------- no  --- --------------   --------------   SS7
   0-017-0       ----------- no  --- --------------   --------------   SS7
   1-011-1       ----------- no  --- --------------   --------------   SS7
   1-011-2       ----------- no  --- --------------   --------------   SS7

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, skip steps 6 through 8 anDatabased perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with step 9.

  6. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   010-020-005   ----------- no  --- --------------   --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   009-002-003  ---- no      50     on    20       no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the adjacent point code is not shown in the rtrv-dstn command output, the following output is displayed. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

No destinations meeting the requested criteria were found

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If the point code is not shown in the rtrv-dstn output, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the adjacent point code to the destination point code table.

    After the new point code has been added, skip steps 7 and 8 and perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with step 9.

  7. The point code and subsystem number being assigned to the GSM MAP screening entry must be in the mated application table.

    Enter the rtrv-map command with the pci/pcn/pcn24 and ssn values that will be specified with the ent-gsmmap-scrn command in step 9.

    If the Flexible GTT Load Sharing feature is not enabled, for this example, enter these commands.

    rtrv-map:pci=3-201-7:ssn=100

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
3-201-5                   100 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pcn=9384:ssn=30

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCN          Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
9384                       30 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pci=4-102-6:ssn=150

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
4-102-6                   150 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    If the Flexible GTT Load Sharing feature is enabled:

    • The mapset parameter must be specified with the ent-gsmmap-scrn command in step 9.
    • The point code and subsystem contained in the GSM MAP screening entry must be in the MAP set assigned to the GSM MAP screening entry.

    For this example, enter these commands.

    rtrv-map:pci=3-201-7:ssn=100

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=DFLT
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
3-201-5                   100 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pcn=9384:ssn=30

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=10
PCN          Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
9384                       30 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    rtrv-map:pci=4-102-6:ssn=150

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=20
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
4-102-6                   150 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    If the point code and subsystem number is not shown in the rtrv-map output, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required point code and subsystem number to the mated application table.

  8. The point code specified with the ent-gsmmap-scrn command must be the DPC of a route.
    If the point code specified with the ent-gsmmap-scrn command is an ANSI point code, the point code can be a member of a cluster point code when that cluster point code is the DPC of a route. Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the ent-gsmmap-scrn command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

    rtrv-rte:dpci=3-201-7

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
3-201-7    12111            240-111-111 ls100001   10    1-234-5
                                        ls100002   10    1-234-6
                                        ls100003   20    1-234-7
                                        ls100004   30    1-234-1
                                        ls100005   40    1-234-2
                                        ls100006   50    1-234-3
                                            RTX:No  CLLI=idp1

    rtrv-rte:dpcn=9384

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCN             ALIASA         ALIASI  LSN        RC    APC
9384             011-222-111    0-001-1 ls200001   10    11111
                                        ls200002   10    11112
                                        ls200003   20    11113
                                        ls200004   30    11114
                                        ls200005   40    11115
                                        ls200006   50    11116
                                            RTX:No  CLLI=ndp1

    rtrv-rte:dpci=4-102-6

    This is an example of the possible output. 

    
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
4-102-6    7659             240-039-150 ls100001   10    5-25-3
                                        ls100002   10    3-250-6
                                        ls100003   20    7-34-7
                                        ls100004   30    6-98-1
                                        ls100005   40    3-142-2
                                        ls100006   50    1-178-3
                                            RTX:No  CLLI=idp1

    If the point code is not shown in the rtrv-rte output, if the point code is an ANSI point code, the point code is not a member of a cluster point code when that cluster point code is the DPC of a route, go to the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database.

  9. Add the new CGPAGSMMAP screening entries to the database with the ent-gsmmap-scrn command.

    Note:

    If a CDPA entry is being added to an existing CGPA entry, skip steps 9 and 10, and go to step 11.
    See Table 5-6 for the parameter combinations that can be used with the ent-gsmmap-scrn command.

    For this example, enter these commands:

    ent-gsmmap-scrn:saddr=9194600000:npv=5:naiv=75:opname=pass50 :forbid=none:action=pass:cgsr=cg01

    ent-gsmmap-scrn:saddr=252555100000:eaddr=252700000000:npv=12:naiv=37 :opname=discard1:forbid=all :action=discard:cgsr=cg02

    ent-gsmmap-scrn:saddr=8284540000:eaddr=8284600000:opname=ati :forbid=state:action=atierr:cgsr=cg03

    ent-gsmmap-scrn:saddr=2416546464:opname=route25:forbid=all :action=route:npv=0:naiv=127:cgsr=cg04

    ent-gsmmap-scrn:saddr=854000000:eaddr=857000000:opname=dd93 :forbid=all:action=forward:npv=3:naiv=99:pci=3-201-7:ssn=100:cgsr=cg05 :mapset=dflt

    ent-gsmmap-scrn:saddr=154363000000:eaddr=155000000000:opname=sri :forbid=all:action=duplicate:npv=8:naiv=86:pcn=9384:ssn=30:cgsr=cg06 :mapset=10

    ent-gsmmap-scrn:saddr=368900000:eaddr=369000000:opname=dup187 :forbid=all:action=dupdisc:npv=9:naiv=111:pci=4-102-6:ssn=150:cgsr=cg07 :mapset=20

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0
GSM Map Screening table is (1512 of 4000) 38% full
ENT-GSMMAP-SCRN: MASP A - COMPLTD
  10. Verify the changes using the rtrv-gsmmap-scrn command and specifying the opname and cgsr parameter values specified in step 9.
    For this example, enter these commands:

    rtrv-gsmmap-scrn:opname=pass50

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: pass50
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR
9194600000      5  75  none  pass cg01

Range CgPA Entries for OPNAME: pass50
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=discard1

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0
Single CgPA Entries for OPNAME: discard1
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: discard1
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

252555100000    252700000000    12 37  all   disc  cg02

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=ati

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: ati
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: ati
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

8284540000      8284600000      *  *   state atier cg03

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=route25

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: route25
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

2416546464      0  127 all   route cg04

Range CgPA Entries for OPNAME: ati
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dd93

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dd93
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dd93
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR
854000000       857000000       3  99  all   fwd      3-201-7       100 cg05
MAPSET = DFLT RI=ssn  TT=-
SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=sri

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: sri
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR
1534363000000   155000000000    8  86  all   dupl     9384          30  cg06
MAPSET = 10 RI=ssn  TT=-
SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dup187

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dup187
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dup187
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR
368900000       369000000       9  111 all   dupdc    4-102-6       150 cg07
MAPSET = 20 RI=ssn  TT=-

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full
  11. Add the new CDPAGSMMAP screening entries to the database with the ent-gsmmap-scrn command.

    Note:

    If a CDPA entry is not being added, or if the Enhanced GSMMAP Screening feature is not enabled or off (see the rtrv-ctrl-feat output in step 3), skip steps 11 and 12, and go to step 13.
    See Table 5-6 for the parameter combinations that can be used with the ent-gsmmap-scrn command.

    For this example, enter these commands:

    ent-gsmmap-scrn:opname=pass50:npv=6:naiv=15:forbid=all:action=pass :cgsr=cg01:cdsr=cd01

    ent-gsmmap-scrn:opname=discard1:npv=10:naiv=15:forbid=all:action=discard :cgsr=cg02:cdsr=cd15

    ent-gsmmap-scrn:opname=dup187:npv=11:naiv=57:forbid=all:pci=5-97-2 :ssn=135:action=dupdisc:cgsr=cg07:cdsr=cd10:mapset=30

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0
GSM Map Screening table is (1512 of 4000) 38% full
ENT-GSMMAP-SCRN: MASP A - COMPLTD
  12. Verify the changes using the rtrv-gsmmap-scrn command and specifying the opname, cgsr, and cdsr parameter values specified in step 11.
    For this example, enter these commands:

    rtrv-gsmmap-scrn:opname=pass50:cgsr=cg01:cdsr=cd01

    This is an example of the possible output. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0

SADDR           NP NAI FORBD ACT   CDSR
*               6  15  all   pass  cd01

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=discard1:cgsr=cg02:cdsr=cd15

    This is an example of the possible output. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0

SADDR           NP NAI FORBD ACT   CDSR
*               10 15  all   disc  cd15

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dup187:cgsr=cg07:cdsr=cd10

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR  MAPSET RI
*               11 57  all   dupdc    5-97-2        135 cd10  30     ssn
TT=-

GSM Map Screening table is (1512 of 4000) 38% full
  13. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-13 Adding a GSM MAP Screening Entry



Sheet 1 of 8



Sheet 2 of 8



Sheet 3 of 8



Sheet 4 of 8



Sheet 5 of 8



Sheet 6 of 8



Sheet 7 of 8



Sheet 8 of 8

Removing a GSM MAP Screening Entry

Use this procedure to remove the GSM MAP screening entries that filter or allow TCAP messages containing MAP operation codes, origination addresses, and forbidden parameters using the dlt-gsmmap-scrn command. The dlt-gsmmap-scrn command uses these parameters:

:opname – The user-defined name for the operation code. The opname value references the operation code (opcode) shown in the rtrv-gsms-opcode command output.

:cgsr – The CGPA screening reference name

:cdsr – The CDPA screening reference name

If the GSM MAP Screening entry contains CDPA entries, the individual CDPA entries can be removed without removing the CGPA entry. However, if you wish to remove the CGPA entry, all CDPA entries assigned to the CGPA entry must be removed before the CGPA entry can be removed.

To remove CDPA entries, the opname, cgsr, and cdsr parameters must be specified with the dlt-gsmmap-scrn command. To remove CGPA entries, the opname and cgsr parameters must be specified with the dlt-gsmmap-scrn command.

Unlike GTT (Global Title Translation) entries, the GSM MAP screening commands do not support splits of ranges during removing or changing entries.

  1. Display the GSMMAP screening operation codes in the database using the rtrv-gsms-opcode command.

    This is an example of the possible output.

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN  RI  TT
 36     for1      fwd        002-002-002  10   gt  10

OPCODE  OPNAME    DFLTACT    PCI          SSN  RI  TT
 93     dd93      dupdc      5-25-3       200  ssn 30
 139    fwd139    fwd        3-159-7      128  ssn - 

OPCODE  OPNAME    DFLTACT    PCN          SSN  RT  TT
 187    dup187    dupl       11519        79   gt  50

OPCODE  OPNAME    DFLTACT    PCN24        SSN

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full
  2. Enter the rtrv-gsmmap-scrn command with an opname value shown in the rtrv-gsms-opcode command output in step 1 to display the CGPAGSMMAP screening entries. For this example, enter these commands.

    rtrv-gsmmap-scrn:opname=pass50 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: pass50
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR
9194600000      5  75  none  pass  cg01

Range CgPA Entries for OPNAME: pass50
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=ati

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: ati
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR
919462000000005 1  0   locat atier ati1

Range CgPA Entries for OPNAME: ati
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR
8284540000      8284600000      *  *   state atier cg03
919461888888888 919461900000000 4  1   locat atier ati2
919462000000000 919463000000000 *  *   locat atier ati3

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=sri

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: sri
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR
1534363000000   155000000000    8  86  all   dupl     9384          30  cg06
RI=ssn TT=-

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    Note:

    The rtrv-gsmmap-scrn output in step 2 shows only the CGPA entries in the MAP screening table for the specified OPNAME. The CGPA entries in step 2 could contain CDPA entries that would have to be removed before the CGPA entry could be removed. CDPA entries can be in the MAP screening table only if the Enhanced GSMMAP Screening feature is enabled and on.

    If any of the following parameters or values are shown in the rtrv-gsmmap-scrn output in step 2, the Enhanced GSM MAP Screening feature is enabled and on. Skip step 3 and go to step 4.

    • saddr=*
    • pc/pca
    • The saddr or eaddr parameter values containing hex digits.

    If the rtrv-gsmmap-scrn output in step 2 does not show any of these parameters or values, it is possible that the Enhanced GSM MAP Screening feature is enabled and on. Perform step 3 to verify the status of the Enhanced GSM MAP Screening feature.

  3. Enter the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.

    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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.

    Note:

    If step 3 shows that the Enhanced GSMMAP Screening feature is not enabled or off, CDPA entries cannot be in the MAP screening table. Skip step 4 and go to step 5.
  4. To display the CDPA entries assigned to the CGPA entry shown in step 2, enter the rtrv-gsmmap-scrn command with the opname and cgsr parameter values specified shown in step 2.

    For this example, enter these commands.

    rtrv-gsmmap-scrn:opname=pass50:cgsr=cg01 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CdPA Entries for OPNAME: pass50 and CGSR: cg01
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT   CDSR
*               6  15  all   pass  cd01

Range CdPA Entries for OPNAME: pass50 and CGSR: cg01
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=ati:cgsr=cg03

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT   CDSR
919461000000130 2  16  locat atier ati5

Range CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           
SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR
4329290000      5450000000      *  *   state atier cd15
919463000000000 919464000000000 11 95  locat atier ati7
803549000000000 803650000000000 *  *   locat atier ati9

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=sri:cgsr=cg06

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: sri and CGSR: cg06
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           NP NAI FORBD ACT   CDSR

Range CgPA Entries for OPNAME: sri and CGSR: cg06
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR

GSM Map Screening table is (1512 of 4000) 38% full
  5. Remove the GSMMAP screening entries from the database with the dlt-gsmmap-scrn command.

    If CDPA entries are being removed, these parameters must be specified with the dlt-gsmmap-scrn command: opname, cgsr, and cdsr.

    If the GSMMAP Screening entry contains CDPA entries, the individual CDPA entries can be removed without removing the CGPA entry. However, if you wish to remove the CGPA entry, all CDPA entries assigned to the CGPA entry must be removed before the CGPA entry can be removed.

    To remove a CGPA entry, enter the dlt-gsmmap-scrn command with the opname, and cgsr parameter values.

    For this example, enter these commands:

    dlt-gsmmap-scrn:opname=pass50:cgsr=cg01:cdsr=cd01

    dlt-gsmmap-scrn:opname=ati:cgsr=cg03:cdsr=cd15

    dlt-gsmmap-scrn:opname=sri:cgsr=cg06

    To remove the CGPA entry cg01 from the opname pass50 (now that CGPA entry cg01 has no CDPA entries assigned), enter this command:

    dlt-gsmmap-scrn:opname=pass50:cgsr=cg01

    When each of these commands has successfully completed, this message appears. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0
GSM Map Screening table is (1508 of 4000) 38% full
DLT-GSMMAP-SCRN: MASP A - COMPLTD
  6. Verify the changes using the rtrv-gsmmap-scrn command with the opname parameter value used in step 5.
    If CDPA entries were removed from CGPA entries without removing the CGPA entry, specify the opname and cgsr parameter values used in step 5 with the rtrv-gsmmap-scrn command.

    For this example, enter these commands:

    rtrv-gsmmap-scrn:opname=pass50

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: pass50
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: pass50
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1508 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=ati:cgsr=cg03

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT   CDSR
919461000000130 2  16  locat atier ati5

Range CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR
919463000000000 919464000000000 11 95  locat atier ati7
803549000000000 803650000000000 *  *   locat atier ati9

GSM Map Screening table is (1508 of 4000) 38% full
  7. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-14 Removing a GSM MAP Screening Entry



Sheet 1 of 2



Sheet 2 of 2

Changing a GSM MAP Screening Entry

Use this command to change the attributes of the GSM MAP screening entries that filter or allow TCAP messages for certain MAP operation codes using the chg-gsmmap-scrn command. The SCCP messages contain MAP operation codes, origination addresses, numbering plan values, nature of address indicator values, and forbidden parameters.

The chg-gsmmap-scrn command uses these parameters.

:opname – The user-defined name for the operation code. The opname value references the operation code (opcode) defined with the ent-gsms-opcode command. GSM MAP screening is performed on the specified address or addresses for the referenced operation code.

:naction – The new screening action to take if a message is forbidden as defined by the forbid parameter value. One of these actions can be assigned.

  • pass – Route the message as normal to the destination.
  • discard – The MSU is to be discarded.
  • atierr – An ATI (Any Time Interrogation) reject message is generated. This option is only valid for ATIMAP operation codes.
  • route – Route the message as normal to the original destination node.
  • forward – Route the original message to the forward node. The original message is not sent to the original node. If, however, the forwarded node is not available for routing then the MSU is routed to the original node.
  • duplicate – Route the message as normal to the original destination and route a copy of the original message to the duplicate node.
  • dupdisc – Duplicate and discard – Route the original message to the duplicate node. The original message is not sent to the original node.

:npc/npca/npci/npcn/npcn24 – The new ANSI point code (npc/npca), new ITU-I point code or ITU-I spare point code (npci), new 14-bit ITU-N point code or 14-bit ITU-N spare point code (npcn), or new 24-bit ITU-N point code (npcn24) of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both.

:nssn – The new subsystem number of the node that the MSU is routed to by the forward, duplicate, or dupdisc screening actions

:force – The mated application override. Is the GSM MAP screening operation code to be entered without a mated application in the database (yes or no)?

:nforbid – The new forbidden parameter value. If a forbidden parameter is detected, the message is rejected by the action defined by the action parameter value. One of four forbidden parameter values can be specified.

  • all – All parameters are forbidden. Take the specified screening action defined by the naction parameter for incoming messages that contain the entered address and operation code combination.
  • none – No parameters are forbidden. Take the specified screening action defined by the naction parameter for incoming messages that contain the entered address and operation code combination.
  • state – Take the specified screening action defined by the naction parameter for incoming messages that contain state as the forbidden parameter for the entered address and operation code combination.
  • location – Take the specified screening action defined by the naction parameter for incoming messages that contain location as the forbidden parameter for the entered address and operation code combination.

:cgsr – The current CGPA screening reference name.

:cdsr – The current CDPA screening reference name.

:ncgsr – The new CGPA screening reference name consisting of 1 alphabetic character and 3 optional alphanumeric characters.

:ncdsr – The new CDPA screening reference name consisting of 1 alphabetic character and 3 optional alphanumeric characters.

:nmapset – The new MAP set ID, shown in the rtrv-map command. This parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform the “Activating the Flexible GTT Load Sharing Feature” procedure in Database Administration - GTT User's Guide.

:nri - The new routing indicator parameter. This parameter specifies whether a subsequent global title translation is required. This parameter has two values.
  • gt - subsequent global title translation is required.
  • ssn - subsequent global title translation is not required.

:ntt - the new translation type that will be assigned to the GSM MAP screening entry. This parameter specifies the value that the translation type for the CdPA is set to as a result of GSM MAP screening. The values for this parameter are 0 to 255, or the value none which specifies removes the existing translation type from to the GSM MAP screening entry.

If a message is screened and does not contain matching npv and naiv values, the message is rejected. The message is rejected with the default action defined by the chg-gsms-opcode command for the operation code (opcode) parameter entry referenced by the operation name (opname) parameter.

Table 5-9 shows the parameter combinations that can be used in this procedure.

Table 5-9 Change GSM MAP Screening Entry Parameter Combinations

Entry Containing a Point Code and SSN Enhanced GSM MAP Screening Feature Enabled and On Entry Without a Point Code and SSN Enhanced GSM MAP Screening Feature Enabled and On Entry containing the Action ATIERR Enhanced GSM MAP Screening Feature Enabled and On Entry Containing a Point Code and SSN GSM MAP Screening Feature Enabled and On Only Entry Without a Point Code and SSN GSM MAP Screening Feature Enabled and On Only Entry containing the Action ATIERR GSM MAP Screening Feature Enabled and On Only

Mandatory Parameters

:opname = current opname value (See Note 2)

:opname = current opname value (See Note 2)

:opname = current opname value containing opcode=71 (See Note 2)

:opname = current opname value (See Note 2)

:opname = current opname value (See Note 2)

:opname = current opname value containing opcode=71 (See Note 2)

:cgsr = current CGSR value

:cgsr = current CGSR value

:cgsr = current CGSR value

:cgsr = current CGSR value

:cgsr = current CGSR value

:cgsr = current CGSR value

Optional Parameters (See Note 1)

:cdsr = current CDSR value (See Notes 3 and 4)

:cdsr = current CDSR value (See Notes 3 and 4)

:cdsr = current CDSR value (See Notes 3 and 4)

:nforbid = all

:nforbid = all, none (See Note 13)

:nforbid = state, location

:nforbid = all

:nforbid = all, none (See Note 13)

:nforbid = state, location

:naction = forward, duplicate, dupdisc (See Note 6)

:naction = pass, discard, route (See Note 13)

:naction = atierr

:naction = forward, duplicate, dupdisc (See Note 6)

:naction = pass, discard, route (See Note 13)

:naction = atierr

:ncgsr = new CGSR value

:ncgsr = new CGSR value

:ncgsr = new CGSR value

:ncgsr = new CGSR value (See Notes 4 and 5)

:ncgsr = new CGSR value (See Notes 4 and 5)

:ncgsr = new CGSR value (See Notes 4 and 5)

:npci/npcn/

npcn24 =point code

value (See Notes 7, 8, 9, 10, 11, and 12)

    

:ncdsr = new CDSR value (See Notes 3 and 5)

:ncdsr = new CDSR value (See Notes 3 and 5)

:ncdsr = new CDSR value (See Notes 3 and 5)

:nssn = 0 - 255, none (See Notes 7, 8, 9, 10, 11, 12, and 14)

:npc/npca/npci/

npcn/npcn24 = point code

value (See Notes 7, 8, 9, 10, 11, and 12)

    

:force=yes (See Notes 11 and 12)

:nmapset = dflt or numbered MAP set ID (See Notes 11 and 12)

:nssn = 0 - 255, none (See Notes 7, 8, 9, 10, 11, 12, and 14)

 :nri = gt, ssn (See Note 14)

:force=yes (See Notes 11 and 12)

 :ntt = 0 - 255, none (See Note 15)

:nmapset = dflt or numbered MAP set ID (See Notes 11 and 12)

  
:nri = gt, ssn (See Note 14)
:ntt = 0 - 255, none (See Note 15)

Notes:

1. At least one optional parameter must be specified with the chg-gsmmap-scrn command. If the cdsr parameter is specified, at least one other optional parameter must be specified with the chg-gsmmap-scrn command.

2. The opname parameter value must be shown in the rtrv-gsms-opcode output.

3. The cdsr parameter must be specified when the ncdsr parameter is specified.

4. The ncgsr parameter should not be specified when the cdsr parameter is specified.

5. The ncgsr and ncdsr parameters cannot be specified together.

6. The point code value must be the DPC of a route or a member of a cluster route. The npc/npca value must be a full point code, The npc/npca value can be a member of a cluster point code when that cluster point code is the DPC of a route. This can be verified with the rtrv-rte command. If the point code value is not shown in the rtrv-rte output as the DPC of a route, go to the “Adding a Route Containing an SS7 DPC” procedure in Database Administration - SS7 User's Guide and add a new route containing the point code value. A proxy point code cannot be assigned to the point code.

7. The EAGLE can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not both at the same time.

8. If the new or current (if unchanged) action parameter values are either forward, duplicate, or dupdisc, the point code and nssn parameters must be specified with the chg-gsmmap-scrn command. If the point code or subsystem number values are not being changed, the point code and subsystem number parameters must be specified with the current values for these parameters.

9. If only the point code or subsystem number value is being changed, the point code or subsystem number value being changed must be specified with the new value for the parameter being changed. The current value for the point code or subsystem number parameter not being changed must be specified. The naction parameter does not have to be specified. For example, if the current point code is pca=002-002-002 and the subsystem number is 50, and the point code is being changed to pca=003-003-003 and the subsystem number is not changing, the npca parameter value would be the new point code value (003-003-003) and the nssn parameter value would be the current value (50).

10. To specify the npc/npca parameters, the Enhanced GSM MAP Screening feature must be enabled and turned on.

11. If the Flexible GTT Load Sharing feature is not enabled:

  • The nmapset parameter cannot be specified.

  • The point code and subsystem number values specified with the chg-gsmmap-scrn command must be shown in the rtrv-map output, or else the force=yes parameter must be specified. If the point code and subsystem number values are not shown in the rtrv-map output, and a new mated application is to be added, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required mated application with the point code and subsystem number values.

12. If the Flexible GTT Load Sharing feature is enabled:

  • If the current action parameter value is either pass, route, discard, or atierr, and the action parameter value is changed to either forward, duplicate, or dupdisc, the GSM MAP screening entry must be assigned to a MAP set with the nmapset=dflt parameter (to assign the GSM MAP screening entry to the default MAP set), or with the nmapset=<numbered MAP set ID> parameter (to assign the GSM MAP screening entry to a MAP set other the default MAP set).

  • If the default MAP set will be assigned to the GSM MAP screening entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in the default MAP set in the rtrv-map output. If the npc/npca/npci/npcn/npcn24 or nssn values are not shown in the default MAP set in the rtrv-map output, the force=yes parameter must be specified.

  • If a MAP set other than the default MAP set will be assigned to the GSM MAP screening entry, the npc/npca/npci/npcn/npcn24 and nssn values must be shown in that MAP set in the rtrv-map output.

  • If the point code and subsystem values are not being changed, the nmapset parameter does not have to be specified unless the MAP set ID assigned to the GSM MAP screening entry is being changed. The new MAP set must contain the point code and subsystem values in the GSM MAP screening entry.

13. If the value of the forbid parameter is being changed to none, and the current value of the action parameter is not pass, the naction=pass parameter must be specified. If the current value of the forbid parameter is none and will not be changed, the value of the action parameter must be pass and cannot be changed.

14. If, when the chg-gsmmap-scrn command is completed, the ri parameter value is ssn, then a numerical value must be assigned to the ssn parameter.

15. The value none for the tt parameter removes the existing tt parameter value that is assigned to the GSM MAP screening entry. A dash is shown in the TT column of the rtrv-gsmmap-scrn output when the tt value is removed.

  1. Display the GSM MAP screening operation codes in the database using the rtrv-gsms-opcode command.

    If the Flexible GTT Load Sharing feature is not enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN  RI  TT
 36     for1      fwd        002-002-002  10   gt  10

OPCODE  OPNAME     DFLTACT   PCI          SSN  RI  TT
 93     dd93       dupdc     5-025-3      200  ssn 40
 139    fwd139     fwd       3-159-7      128  ssn -

OPCODE  OPNAME     DFLTACT   PCN          SSN  RI  TT
 187    dup187     dupl      11519        79   gt  50

OPCODE  OPNAME     DFLTACT   PCN24        SSN

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    If the Flexible GTT Load Sharing feature is enabled, this is an example of the possible output. 

    
rlghncxa03w 08-09-10 11:43:04 GMT EAGLE5 39.2.0

OPCODE  OPNAME    DFLTACT    PCA          SSN   MAPSET RI  TT
 36     for1      fwd        002-002-002  10    25     gt  10

OPCODE  OPNAME     DFLTACT   PCI          SSN   MAPSET RI  TT
 93     dd93       dupdc     5-025-3      200   20     ssn 40
 139    fwd139     fwd       3-159-7      128   DFLT   ssn -

OPCODE  OPNAME     DFLTACT   PCN          SSN   MAPSET RI  TT
 187    dup187     dupl      11519        79    10     gt  50

OPCODE  OPNAME     DFLTACT   PCN24        SSN   MAPSET RI  TT

OPCODE  OPNAME    DFLTACT
 22     sri       disc
 25     route25   route
 50     pass50    pass
 71     ati       atierr
 150    discard1  disc
 *      star      pass

GSMMS OPCODE Table (10 of 257) is 4% full

    If the default action for the GSM MAP screening entry will be atierr, or the forbid parameter value will be location or state, the opname value must contain an opcode value of 71.

  2. Enter the rtrv-gsmmap-scrn command with an opname value shown in the rtrv-gsms-opcode command output in step 1 to display the CGPA GSM MAP screening entries to change.
    For this example, enter this command.

    rtrv-gsmmap-scrn:opname=ati

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: ati
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR
919462000000005 1  0   locat atier ati1

Range CgPA Entries for OPNAME: ati
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           
SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR
8284540000      8284600000      *  *   state atier cg03
919461888888888 919461900000000 4  1   locat atier ati2
919462000000000 919463000000000 *  *   locat atier ati3

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dd93

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dd93
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR RI  TT 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR RI  TT

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dd93
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR
854000000       857000000       3  99  all   fwd      3-201-7       100 cg05
RI=ssn TT=-

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    If the Flexible GTTLoad Sharing feature is enabled, the MAPSET field is shown in the rtrv-gsmmap-scrn output as shown in the following output example. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dd93
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET  RI 

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dd93
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           
SSN CGSR
854000000       857000000       3  99  all   fwd      3-201-7       100 cg05
MAPSET = DFLT RI=ssn TT=-

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full

    Note:

    If the npc/npca or ncdsr parameters are being specified in this procedure, the Enhanced GSMMAP Screening feature must be enabled and on. If these parameters are not being specified in this procedure, skip step 3 and go to step 4.

    If any of the following parameters or values are shown in the rtrv-gsmmap-scrn output in this step, the Enhanced GSM MAP Screening feature is enabled and on. Skip step 3 and go to step 4.

    • saddr=*
    • pc/pca
    • The saddr or eaddr parameter values containing hex digits.

    If the rtrv-gsmmap-scrn output in this step does not show any of these parameters or values, it is possible that the Enhanced GSM MAP Screening feature is enabled and on. If you wish to use the npc/npca or ncdsr parameters, perform step 3 to verify the status of the Enhanced GSM MAP Screening feature.

  3. Verify that the Enhanced GSMMAP Screening feature is enabled and on by entering the rtrv-ctrl-feat command with the part number of the Enhanced GSMMAP Screening feature.
    Enter this command.

    rtrv-ctrl-feat:partnum=893012401

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Enhanced GMS (EGMS)       893012401  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 Enhanced GSMMAP screening feature is not enabled or is turned off, and you wish to use the npc/npca or ncdsr parameters, perform the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the Enhanced GSMMAP Screening feature. After the Enhanced GSM MAP Screening feature has been enabled and turned on, continue the procedure with step 4.
    • Skip step 4 and continue the procedure with step 5 if:
      • The Enhanced GSMMAP Screening feature will not be enabled and turned on in this step.
      • The npc/npca or ncdsr parameters will not be specified in this procedure and the Enhanced GSM MAP Screening feature is enabled and turned on.
  4. Enter the rtrv-gsmmap-scrn command with an opname and cgsr values shown in the rtrv-gsmmap-scrn command output in step 2 to display the CDPAGSMMAP screening entries to change.
    For this example, enter this command.

    rtrv-gsmmap-scrn:opname=ati:cgsr=cg03

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT   CDSR
919461000000130 2  16  locat atier ati5

Range CdPA Entries for OPNAME: ati and CGSR: cg03
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           
SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR
4329290000      5450000000      *  *   state atier cd15
919463000000000 919464000000000 11 95  locat atier ati7
803549000000000 803650000000000 *  *   locat atier ati9

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dd93:cgsr=cg05

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CdPA Entries for OPNAME: dd93 and CGSR: cg05
--------------------------------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCI           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN           SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT      PCN24         SSN CDSR RI  TT

SADDR           NP NAI FORBD ACT   CDSR

Range CgPA Entries for OPNAME: dd93 and CGSR: cg05
--------------------------------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CDSR

SADDR           EADDR           NP NAI FORBD ACT   CDSR

GSM Map Screening table is (1512 of 4000) 38% full

    Note:

    If the Flexible GTTLoad Sharing feature is enabled, the MAPSET field is shown in the rtrv-gsmmap-scrn output if the action parameter value for the GSMMAP screening entry is either forward, duplicate, or dupdisc.
  5. Perform one of these actions.
    • If the naction parameter value will be either pass, discard, route, or atierr, skip steps 6 through 9, and continue the procedure with step 10.
    • If the point code is not being changed, skip steps 6 through 9, and continue the procedure with step 10. If the point code and subsystem values are not being changed, and the Flexible GTT Load Sharing feature is enabled, the nmapset parameter does not have to be specified unless the MAP set ID assigned to the GSM MAP screening entry is being changed. The new MAP set must contain the point code and subsystem values in the GSM MAP screening entry.
    • If the naction parameter value will be either forward, duplicate, or dupdisc, perform one of these actions.
      • To use a point code and a MAP set from the mated application table, and MAP sets are not shown in the rtrv-gsmmap-scrn output in step 4, the Flexible GTT Load Sharing Feature must be enabled. Perform the “Activating the Flexible GTTLoad Sharing Feature” procedure in Database Administration - GTT User's Guide and enable the Flexible GTTLoad Sharing feature. After enabling the Flexible GTTLoad Sharing feature, skip steps 6 and 7 and continue the procedure with step 8.
      • To use a point code and a MAP set from the mated application table, and MAP sets are shown in the rtrv-gsmmap-scrn output in step 4, skip steps 6 and 7 and continue the procedure with step 8.
      • To use a point code in the mated application table, but without using a MAP set, and MAP sets are not shown in the rtrv-gsmmap-scrn output in step 4, skip steps 6 and 7 and continue the procedure with step 8.
      • To use a point code that is not in the mated application table, the force=yes parameter must be specified with the chg-gsmmap-scrn command. A proxy point code cannot be assigned to this point code. If the Flexible GTT Load Sharing feature is enabled, the force=yes parameter can be used only if the default MAP set is assigned to the GSM OPCODE entry. Continue the procedure with step 6.
  6. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   001-207-000   ----------- no  --- --------------   --------------   SS7
   001-001-001   ----------- no  --- --------------   --------------   SS7
   001-001-002   ----------- no  --- --------------   --------------   SS7
   001-005-000   ----------- no  --- --------------   --------------   SS7
   001-007-000   ----------- no  --- --------------   --------------   SS7
   008-012-003   ----------- no  --- --------------   --------------   SS7
   003-002-004   ----------- no  --- --------------   --------------   SS7
   009-002-003   ----------- no  --- --------------   --------------   SS7
   010-020-005   ----------- no  --- --------------   --------------   SS7

   DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
   1-207-0       ----------- no  --- --------------   --------------   SS7
   0-015-0       ----------- no  --- --------------   --------------   SS7
   0-017-0       ----------- no  --- --------------   --------------   SS7
   1-011-1       ----------- no  --- --------------   --------------   SS7
   1-011-2       ----------- no  --- --------------   --------------   SS7

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, skip steps 7 through 9 and perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with step 10.

  7. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   010-020-005   ----------- no  --- --------------   --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   009-002-003  ---- no      50     on    20       no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    If the adjacent point code is not shown in the rtrv-dstn command output, the following output is displayed. 

    
rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0

No destinations meeting the requested criteria were found

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If the point code is not shown in the rtrv-dstn output, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the adjacent point code to the destination point code table.

    After the new point code has been added, skip steps 8 and 9, and perform the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with step 10.

  8. The point code and subsystem number being assigned to the GSMMAP screening entry must be in the mated application table.
    Enter the rtrv-map command with the npc/npca/npci/npcn/npcn24 and nssn values that will be specified with the chg-gsmmap-scrn command in step 10.

    If the Flexible GTTLoad Sharing feature is not enabled, for this example, enter these commands.

    rtrv-map:pci=5-79-2:ssn=89

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
5-079-2                    89 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    Note:

    If the point code and subsystem number is not shown in the rtrv-map output, and is not added to the database in one of these procedures, the force=yes parameter must be specified with the chg-gsmmap-scrn command in step 10.

    If the Flexible GTT Load Sharing feature is enabled and the current action parameter value is either pass, route, discard, or atierr, and the action parameter value is changed to either forward, duplicate, or dupdisc, the GSM MAP screening entry must be assigned to a MAP set with the nmapset=dflt parameter (to assign the GSM MAP screening entry to the default MAP set), or with the nmapset=<numbered MAP set ID> parameter (to assign the GSM MAP screening entry to a MAP set other the default MAP set).

    For this example, enter these commands.

    rtrv-map:pci=5-79-2:ssn=89

    This is an example of the possible output. 

    
rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0

MAPSET ID=DFLT
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
5-079-2                    89 10  SOL *N  *N  GRP01    ON

MAP TABLE IS (20 of 1024) 2 % FULL

    If the point code and subsystem number is not shown in the rtrv-map output, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide and add the required point code and subsystem number to the mated application table.

  9. The point code specified with the chg-gsmmap-scrn command must be the DPC of a route.
    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the chg-gsmmap-scrn command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

    rtrv-rte:dpci=5-79-2

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
5-79-2     1501             230-101-191 ls100001   10    1-234-5
                                        ls100002   10    3-65-4
                                            RTX:No  CLLI=idp9

    If the point code is not shown in the rtrv-rte output, go to the "Adding a Route Containing an SS7 DPC" procedure in Database Administration - SS7 User's Guide and add the required route to the database.

  10. Change the GSMMAP screening entry with the chg-gsmmap-scrn command.
    Table 5-9 shows the parameter combinations that can be used with the chg-gsmmap-scrn command.

    For this example, the Enhanced GSM MAP Screening feature is enabled and on. Enter these commands:

    chg-gsmmap-scrn:opname=ati:cgsr=cg03:cdsr=cd15:nforbid=none :naction=pass

    chg-gsmmap-scrn:opname=dd93:cgsr=cg05:nforbid=none:naction=pass :npci=5-79-2:nssn=89:nmapset=20

    When this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-20 09:07:58 GMT  EAGLE5 36.0.0
GSM Map Screening table is (1512 of 4000) 38% full
CHG-GSMMAP-SCRN: MASP A - COMPLTD
  11. Verify the changes using the rtrv-gsmmap-scrn command, specifying the opname parameter value used in step 10.
    If the cdsr parameter was specified in step 10, specify the cgsr, and cdsr parameter values used in step 10 with the opname parameter value. For this example, the Enhanced GSMMAP Screening feature is enabled and on. Enter these commands:

    rtrv-gsmmap-scrn:opname=ati:cgsr=cg03:cdsr=cd15

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

SADDR           EADDR           NP NAI FORBD ACT   CDSR  MAPSET RI
8284540000      8284600000      *  *   none  pass  cd15  DFLT   ssn
TT=-

GSM Map Screening table is (1512 of 4000) 38% full

    rtrv-gsmmap-scrn:opname=dd93

    This is an example of the possible output. 

    
rlghncxa03w 08-09-20 09:07:58 GMT  EAGLE5 39.2.0

Single CgPA Entries for OPNAME: dd93
-----------------------------------
SADDR           NP NAI FORBD ACT      PCA           SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT      PCI           SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT      PCN           SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT      PCN24         SSN CGSR  MAPSET  RI

SADDR           NP NAI FORBD ACT  CGSR

Range CgPA Entries for OPNAME: dd93
----------------------------------
SADDR           EADDR           NP NAI FORBD ACT      PCA           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCI           SSN CGSR
854000000       860000000       3  99  none  pass     5-79-2        89  cg05
MAPSET = 20 RI=ssn TT=-

SADDR           EADDR           NP NAI FORBD ACT      PCN           SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT      PCN24         SSN CGSR

SADDR           EADDR           NP NAI FORBD ACT   CGSR

GSM Map Screening table is (1512 of 4000) 38% full
  12. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-15 Changing a GSM MAP Screening Entry



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6

Changing the GSM MAP Screening TCAP Continue and End Message Processing Option

The option for enabling or disabling the processing of GSM MAP screening TCAP Continue and TCAP End messages can be changed with the chg-sccpopts command and with the following parameter:

:gmstcapce – This parameter has two values:

  • on – enables the processing of TCAP Continue and TCAP End messages.

  • off – disables the processing of TCAP Continue and TCAP End messages.

The system default value for this parameter is off.

The value of the gmstcapce parameter is shown in the GMSTCAPCE field of the rtrv-sccpopts output. The GMSTCAPCE field of the rtrv-sccpopts output is shown only when the GSM MAP Screening feature is enabled and turned on. If the GMSTCAPCE field is not shown in the rtrv-sccpopts output, perform the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSM MAP screening feature.

  1. Display the existing value for the gsmtcapce parameter by entering the rtrv-sccpopts command.
    The value for the gsmtcapce parameter is shown in the GSMTCAPCE field. This is an example of the possible output. 
    
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0

SCCP OPTIONS
-------------------------------
GSMTCAPCE                   off

    Note:

    The rtrv-sccpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-sccpopts command, see the rtrv-sccpopts command description in the Commands Manual.

    If the GSMTCAPCE field is not shown in the rtrv-sccpopts output, perform the “Activating the GSMMAP Screening Feature” procedure to enable and turn on the GSMMAP screening feature. After the GSMMAP Screening feature is enabled and turned on, go to step 2.

    If the GSMTCAPCE field is shown in the rtrv-sccpopts output, go to step 2.

  2. Change the gsmtcapce parameter value by entering on of the following commands.

    If the current value of the gsmtcapce parameter is off, or if the GSMMAP Screening feature was enabled and turned on in step 1, enter the following command to enable the processing of TCAP Continue and TCAP End messages.

    chg-sccpopts:gsmtcapce=on

    If the current value of the gsmtcapce parameter is on, enter the following command to disable the processing of TCAP Continue and TCAP End messages.

    chg-sccpopts:gsmtcapce=off

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 00:22:57 GMT  EAGLE5 36.0.0
CHG-SCCPOPTS: MASP A - COMPLTD
  3. Verify the changes using the rtrv-sccpopts command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0

SCCP OPTIONS
-------------------------------
GSMTCAPCE                    on

    Note:

    The rtrv-sccpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-sccpopts command, see the rtrv-sccpopts command description in the Commands Manual.

  4. Backup the new changes using the chg-db:action=backup:dest=fixed command.
    These 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 5-16 Changing the GSM MAP Screening TCAP Continue and End Message Processing Option