Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.8
F11880-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Adding a Global Title Translation

This procedure is used to add a global title translation to the database using the ent-gtt command.

The ent-gtt command uses these parameters.

:gta – Global title start address – along with the egta parameter, identifies all valid global titles for the given translation type to translate to the given pc or ssn parameters. These are the non-SS7 addresses transmitted to the STP for translation.

:type/typea/typei/typeis/typen/typens/typen24 – The translation type and network type of the translation type that is being assigned to the global title translation. The value of this parameter is shown in the rtrv-tt output and provisioned in the Adding a Translation Type procedure.

:ttn - the translation type name associated with the :type/typea/typei/typeis/typen/typens/typen24 parameter value. The value of this parameter is shown in the rtrv-tt output and provisioned in the Adding a Translation Type procedure.

:egta – Global title end address – along with the gta parameter, identifies all valid global titles for the given translation type to translate to the given pc or ssn parameters. These are the non-SS7 addresses transmitted to the STP for translation.

:force – the mated application override. Is the global title translation to be entered without a mated application in the database?

:xlat – Translate indicator – defines the type of global title translation that is to be performed.

:ri – Route indicator – indicates whether a subsequent global title translation is required.

:pc/pca/pci/pcn/pcn24 – The point code of the signaling point that is to receive the message.

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.

:ssn – Subsystem number – identifies the subsystem address that is to receive the message.

:gtmodid - the name of the GT modification identifier shown in the rtrv-gtmod output and provisioned in the Adding Global Title Modification Information procedure. The GT modification identifier contains the information to modify the numbering plan, nature of address indicator, and the prefix or suffix digits in the called party address or calling party address portion of outbound MSUs.

:mrnset – The MRN set ID, shown in the rtrv-mrn command. This parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled and if the ri=gt parameter is specified for the global title translation. If the Flexible GTT Load Sharing feature is enabled, the point code specified for the global title translation must be assigned to the MRN set specified by this parameter. 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.

:mapset – The MAP set ID, shown in the rtrv-map command. This parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled and if the ri=ssn parameter is specified for the global title translation. If the Flexible GTT Load Sharing feature is enabled, the point code and SSN specified for the global title translation must be assigned to the MAP set specified by this parameter. 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.

:loopset - The value of this parameter is the name of the loopset that is assigned to the GTT. This parameter can be specified only if the SCCP Loop Detection feature is enabled. Enter the rtrv-loopset command to verify that the SCCP Loop Detection feature is enabled. Perform the Activating the SCCP Loop Detection Feature procedure, if necessary. By default, the value of the loopset parameter is “none” because no loopset is assigned to the GTT.

:cggtmod - The calling party GT modification indicator. This parameter specifies whether or not calling party global title modification is required. The values for this parameter are yes (calling party global title modification is required) or no (calling party global title modification is not required). This parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled. Enter the rtrv-ctrl-feat command to verify that either the AMGTT or AMGTT CgPA Upgrade feature is enabled. If the AMGTT or AMGTT CgPA Upgrade feature is not enabled, perform the Activating the Advanced GT Modification Feature procedure to enable the required feature.

Note:

The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the ent-gtt command are too long to fit on the ent-gtt command line, perform the Changing a Global Title Translation section to complete adding the GTT entry.

The XLAT parameter does not have a SEAS equivalent. When global title translations are configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, all mandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE parameters and values shown in the Table 3-3 procedure.

Table 3-3 SEAS and Global Title Translation Parameter Conversion

SEAS GTT Parameters GTT Parameters
RI DPC SSN XLAT RI PC/PCA SSN
G xxx-xxx-xxx 000 DPC GT xxx-xxx-xxx Not Specified
D xxx-xxx-xxx 002-255 DPCSSN SSN xxx-xxx-xxx 002-255
G xxx-xxx-xxx 002-255 DPCSSN GT xxx-xxx-xxx 002-255
D xxx-xxx-xxx 000 DPC SSN xxx-xxx-xxx Not Specified

Notes:

  • The SEAS RI=G parameter denotes global title routing, further global title translation is required.
  • The SEAS RI=D parameter denotes DPC routing, no further global title translation is required.
  • The RI=GT parameter denotes further global title translation is required and uses MTP routing.
  • The RI=SSN parameter denotes final global title translation and uses MAP routing.
  • The XLAT=DPC parameter indicates that the DPC & RI values in the MSU are to be replaced.
  • The XLAT=DPCSSN parameter indicates that the DPC, RI, and SSN values in theMSU are to be replaced.
  • The XLAT=DPCNGT parameter indicates that the DPC, RI, and TT values in the MSU are to be replaced.

The global title translation data cannot be added to the database if the translation type is defined as an alias and if the global title translation data is already assigned to that translation type.

If the translate indicator is equal to dpc (xlat=dpc) and the routing indicator is equal to ssn (ri=ssn), and the force=yes parameter is not specified, the point code specified in the ent-gtt command must be defined in the database as a mated application. Verify this by entering the rtrv-map command. If this point code is not defined as a mated application, perform one of these procedures to add the point code and subsystem number to the database as a mated application:

The point code and subsystem number do not have to be in the mated application table when the ent-gtt command is executed if these parameters are specified with the ent-gtt command.

  • ri=gt
  • xlat=dpcssn and ri=ssn

If the point code and subsystem, if applicable, are not in the mated application table when either of these parameters are specified with the ent-gtt command, the EAGLE creates a solitary mated application in the mated application table using the point code and subsystem values specified in the ent-gtt command.

If the xlat=dpcssn parameter is specified, the ssn parameter must be specified. Otherwise, the ssn parameter cannot be specified.

If a point code is the STP’s True PC, then the value of the XLAT parameter must be set to DPCSSN and the value of the RI parameter must be set to SSN. If the SSN parameter is specified and a point code is the STP’s True PC, then the subsystem number specified must exist in the SS-APPL table. This can be verified with the rtrv-ss-appl command. To execute the rtrv-ss-appl command, one or more features shown in Table 3-4 must be enabled, and turned on if necessary. The rtrv-ctrl-feat output shows the required status of the features.

Table 3-4 Feature Status

Feature Feature's Status Entry Displayed in the rtrv-ctrl-feat Output
LNP Enabled The entry LNP TNs with a quantity greater than zero (0)
EIR Enabled and Turned On EIR
INP Enabled and Turned On INP
ANSI-41 INP Query Enabled and Turned On ANSI-41 INP Query
V-Flex Enabled and Turned On VFLEX
ATINP Enabled ATINP
ANSI41 AIQ Enabled ANSI41 AIQ

