GTT Configuration

The following procedures describe the steps needed to add, remove, or change global title translation (GTT) data in the database.

Note:

The Global Title Translation (GTT) feature must be purchased before enabling the features with the chg-feat:gtt=on command. If you are not sure whether you have purchased the GTT feature, contact your Oracle Sales Representative or Account Representative.

The items configured in this section are:

• Service modules
• Translation type mapping
• Concerned signaling point codes
• Mated applications
• Mated relay nodes.
• GT conversion table entries for the ANSI/ITU SCCP Conversion feature
• Loopsets for the SCCP Loop Detection feature.
• GT modification identifiers for the Advanced GT Modification feature.

To configure the global title translation feature, translation types and global title translations must also be configured. The procedures to configure translation types and global title translations are located in the Global Title Translation (GTT) Configuration section.

The procedures shown in this chapter use a variety of commands. If more information on these commands is needed, refer to Commands User's Guide to find the required information.

There must be SS7 routes to the nodes referenced by the global title translation entities in the database. Perform one of the Adding a Route procedures in Database Administration – SS7 User's Guide to configure these routes.

The following is a brief description of the global title translation entities. These global title translation entities must be configured in the order that they are shown.

1. The GTT feature must be turned on with the chg-feat:gtt=on command. Verify this with the rtrv-feat command.

   Note:

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

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

2. A service module must be configured in the database with the ent-card command. A service module can be one of these cards: DSM (E5-SM4G/E5-SM8G-B), or SLIC. The DSM card is specified with the type=dsm and appl=vsccp parameters of the ent-card command. The SLIC card is specified with type=dsm (in the odd numbered card slots) or type=slic (in the even numbered card slots), and appl=vsccp parameters of the ent-card command. Refer to the Adding a Service Module procedure for the required cards. The card configuration can be verified with the rtrv-card command.
3. A translation type must be defined in the database. Verify this with the rtrv-tt command. If the necessary translation types are not in the database, add them with the ent-tt command. The translation type is used by the ent-gtt command and defines the length of the global title address.

   If the Variable-length Global Title Translation (VGTT) feature is being used, it must be enabled with the chg-feat:vgtt=on command. Verify this with the rtrv-feat command. Refer to the Variable-length Global Title Translation Feature section for more information on this feature.

   Note:

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

   The VGTT feature must be purchased before enabling this feature. If you are not sure whether you have purchased the VGTT feature, contact your Oracle Sales Representative or Account Representative.

4. The translation type can be mapped to another translation type. This is a function of the translation type mapping feature. The translation type mapping feature maps standardized internetwork translation type values to intranetwork translation type values used within any particular network. This feature also maps intranetwork translation type values to standardized internetwork translation type values. Enter the rtrv-ttmap command to verify that the necessary translation type mapping information is in the database. Enter the necessary translation type mapping information in the database using the ent-ttmap command.
5. The concerned signaling point code broadcast groups must be defined in the database. These groups define the point codes that receive subsystem allowed and subsystem prohibited status messages about a particular global title translation node. These messages are broadcast from SCCP management. Verify that these groups are in the database with the rtrv-cspc command. If these groups are not in the database, add them with the ent-cspc command.
6. The mated applications must be defined in the database. The mated applications are the point codes and subsystem numbers of the service databases along with parameters describing the routing between replicated pairs of service databases. Verify the mated application information in the database with the rtrv-map command. If the necessary mated application information is not in the database, add the necessary information with the ent-map command.

   If the XMAP Table Expansion feature is to be used to increase the number of mated application entries in the mated application table to either 2000 or 3000 entries, the XMAP Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XMAP Table Expansion feature with the rtrv-ctrl-feat command.

   The mated applications provide load sharing of the traffic between replicated pairs of service databases. The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for final global title translations (global title translation containing the routing indicator value SSN) than the mated applications can provide without the Flexible GTT Load Sharing feature enabled. With this feature enabled, MAP sets are provisioned. These MAP sets are assigned to global title translations. Refer to Flexible Final GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated applications.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

   Load sharing based on the weight assigned to an individual entities in a load sharing MAP group can be performed if the Weighted GTT Load Sharing feature is enabled and turned on. Refer to the Weighted GTT Load Sharing section for more information on using the Weighted GTT Load Sharing feature.

7. The mated relay node groups can be defined in the database if the Intermediate GTT Load Sharing feature is to be used. Verify this with the rtrv-mrn command. If the necessary global title translation information is not in the database, add it with the ent-mrn command.

   The Intermediate GTT Load Sharing (IGTTLS) feature must be enabled with the enable-ctrl-feat and chg-ctrl-feat commands. Verify this with the rtrv-ctrl-feat command. Refer to the Intermediate GTT Load Sharing Feature section for more information on this feature.

   The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for intermediate global title translations (global title translation containing the routing indicator value GT) than the Intermediate GTT Load Sharing feature can provide. With this feature enabled, MRN sets are provisioned. These MRN sets are assigned to global title translations. Refer to Flexible Intermediate GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated relay node groups.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

   Load sharing based on the weight assigned to an individual entities in a load sharing MRN group can be performed if the Weighted GTT Load Sharing feature is enabled and turned on. See the Weighted GTT Load Sharing section for more information on using the Weighted GTT Load Sharing feature.

8. The global title translation data must be defined in the database. This data is used to determine the destination of the service database that needs to queried for additional routing information. Verify this with the rtrv-gtt command. If the necessary global title translation information is not in the database, add it with the ent-gtt command.
   If the Advanced GT Modification feature is being used, it must be enabled with the enable-ctrl-feat command. Verify this with the rtrv-ctrl-feat command. Refer to the Advanced GT Modification Feature section for more information on this feature.

   Note:

   Once the Advanced GT Modification feature is enabled, it cannot be disabled.

   If the XGTT Table Expansion feature is to be used to increase the number of mated application entries in the mated application table to either 400,000 or 1,000,000 entries, the XGTT Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XGTT Table Expansion feature with the rtrv-ctrl-feat command.

   The ANSI/ITU SCCP Conversion feature provides a means to perform SCCP conversion between ANSI MSUs and ITU MSUs. To perform this conversion, the ANSI/ITU SCCP Conversion feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Verify the status of the ANSI/ITU SCCP Conversion feature with the rtrv-ctrl-feat command. Entries must be also configured in the GT conversion table with the ent-gtcnv command. The content of the GT conversion table can be verified with the rtrv-gtcnv command.

   Decimal digits (0-9) or hexadecimal digits (0-9, a-f, A-F) can be specified for these items that are assigned to the global title translation entry.

   • The global title address (gta and egta) values
   • Entries in the GT conversion table
   • The prefix (npds) and suffix (nsds) values in the GTMOD identifier that is assigned to the global title translation entry.

   Hexadecimal digits can be specified only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature with the rtrv-ctrl-feat command. Refer to the Hex Digit Support for GTT section for more information on this feature.

   The SCCP Loop Detection feature provides a method for detecting SCCP looping. With this feature enabled, loopsets are provisioned. These loopsets are assigned to Global Title Translations. See the SCCP Loop Detection section for more information on using the SCCP Loop Detection feature with Global Title Translations.