The point code specified in the ent-gtt command must be defined in the routing table or be the EAGLE’s point code. For ANSI point codes (pc/pca), the point code specified in the ent-gtt command, must be a full point code. That point code can be defined as a full point code in the destination point code table, or can be a member of a cluster point code defined in the destination point code table. Cluster point codes or a network routing point codes cannot be specified with this command. Enter the rtrv-rte command to verify that the point code is in the routing table. If the point code is not defined as a route, perform one of the Adding a Route procedures in Database Administration – SS7 User's Guide to define the point code as a route.

If the EAGLE’s point code is specified with the ent-gtt command, then the xlat=dpcssn and ri=ssn parameters must be specified. The EAGLE’s point code is shown in the PCA, PCI, PCN, or PCN24 fields of the rtrv-sid command output.

If the xlat=dpcngt parameter is specified, the ngt parameter and the ri=gt parameters must be specified.

An ANSI point code or ITU international point code containing all zeros is not a valid point code and cannot be entered into the database. An ITU national point code containing all zeros is a valid point code and can be entered into the database.

Either the type parameter or the ttn parameter must be specified.

If the type parameter is specified, the translation type must be in the database. This can be verified with the rtrv-tt command.

If the type parameter is not specified, the translation type name must be assigned to a translation type in the database. This can be verified with the rtrv-tt command.

If the type and ttn parameters are specified, the specified translation type must be in the database and the specified translation type name must be assigned to the translation type.

If the translation type is ANSI (type or typea), the pc type must be ANSI (pc or pca). If the translation type is one of the ITU types (typei, typen,typeis, typens, or typen24) the pc type may be either of the ITU types (pci, pcn, or pcn24). If the ANSI/ITU SCCP Conversion feature is enabled, the domain (ANSI or ITU) of the translation type and point code do not have to be the same.

The end global title address (egta) must be greater than or equal to the start global title address (gta) and its length must be equal to the start global title address.

If the Variable-Length Global Title Translation (VGTT) feature is off, shown the entry VGTT = off, the global title address length must be equal to the number of digits specified by the given translation type. The length of the global title address can be verified with the rtrv-tt command.

If the Variable-Length Global Title Translation (VGTT) feature is on, shown the entry VGTT = on, up to 10 different length global title addresses can be assigned to a translation type. If the Activating the Support for 16 GTT Lengths in VGTT feature is enabled and on, shown the entry VGTT with 16 GTT lengths in the rtrv-ctrl-feat output, up to 16 different length global title addresses can be assigned to a translation type. The length of the global title address is only limited by the range of values for the gta and egta parameters, one to 21 digits, and by the global title addresses already assigned to the translation type. The ndgt parameter of the ent-tt command has no effect on the length of the global title address. As global title addresses of different lengths are assigned to a specific translation type, these lengths are displayed in the NDGT field of the rtrv-tt command output.

If the translation type has maximum number of different length global title addresses assigned to it, and another global title address is specified for the translation type, the length of the global title address being added to the translation type must be the same as one of the lengths already assigned to the translation type. If the length of the global title address does not match one of the lengths already assigned to the translation type, the ent-gtt command is rejected with this message.

E4007 Cmd Rej: Exceeding max GTA Lengths supported per TT

If the translation type has less than the maximum number of different length global title addresses assigned to it, and another global title address is specified for the translation type, the length of the global title address can be from one to 21 digits and does not have to match the length of the other global title addresses assigned to the translation type.

Refer to Variable-length Global Title Translation Feature for more information about this feature.

The range, as specified by the start and end global title addresses, cannot already exist in the global title translation data for the specified translation type. If the ranges overlap, the range of global title addresses cannot be split and the ent-gtt command is rejected with this message.

E2401 Cmd Rej:GTA range overlaps a current range. GTA range overlaps a current range

Along with error message 2401, a list of the overlapped global title addresses is displayed as shown in the following example.

rlghncxa03w 07-02-24 08:29:15 GMT EAGLE5 35.6.0
The following GTA ranges overlap the input GTA range

START GTA               END GTA
8005550000              8005551999
8005552000              8005553999
8005554000              8005555999

ENT-GTT: MASP A - Command Aborted

Table 3-5 shows the valid combinations for the parameters. All other combinations are rejected.

Table 3-5 Valid Parameter Combinations for the ent-gtt Routing Parameters

XLAT Value RI Value Routing Action SSN Value
DPC GT Translate DPC only and route on GT Cannot specify
DPC SSN Translate DPC only and route on SSN Cannot specify
DPCSSN GT Translate DPC and SSN and route on GT Must specify
DPCSSN SSN Translate DPC and SSN and route on SSN Must specify
DPCNGT GT Translate New GT and route on GT Cannot specify

The EAGLE can contain 269,999, 400,000, or 1,000,000 global title translations. The system default is 269,999 global title translations. This quantity can be increased to 400,000 by enabling the feature access key for part number 893-0061-01, or to 1,000,000 by enabling the feature access key for part number 893-0061-10. For more information on enabling these feature access keys, perform the Enabling the XGTT Table Expansion Feature procedure.

Canceling the RTRV-GTT Command

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-gtt command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-gtt command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-gtt command was entered, from another terminal other that the terminal where the rtrv-gtt command was 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 translation types in the database using the rtrv-tt command. This is an example of the possible output.
    rlghncxa03w 10-07-25 09:42:31 GMT  EAGLE5 42.0.0
    TYPEA      TTN        NDGT
    1          lidb       5
    2          c800       10
    3          d700       6
    5          scp1       6
    10         scp2       6
    15         scp3       3
    
    ALIAS      TYPEA
    30         5
    40         10
    50         3
    65         3
    
    TYPEI      TTN        NDGT
    105        itudb      8
    
    ALIAS      TYPEI
    7          105
    
    TYPEN      TTN        NDGT
    120        dbitu      7
    
    ALIAS      TYPEN
    8          120
    
    TYPEIS     TTN        NDGT
    
    ALIAS      TYPEIS
    
    TYPENS     TTN        NDGT
    
    ALIAS      TYPENS

    If the required translation type is shown in the rtrv-tt output, continue the procedure with 2.

    If the required translation type is not shown in the rtrv-tt output, perform the Adding a Translation Type procedure to add the translation type to the database. After the translation type has been added, continue the procedure with 10.

  2. Verify that the EGTT feature is on, by entering the rtrv-feat command. If the GTT feature is on, the EGTT field should be set to on.

    Note:

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

    If the EGTT feature is off, continue the procedure with 5.

    If the EGTT feature is on, continue the procedure with 3.

  3. Display the features that are enabled by entering the rtrv-ctrl-feat command.

    The following is an example of the possible output.

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    HC-MIM SLK Capacity       893012707  on      64
    
    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.
  4. Display the GTT selectors in the database by entering the rtrv-gttsel command with the TTN value associated with the translation type that will be assigned to the global title translation. The TTN value is shown in the rtrv-tt output in 1.

    To specify of the TTN value, the parameters shown in Table 3-6 must be specified with the rtrv-gttsel command. The parameters that can be specified are dependent on the features that are enabled, shown in 3.

    Table 3-6 RTRV-GTTSEL Parameters

    Feature that is Enabled Parameter that must be Specified for the TTN Value
    Neither the Origin Based SCCP Routing nor the Flexible Linkset Optional Based Routing, shown as Flex Lset Optnl Based Rtg in thertrv-ctrl-feat output, is enabled. gttsn
    Origin Based SCCP Routing cdgtasn,cggtasn
    Flexible Linkset Optional Based Routing cdgttsn,cggttsn

    For this example, enter these commands.

    rtrv-gttsel:gttsn=scp1

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    
    GTIA    TT     NP      NAI  SELID GTTSN
     2       5     --      ---  none  scp1
    GTII    TT     NP      NAI  SELID GTTSN
    
    GTIN    TT     NP      NAI  SELID GTTSN
    
    GTIN24  TT     NP      NAI  SELID GTTSN
    
    GTIIS   TT     NP      NAI  SELID GTTSN
    
    GTINS   TT     NP      NAI  SELID GTTSN

    rtrv-gttsel:gttsn=scp2

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    
    GTIA    TT     NP      NAI  SELID GTTSN
     2      10     --      ---  none  scp2
    GTII    TT     NP      NAI  SELID GTTSN
    
    GTIN    TT     NP      NAI  SELID GTTSN
    
    GTIN24  TT     NP      NAI  SELID GTTSN
    
    GTIIS   TT     NP      NAI  SELID GTTSN
    
    GTINS   TT     NP      NAI  SELID GTTSN

    rtrv-gttsel:gttsn=scp3

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    
    GTIA    TT     NP      NAI  SELID GTTSN
     2      15     --      ---  none  scp3
    GTII    TT     NP      NAI  SELID GTTSN
    
    GTIN    TT     NP      NAI  SELID GTTSN
    
    GTIN24  TT     NP      NAI  SELID GTTSN
    
    GTIIS   TT     NP      NAI  SELID GTTSN
    
    GTINS   TT     NP      NAI  SELID GTTSN

    If any of the entries shown in the rtrv-gttsel output do not have the default values for the advanced GTT parameters, or if a GTT selector entry with the TTN value was removed with the dlt-gttsel command, the remainder of this procedure cannot be performed. Choose another translation type to assign to the global title translation and repeat this procedure from 1.

    If all of the entries shown in the rtrv-gttsel output have the default values for the advanced GTT parameters, and none of the GTT selector entries with the TTN value were removed with the dlt-gttsel command, continue the procedure with 5.

  5. Continue the procedure by performing one of these steps to verify if the VGTT or the Support for 16 GTT Lengths in VGTT features can be used to provision the global title translation.
    If multiple values are shown in the NDGT column for any translation type entry, the Variable-Length Global Title Translation feature is turned on. If a translation type entry contains 11 - 16 values in the NDGT column, the Support for 16 GTT Lengths in VGTT feature is enabled and turned on.
    • If no more than 10 values are shown in the NDGT column for any translation type, continue the procedure by performing one of these steps.
      • If the translation type will contain no more than 10 different length global title addresses, continue the procedure with 10.
      • If the translation type will contain more than 10 different length global title addresses, continue the procedure with 9.
    • If more than 10 values are shown in the NDGT column for any translation type, continue the procedure with 10.
    If only single values are shown in the NDGT column for all the translation type entries, continue the procedure by performing one of these steps.
    • If the translation type will contain global title addresses of only one length, continue the procedure with 10.
    • If the translation type will contain multiple lengths of global title addresses, continue the procedure with 6.
  6. Verify that the VGTT feature is on, by entering the rtrv-feat command. If the VGTT feature is on, the VGTT field should be set to on. For this example, the VGTT feature is off.

    Note:

    Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, see thertrv-feat command description in Commands User's Guide.
    Continue the procedure by performing one of these steps.
    • If the VGTT feature is on, continue the procedure by performing one of these steps.
      • If the translation type will contain no more than 10 different length global title addresses, continue the procedure with 10.
      • If the translation type will contain more than 10 different length global title addresses, continue the procedure with 9.
    • If the VGTT feature is off, continue the procedure with 7.
  7. Display the cards in the EAGLE using the rtrv-card command. This is an example of the possible output.
    rlghncxa03w 13-05-25 09:58:31 GMT EAGLE5 45.0.0
    CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
    1102   TSM       GLS       
    1113   E5MCAP    EOAMHC
    1114   E5TDM-A
    1115   E5MCAP    EOAMHC
    1116   E5TDM-B
    1117   E5MDAL
    1118   RESERVED
    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
    1216   DCM       STPLAN    
    1308   LIMDS0    SS7ANSI   sp6           A    1   sp7           B    0
    1314   LIMDS0    SS7ANSI   sp7           A    1   sp5           B    1
    1317   DCM       STPLAN

    The correct service modules must be in the EAGLE before the VGTT feature can be turned on, or the Support for 16 GTT Lengths in VGTT feature can be enabled and turned on. See the Adding a Service Module procedure to determine the service modules that are required. If any service modules must be replaced, contact the Customer Care Center before replacing any service modules. Refer to My Oracle Support (MOS) for the contact information.

  8. Turn the Variable-length Global Title Translation (VGTT) feature on by entering this command.

    chg-feat:vgtt=on

    Note:

    Once the Variable-length Global Title Translation (VGTT) feature is enabled with thechg-feat command, it cannot be disabled.

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

    When the chg-feat has successfully completed, this message should appear.

    rlghncxa03w 09-05-25 09:57:41 GMT EAGLE5 41.0.0
    CHG-FEAT: MASP A - COMPLTD
    Continue the procedure by performing one of these steps.
    • If the translation type will contain no more than 10 different length global title addresses, continue the procedure with 10.
    • If the translation type will contain more than 10 different length global title addresses, perform the Activating the Support for 16 GTT Lengths in VGTT Feature procedure to enable and turn on the Support for 16 GTT Lengths in VGTT feature. After the Support for 16 GTT Lengths in VGTT feature has been enabled and turned on, continue the procedure with 10.
  9. Display the status of the Support for 16 GTT Lengths in VGTT feature by entering this command.

    rtrv-ctrl-feat:partnum=893024801

    rlghncxa03w 09-05-25 09:57:41 GMT EAGLE5 41.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    VGTT with 16 GTT lengths  893024801 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 Support for 16 GTT Lengths in VGTT feature is enabled and turned on, continue the procedure with 10.

    If the Support for 16 GTT Lengths in VGTT feature is not enabled or turned on, perform the Activating the Support for 16 GTT Lengths in VGTT Feature procedure to enable and turn on the Support for 16 GTT Lengths in VGTT feature. After the Support for 16 GTT Lengths in VGTT feature has been enabled and turned on, continue the procedure with 10.

  10. Display the global title translations in the database using the rtrv-gtt command specifying a translation type (type), translation type name (ttn), or both from the rtrv-tt command output shown in 1 along with the desired global title address (gta). If a range of global title addresses will be specified for the global title translation, the egta parameter can be specified with the rtrv-gtt command. For this example, enter these commands.

    rtrv-gtt:typea=5:gta=910460

    rtrv-gtt:typea=10:gta=615370:egta=615380

    rtrv-gtt:typea=15:gta=800:egta=900

    To add a global title translation, the desired global title addresses cannot be in the database. If the global title addresses are not in the database, the rtrv-gtt command is rejected with the following message.

    E2405 Cmd Rej: GTA does not exist in any range
  11. The global title translation cannot be added to the database if the database contains the maximum number of global title translations the EAGLE is allowed to have. The maximum number of global title translations is shown in the rtrv-gtt output in 10 or the rtrv-ctrl-feat output.

    If error message E2405 was displayed in the output in 10, enter the rtrv-ctrl-feat command to verify the maximum number of global title translations that are allowed in the database.

    If the 3 was performed, this step does not need to be performed.

    The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    HC-MIM SLK Capacity       893012707  on      64
    
    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.
  12. Continue the procedure by performing these steps based the XGTT Table Expansion entry that is shown in the rtrv-ctrl-feat output in either 3 or 11.

    Note:

    If the entryXGTT Table Expansion is not shown in thertrv-ctrl-feat output, the maximum number of global title addresses that the database can contain is 269,999.

    If the maximum number of global title translations is 1,000,000, and adding the global title translation will exceed 1,000,000 global title translations, the new global title translation cannot be added and the remainder of this procedure cannot be performed.

    If the maximum number of global title translations is either 269,999 or 400,000 and adding the global title translation will exceed the maximum number of global title translations, perform the Enabling the XGTT Table Expansion Feature procedure to enable XGTT Table Expansion feature for either 400,000 or 1,000,000 global title translations as needed.

    If adding the global title translation will not exceed the maximum number of global title translations, or if the Enabling the XGTT Table Expansion Feature procedure was performed in this step, continue the procedure by performing one of these steps.
    • If the gtmodid parameter will be specified for the global title translation, continue the procedure with 13.
    • If the cggtmod=yes parameter will be specified for the global title translation and the gtmodid parameter will not be specified for the global title translation, continue the procedure with 14.
    • If the gtmodid and cggtmod=yes parameters will not be specified for the global title translation, continue the procedure with 15.
  13. Display the GT modification information in the database using the rtrv-gtmod command.

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:29:31 GMT EAGLE5 42.0.0
    
    GTMODID   NTT  NGTI  GT0FILL  NNP  NNAI  NPDD  NSDD  PRECD  CGPASSN
    modid2     --     2       ON   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid5     --     2      OFF   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid6     --     4       ON    4     5     3     3    SFX       --
          NPDS=123                    NSDS=456
    modid10    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    modid11    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    
    
    GTMOD table is (5 of 100000) 1% full.

    If the desired GT modification entry is not displayed, perform the Adding Global Title Modification Information procedure to add the desired GT modification entry to the database.

    If the desired GT modification entry is displayed or the Adding Global Title Modification Information procedure was performed, continue the procedure by performing one of these steps.
    • If the cggtmod=yes parameter will be specified for the global title translation and the gtmodid parameter will not be specified for the global title translation, continue the procedure with 14.
    • If the cggtmod=yes parameter will not be specified for the global title translation, continue the procedure with 15.
  14. To specify the cggtmod=yes parameters in this procedure, one of these the Advanced GT Modification features must be enabled.
    • AMGTT - 893021801
    • AMGTT CgPA Upgrade - 893021803

    If the rtrv-ctrl-feat command was performed in 3 or 11, and the appropriate AMGTT entry is shown in the rtrv-ctrl-feat output, continue the procedure with 15.

    If the rtrv-ctrl-feat command was not performed in 3 and 11, enter the rtrv-ctrl-feat command to verify the status of the Advanced GT Modification feature.

    The following is an example of the possible output.

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    IPGWx Signaling TPS       893012814  on      20000
    ISUP Normalization        893000201  on      ----
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    HC-MIM SLK Capacity       893012707  on      64
    
    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 appropriate Advanced GT Modification feature is not shown in the rtrv-ctrl-feat output in this step, 3 or 11, perform the Activating the Advanced GT Modification Feature procedure to enable the appropriate Advanced GT Modification feature. After the Advanced GT Modification feature has been enabled, continue the procedure with 15.

  15. A loopset can be assigned to the global title translation to determine if SCCP messages are being looped. The loopset parameter is used to assign a loopset to a global title translation. To assign a loopset to the global title translation, the SCCP Loop Detection feature must be enabled.

    Note:

    If you do not wish to specify theloopset parameter with theent-gtt command, continue the procedure with 17.

    If the SCCP Loop Detection feature is enabled, the LOOPSET field is shown in the rtrv-gtt output, and the entry SCCP Loop Detection is shown in the rtrv-ctrl-feat output.

    If the LOOPSET field is shown in the rtrv-gttoutput in 10, continue the procedure with 16.

    If error message E2405 is displayed in the rtrv-gttoutput in 10, enter the rtrv-ctrl-feat command with the SCCP Loop Detection feature part number to verify the status of the SCCP Loop Detection feature. Enter this command.

    rtrv-ctrl-feat:partnum=893016501

    The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum     Status  Quantity
    SCCP Loop Detection       8930165101  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 SCCP Loop Detection feature is enabled, continue the procedure with 16.

    If the LOOPSET field does not appear in the rtrv-gttoutput in 10, or the rtrv-ctrl-feat output shows that the SCCP Loop Detection feature is not enabled, perform the Activating the SCCP Loop Detection Feature procedure to enable the SCCP Loop Detection feature. After the SCCP Loop Detection feature has been enabled, perform the Adding a Loopset procedure to add the required loopset. After the loopset has been added, continue the procedure with 17.

  16. Display all the loopsets in the database by entering this command

    rtrv-loopset:num=1000:force=yes

    This is an example of the possible output.

    LoopSet            Mode          Point Codes
    ====================================================================
    cary2             notify         005-015-005     007-007-007 (ANSI)
                                     033-004-003     033-007-003
                                     005-027-005     007-004-007
    cary4             notify         005-012-005     007-026-007 (ANSI)
                                     003-049-003     033-002-003
                                     005-008-055     007-014-007
    apex3             discard        005-017-008     007-017-009 (ANSI)
                                     033-005-043     005-014-005
                                     005-017-005     007-014-007
                                     033-002-043     005-038-005
                                     007-009-027     033-003-043
                                     005-012-005     007-002-027
    apex4             discard        005-007-008     027-007-009 (ANSI)
                                     033-005-003     005-004-055
                                     027-001-007     033-008-003
                                     033-007-003     005-003-055
                                     027-008-007
    ral5              notify         005-005-005     007-007-007 (ANSI)
                                     003-004-003     003-001-003
                                     005-007-005     007-004-007
                                     003-002-003     005-008-005
                                     007-009-007     003-003-003
                                     005-002-005     007-002-007
    ral6              notify         005-007-008     007-007-009 (ANSI)
                                     003-005-003     003-007-003
                                     005-007-005
    dunn1             discard        005-002-055     007-051-007 (ANSI)
                                     003-008-033
    rtp9              discard        005-002-005     007-001-007 (ANSI)
                                     003-008-003     003-007-003
                                     005-003-005     007-008-007
                                     005-004-005
    rtp5              discard        005-007-008     007-007-009 (ANSI)
                                     003-005-003
    rtp1              discard        005-005-005     007-007-007 (ANSI)
                                     003-004-003     003-007-003
                                     005-007-005     007-004-007
                                     005-004-005
    rtp2              notify         005-007-008     007-007-009 (ANSI)
                                     003-005-003
    
    
    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    LOOPSET table is (11 of 1000) 1% full
    RTRV-LOOPSET: MASP A - COMPLTD

    Note:

    If thertrv-loopset command is entered with no other parameters specified, a maximum of 50 entries are displayed. To display more than 50 entries, theforce=yesparameter must be specified with thertrv-loopset command and the num parameter value must be greater than 50. Since there can be a maximum of 1000 loopsets in the database, to display all the loopsets in the database, theforce=yes andnum = 1000parameters must be specified with thertrv-loopset command.

    If the required loopset is shown in the rtrv-loopset output, continue the procedure with 17.

    If the required loopset is not shown in the rtrv-loopset output, perform the Adding a Loopset procedure to add the required loopset. After the loopset has been added, continue the procedure with 17.

  17. Hexadecimal digits (0-9, a-f, A-F) can be specified as values for the gta or egta parameters only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature by entering the rtrv-ctrl-feat command with the Hex Digit Support for GTT feature part number.

    Note:

    If hexadecimal digits are shown in thertrv-gtt output in 10, or if hexadecimal digits will not be specified for thegta oregta parameters in this procedure, continue the procedure with 18.

    Enter this command.

    rtrv-ctrl-feat:partnum=893018501

    The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    
    The following features have been permanently enabled:
    
    Feature Name              Partnum      Status     Quantity
    Hex Digit Support for GTT 893018501      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 Hex Digit Support for GTT feature has not been enabled, perform the Activating the Hex Digit Support for GTT Feature procedure to enable this feature. After the Hex Digit Support for GTT feature is enabled, continue the procedure with 18.

  18. Verify that the ANSI/ITU SCCP Conversion feature is enabled by entering the rtrv-ctrl-feat:partnum=893012001 command. The following is an example of the possible output.
    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    The following features have been permanently enabled:
    Feature Name       Partnum       Status       Quantity
    SCCP Conversion    893012001       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 ANSI/ITU SCCP Conversion feature is not enabled, perform the Activating the ANSI/ITU SCCP Conversion Feature procedure to enable the ANSI/ITU SCCP Conversion feature.

    Note:

    If the domain (ANSI or ITU) of the point code and the translation type assigned to the global title translation will be different, and thengti parameter will be specified with the global title translation, theANSI/ITU SCCP Conversion feature (SCCP Conversion) must be enabled. If the ANSI/ITU SCCP Conversion feature is not being used, or if thertrv-ctrl-feat output in this step shows that theANSI/ITU SCCP Conversion feature is enabled, continue the procedure with 19.
  19. To use either the mrnset parameter (if the routing indicator value for the global title translation is GT) or mapset parameter (if the routing indicator value for the global title translation is SSN), the Flexible GTT Load Sharing feature must be enabled.

    If the Flexible GTT Load Sharing feature is enabled, either the mrnset or mapset parameters, depending on the routing indicator value for the global title translation being added in this procedure, must be specified with the ent-gtt command.

    Verify that the Flexible GTT Load Sharing feature is enabled by entering this command.

    rtrv-ctrl-feat:partnum=893015401

    The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    
    The following features have been permanently enabled:
    
    Feature Name               Partnum      Status       Quantity
    Flexible GTT Load Sharing 893015401      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 routing indicator for the global title translation being added is GT, there are three actions that can be taken.
    • If the Flexible GTT Load Sharing feature is not enabled, and you do not wish to specify the mrnset parameter for the global title translation, continue the procedure with 20.
    • If the Flexible GTT Load Sharing feature is not enabled, and you do wish to specify the mrnset parameter for the global title translation, perform the Activating the Flexible GTT Load Sharing Feature procedure to enable the Flexible GTT Load Sharing feature. After enabling the Flexible GTT Load Sharing feature, continue the procedure with 23.
    • If the Flexible GTT Load Sharing feature is enabled, continue the procedure with 23.

    If the routing indicator for the global title translation being added is SSN, there are three actions that can be taken:

    • If the Flexible GTT Load Sharing feature is not enabled, and you do not wish to specify the mapset parameter for the global title translation, continue the procedure with one of these steps.
      • If the point code value is the EAGLE’s point code, continue the procedure with 2424.
      • If the point code value is a value other than the EAGLE’s point code, the ri parameter value will be ssn, and the xlat parameter value will be dpc, continue the procedure with 26.
      • If the point code value is a value other than the EAGLE’s point code, the ri parameter value will be ssn, and the xlat parameter value will be dpcssn when this procedure is completed, continue the procedure with 26.
    • If the Flexible GTT Load Sharing feature is not enabled, and you do wish to specify the mapset parameter for the global title translation, perform the Activating the Flexible GTT Load Sharing Feature procedure to enable the Flexible GTT Load Sharing feature. After enabling the Flexible GTT Load Sharing feature, continue the procedure with one of these steps.
      • If the point code value is the EAGLE’s point code, continue the procedure with 24.
      • If the point code value is a value other than the EAGLE’s point code, or the xlat parameter value will be dpc, continue the procedure with 26.
    • If the Flexible GTT Load Sharing feature is enabled, perform one of these steps.
      • If the point code value is the EAGLE’s point code continue the procedure with 24.
      • If the point code value is a value other than the EAGLE’s point code, or the xlat parameter value will be dpc, continue the procedure with 26.
  20. 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 one of the Adding a Route procedures in Database Administration - SS7 User's Guide to add the required route to the database. After the route has been added, continue the procedure with 27.

  21. Display the point code that will be assigned to the global title translation 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 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 20 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 point code to the destination point code table.

  22. The point code specified with the ent-gtt command must be the DPC of a route, unless the point code is the EAGLE’s point code. Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the ent-gtt command to verify whether or not the point code is the DPC of a route.

    For this example, enter these commands.

    rtrv-rte:dpca=007-007-007

    This is an example of the possible output.

    rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
       DPCA       ALIASI     ALIASN/N24     LSN        RC      APCA
    007-007-007  --------   -----------     ls03       10    007-007-007
                                            ls02       30    150-150-150
                                            lsa2       50    200-200-200
                                                   RTX:No  CLLI=ls03clli

    rtrv-rte:dpca=003-003-003

    This is an example of the possible output.

    rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
       DPCA        ALIASI     ALIASN/N24    LSN        RC    APCA
    003-003-003   --------    ----------    ls02       10    002-002-002
                                            ls08       30    025-025-150
                                            lsa5       50    066-030-100
                                                   RTX:No  CLLI=ls07clli

    rtrv-rte:dpca=005-005-005

    This is an example of the possible output.

    rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
        DPCA       ALIASI     ALIASN/N24    LSN     RC         APCA
    005-005-005    ------    -----------    ls05    10    005-005-005
                                            ls15    30    089-047-123
                                            lsa8    50    077-056-000
                                                   RTX:No  CLLI=ls05clli

    If the point code is not shown in the rtrv-rte output, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database.

  23. The point code and MRN set ID specified for the global title translation must be shown in the rtrv-mrn command output. The point code must be assigned to the MRN set that will be assigned to the global title translation.

    Enter the rtrv-mrn command to verify that the required MRN set is configured in the database, and that the required point code is assigned to the MRN set. The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    
    MRNSET   PC             RC
    DFLT     001-001-001    10
             001-001-002    20
             001-001-003    30
    
    MRNSET   PC             RC
    110      001-001-001    10
             001-001-005    20
             001-001-006    30
             001-001-003    40
             001-001-008    50
    
    MRNSET   PC             RC
    111      001-001-001    30
             001-001-005    30
             001-001-006    30
             001-001-003    30
             001-001-008    30
    
    MRNSET   PC             RC
    112      001-003-001    10
             001-003-002    10
             001-003-003    30
             001-003-004    30
             001-003-006    60
             001-003-007    60
             001-003-008    80
             001-003-009    80
    
    MRNSET   PCN               RC
    113      s-1-1-1-0123-aa   1
             s-1-1-1-0235-aa   2
             s-1-1-1-0235-aa   3

    Note:

    If theWeighted GTT Load Sharing feature is enabled, theWT, %WT, andTHR columns are shown in thertrv-mrn output

    If the required MRN set is not shown in the rtrv-mrn output, or if the required point code is not assigned to the required MRN set, provision the required MRN set by performing the Provisioning MRN Entries procedure. After provisioning the required MRN set, continue the procedure with 27.

    If the required MRN set is shown in the rtrv-mrn output, or if the required point code is assigned to the required MRN set, continue the procedure with 27.

    Note:

    If the EAGLE’s point code is not going to used for thepc parameter of theent-gtt command, continue the procedure with 26.
  24. If the ri=ssn and xlat=dpcssn parameters are specified with the ent-gtt command, and you wish to use the EAGLE’s point code for the value of the pc parameter of the ent-gtt command, the point code value must be in the EAGLE’s self ID table. Display the EAGLE self-identification, using the rtrv-sid command.

    This is an example of the possible output.

    rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0
    
    PCA               PCI          PCN           CLLI         PCTYPE
    010-020-030     1-023-1      12-0-14-1     rlghncxa03w    OTHER
                  s-1-023-1    s-12-0-14-1
    
    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       050-060-070
       
    CPCI
    1-001-1           1-001-2           1-001-3          1-001-4
    1-002-1           1-002-2           1-002-3          1-002-4
    2-001-1           7-222-7
       
    CPCN
    2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
    2-2-3-3           2-2-4-0           10-14-10-1
  25. Enter the rtrv-ss-appl command to verify that either the LNP, EIR, V-Flex, ATINPQ, INP, or AIQ subsystem number (depending on which feature is on) is in the subsystem application table.

    This is an example of the possible output.

    rlghncxa03w 09-05-28 14:42:38 GMT EAGLE5 41.0.0
    APPL       SSN       STAT
    LNP        254       ONLINE
    
    SS-APPL table is 20% FULL (1 of 5)

    If the subsystem number is shown in the rtrv-ss-appl output, go to 26. If no subsystem number is shown in the rtrv-ss-appl output, or if the rtrv-ss-appl command is rejected, go to one of these User's Guides, depending on the type of subsystem you wish to use, to enable and turn on the feature as necessary, and add the subsystem to the subsystem application table:

    • EIR subsystem – go to EIR User's Guide.
    • INP subsystem – go to INP/AINPQ User's Guide.
    • LNP subsystem – go to ELAP Administration and LNP Feature Activation Guide.
    • V-Flex subsystem – go to V-Flex User's Guide.
    • ATINPQ subsystem – go to ATINP User's Guide.
    • AIQ subsystem – go to Analyzed Information Features User's Guide.

    Note:

    If the Flexible GTT Load Sharing feature is enabled, shown in 19, a MAP set ID must be specified for the final global title translation. The point code and SSN specified for the final global title translation being added in this procedure must be assigned to the MAP set ID that will be assigned to the final global title translation. Perform 26 to verify that the required MAP set is configured in the database.

    Note:

    If the Flexible GTT Load Sharing feature is not enabled, and theri=ssn andxlat=dpc parameters are not being specified with theent-gtt command, or if the EAGLE’s true point code and the EAGLE’s subsystem number, along with theri=ssn andxlat=dpcssn parameters, are not being specified with theent-gtt command, continue the procedure with 27.
  26. Enter the rtrv-map command with the pc parameter specifying the required point code to verify that the required data is in the mated application table.

    For this example enter this command.

    rtrv-map:pca=005-005-005

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

    rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0
    
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       005-005-005                  250 10  SOL *Y  *Y  GRP01     ON
    
    
    MAP table is (37 of 1024) 4% full.

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

    rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0
    
       MAPSET ID=DFLT
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       005-005-005                   55  5  DOM YES YES -------- OFF
                      001-001-002    15 15  DOM YES YES -------- ON
                      001-001-003    25 20  DOM YES YES -------- ON
                      001-001-002    40 35  DOM YES YES -------- OFF
    
       MAPSET ID=1
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       005-005-005                   50  5  DOM YES YES -------- OFF
                      001-001-002    10 15  DOM YES YES -------- ON
                      001-001-003    20 20  DOM YES YES -------- ON
                      001-001-002    40 35  DOM YES YES -------- OFF
    
       MAPSET ID=    2
       005-005-005                    5 10  SOL *Y  *Y  -------- OFF
    
    MAP table is (12 of 36000) 1% full.

    If the ri=ssn and xlat=dpc parameters are being specified with the ent-gtt command, the point code must be in the mated application table. If the point code is not in the mated application table when the ent-gtt command is executed, the force=yes parameter must be specified with the ent-gtt command.

    If the EAGLE’s true point code and the EAGLE’s subsystem number, along with the ri=ssn and xlat=dpcssn parameters are being specified with the ent-gtt command, the EAGLE’s true point code and the EAGLE’s subsystem number must be in the mated application table.

    If the required point code, subsystem number, or MAP set ID is not shown in the rtrv-map output, perform one of these procedures to add the required information to the mated application table.

  27. Add the global title translation to the database using the ent-gtt command using the parameter combinations shown in Table 3-7.

    For this example, enter these commands.

    ent-gtt:typea=5:gta=910460:egta=919460:xlat=dpcngt:ri=gt :pca=007-007-007:ttn=scp1:mrnset=114:cggtmod=yes:gtmodid=modid2

    ent-gtt:typea=10:gta=615370:egta=615380:xlat=dpcssn:ri=ssn :pca=003-003-003:ssn=254:ttn=scp2:mapset=3

    ent-gtt:typea=15:gta=800:egta=900:xlat=dpc:ri=ssn:pca=005-005-005 :ttn=scp3:mapset=1:loopset=rtp:cggtmod=yes

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

    rlghncxa03w 09-05-07 11:44:13 GMT  EAGLE5 41.0.0
    ENT-GTT:  MASP A - COMPLTD

    Note:

    The command line on the terminal can contain up to 150 characters. If the parameters and values specified with theent-gtt command are too long to fit on theent-gtt command line, perform the Changing a Global Title Translationprocedure to complete adding the GTT entry.

    Table 3-7 Add GTT Parameter Combinations

    RI = GT XLAT= DPCNGT RI = GT XLAT= DPCSSN RI = GT XLAT= DPC RI = SSN XLAT= DPCSSN RI = SSN XLAT= DPC
    Mandatory Parameters

    TYPE/TYPEA/

    TYPEI/TYPEN/

    TYPEIS/TYPENS/

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN/

    TYPEIS/TYPENS/

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN/

    TYPEIS/TYPENS/

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN/

    TYPEIS/TYPENS/

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN/

    TYPEIS/TYPENS/

    TYPEN24 (See Notes 2 and 3)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 8)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 8)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 8)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 8)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 8)

    GTA (See Notes 4, 5, 6, 12, 14, and 16) GTA (See Notes 4, 5, 6, 12, 14, and 16) GTA (See Notes 4, 5, 6, 12, 14, and 16) GTA (See Notes 4, 5, 6, 12, 14, and 16) GTA (See Notes 4, 5, 6, 12, 14, and 16)
      SSN   SSN  
    Optional Parameters
    TTN (See Notes 14, 15, and 16) TTN (See Notes 14, 15, and 16) TTN (See Notes 14, 15, and 16) TTN (See Notes 14, 15, and 16) TTN (See Notes 14, 15, and 16)
    EGTA(See Note 17) EGTA (See Note 17) EGTA (See Note 17) EGTA (See Note 17) EGTA (See Note 17)
    GTMODID (See Note 18) GTMODID (See Note 18) GTMODID (See Note 18) GTMODID (See Note 18) GTMODID (See Note 18)
    MRNSET (See Note 9) MRNSET (See Note 9) MRNSET (See Note 9) MAPSET (See Note 11) MAPSET (See Note 11)
    LOOPSET (See Note 13) LOOPSET (See Note 13) LOOPSET (See Note 13) LOOPSET (See Note 13) LOOPSET (See Note 13)
    CGGTMOD (See Note 7) CGGTMOD (See Note 7) CGGTMOD (See Note 7) CGGTMOD (See Note 7) CGGTMOD (See Note 7)
            FORCE (See Note 10)
    NTT (See Note 19)
    Parameter Values:

    TYPE/TYPEA/TYPEI/TYPEN/TYPEIS/TYPENS/TYPEN24 – The translation type from the TYPE/TYPEA/TYPEI/TYPEN/TYPEIS/TYPENS/TYPEN24 column of the rtrv-tt output. See Note 2.

    TTN – The translation type name from the TTN column of the rtrv-tt output.

    GTA – 1 - 21 digits or 1 - 21 hexadecimal digits

    PC/PCA/PCI/PCN/PCN24 – See Note 1

    SSN – 0 - 255

    EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits. Default = same as the GTA value

    FORCE – yes, no. Default = no

    LOOPSET – Loopset name from the rtrv-loopset output

    GTMODID – GT modification identifier from the rtrv-gtmod output

    MRNSET – MRN set ID from the rtrv-mrn output

    MAPSET – MAP set ID from the rtrv-map output

    CGGTMOD – yes, no. Default = no

    Notes:

    1. The pc/pca/pci/pcn/pcn24 parameters are used to assign either ANSI, ITU-I, ITU-I spare, 14-bit ITU-N, 14-bit ITU-N spare, or 24-bit ITU-N point codes to the global title translation (GTT).
      • pc/pca = ANSI point code
      • pci = ITU-I or ITU-I spare point code
      • pcn = 14-bit ITU-N or 14-bit ITU-N spare point code
      • pcn24 = 24-bit ITU-N point code.
    2. The type/typea/typei/typen/typeis/typens/typen24 parameters specify the translation type and the network type of the translation type.
      • type/typea = ANSI translation type
      • typei = ITU-I translation type
      • typen = ITU-N translation type
      • typeis = ITU-I spare translation type
      • typens = ITU-N spare translation type
      • typen24 = ITU-N24 translation type
    3. The domain (ANSI or ITU) of the point code and translation type must be the same, unless the ANSI/ITU SCCP Conversion feature is enabled. If the ANSI/ITU SCCP Conversion feature is enabled, a GTT may contain an ANSI point code and an ITU translation type, or an ITU point code and an ANSI translation type. Whether the ANSI/ITU SCCP Conversion feature is enabled or not, the translation type parameters typei, typen, or typen24 can be specified with either the pci, pcn, or pcn24 parameters.
    4. If the VGTT feature is on, shown by the VGTT = on entry in the rtrv-feat output, the translation type can contain a maximum of 10 different length GTAs. If the Support for 16 GTT Lengths in VGTT feature is enabled and turned on, shown by the VGTT with 16 GTT lengths entry in the rtrv-ctrl-feat output, the translation type can contain maximum of 16 different length GTAs. If the maximum number of different GTA lengths is shown in the NDGT column of the rtrv-tt output, the length of the GTA must match any existing GTA assigned to the translation type.
    5. If the translation type contains less than the maximum number of different length GTAs, the length of the GTA can be from 1 to 21 digits.
    6. If the VGTT feature is off, the length of the GTA must contain the number of digits defined by the NDGT field of the rtrv-tt output.
    7. The cggtmod parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled.
    8. If the point code is the EAGLE’s point code, then the xlat parameter value must be dpcssn and the ri parameter value must be ssn.
    9. The mrnset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.
    10. If the pc/pca/pci/pcn/pcn24 parameter value is not shown in the rtrv-map output, the force=yes parameter must be specified with the ent-gtt command.
    11. The mapset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.
    12. Hexadecimal digits (0-9, a-f, A-F) can be specified for the gta or egta parameters only if the Hex Digit support for GTT feature is enabled.
    13. The loopset parameter can be specified only if the SCCP Loop Detection feature is enabled.
    14. Either the type parameter or the ttn parameter must be specified.
    15. If the type parameter is not specified, the translation type name must be assigned to a translation type in the database. This can be verified with the rtrv-tt command.
    16. If the type and ttn parameters are specified, the specified translation type must be in the database and the specified translation type name must be assigned to the translation type.
    17. The end global title address (egta) must be greater than or equal to the start global title address (gta) and its length must be equal to the start global title address.
    18. A GT modification identifier entry can contain the ngti=4 parameter value only if the point code value in the GTT entry is an ITU point code.
    19. Since NTT is no longer dependent on XLAT=DPCNGT, the functionality of XLAT=DPCNGT and XLAT=DPC shall be the same.
  28. Verify the changes using the rtrv-gtt command with the translation type parameter and value, and the gta parameter value specified in 27. If the num parameter is specified with the rtrv-gtt command, and the value of the num parameter is greater than 1000, the force=yes parameter must be specified with the rtrv-gtt command.
    For this command, enter these commands.

    rtrv-gtt:typea=5:gta=910460

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:46:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT  
    5      scp1       6
    
    GTT TABLE IS (27000 of 269999)  10 % FULL   
    
    START GTA             END GTA               XLAT   RI     PC
    910460                919460                DPCNGT GT     007-007-007
         MAPSET=114   SSN=---  GTMODID=modid2     CGGTMOD = YES
         LOOPSET = none
    
    Command Retrieved 1 Entries

    rtrv-gtt:typea=10:gta=615370

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:46:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT  
    10     scp2       6
    
    GTT TABLE IS (27000 of 269999)  10 % FULL
       
    START GTA             END GTA               XLAT   RI     PC
    615370                615380                DPCSSN SSN    003-003-003
         MAPSET=3     SSN=254  GTMODID=---------  CGGTMOD = NO
         LOOPSET = none
    
    Command Retrieved 1 Entries

    rtrv-gtt:typea=15:gta=800

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:48:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT  
    15     scp3       3
    
    GTT TABLE IS (27000 of 269999)  10 % FULL
    
    START GTA             END GTA               XLAT   RI     PC
    800                   900                   DPC    SSN    005-005-005
         MAPSET=1     SSN=---  GTMODID=---------  CGGTMOD = NO
         LOOPSET = rtp1
    
    Command Retrieved 1 Entries
  29. 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 3-11 Add a Global Title Translation - Sheet 1 of 10

Figure 3-12 Add a Global Title Translation - Sheet 2 of 10

Figure 3-13 Add a Global Title Translation - Sheet 3 of 10

Figure 3-14 Add a Global Title Translation - Sheet 4 of 10

Figure 3-15 Add a Global Title Translation - Sheet 5 of 10

Figure 3-16 Add a Global Title Translation - Sheet 6 of 10

Figure 3-17 Add a Global Title Translation - Sheet 7 of 10

Figure 3-18 Add a Global Title Translation - Sheet 8 of 10

Figure 3-19 Add a Global Title Translation - Sheet 9 of 10

Figure 3-20 Add a Global Title Translation - Sheet 10 of 10