Hex Digit Support for GTT

The Hex Digit Support for GTT feature, when enabled, allows the EAGLE to process incoming messages that contain either decimal (0-9) or hexadecimal digits (0-9, a-f, A-F) in the global title address in the called party address field of the messages.

If the Hex Digit Support for GTT feature is enabled and the Origin-Based SCCP Routing feature is enabled and turned on, the EAGLE can process messages containing decimal or hexadecimal digits in the global title address in either the calling party address or the called party address fields of the messages, depending on the GTT hierarchy that is used to process the messages. For more information on the Origin-Based SCCP Routing feature, refer to the Origin-Based SCCP Routing section.

With the Hex Digit Support for GTT feature enabled, hexadecimal digits can be specified for the gta and egta parameters of the ent-gtt, chg-gtt, ent-gta, and chg-gta commands. If the Advanced GT Modification feature is enabled, hexadecimal digits can be specified for the values of the prefix and suffix deletion digit parameters (npds and nsds) of the ent-gtmod, and chg-gtmod commands. For more information on the Advanced GT Modification feature, refer to the Advanced GT Modification Feature section.

If the ANSI/ITU SCCP Conversion feature is enabled, hexadecimal digits can be specified for the values of the prefix and suffix deletion digit parameters (npds and nsds) of the ent-gtcnv or chg-gtcnv commands. For more information on the ANSI/ITU SCCP Conversion feature, refer to the ANSI/ITU SCCP Conversion Feature section.

After the Hex Digit Support for GTT feature is enabled, any existing range entries for global title addresses are treated as a range of hexadecimal values instead of a range of decimal values. For example, the database contains an entry that contains the range of global title addresses from 20 to 30. With the Hex Digit Support for GTT feature not enabled, this translation would match MSUs containing the global title addresses 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, and 30. With the Hex Digit Support for GTT feature enabled, this translation would match MSUs containing the global title addresses 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2A, 2B, 2C, 2D, 2E, 2F, and 30. Translations containing a single entry for the global title address are not changed.

If you wish to have different translated data for hexadecimal digits, the existing range entry can be split into 3 entries as follows in Table 2-1.

Table 2-1 Hex Digit Range Example

GTA=20	EGTA=29	with existing translation data
GTA=2A	EGTA=2F	with user specified translation data
GTA=30		with existing translation data

Hexadecimal digits cannot be used as a value for the gta parameter for the ent-gws-redirect and chg-gws-redirect commands.

Hexadecimal digits can be used as values for GSM MAP screening entries only if the Enhanced GSM MAP Screening feature is enabled.

Provisioning the Hex Digit Support for GTT Feature

To provision the Hex Digit Support for GTT feature, perform these steps.

1. Turn the GTT feature on using the chg-feat command. Add the required service modules to the database using the ent-card command. Perform the Adding a Service Module procedure. If Enhanced Global Title Translation will be used, turn the EGTT feature on using the chg-feat command.
2. Enable the Hex Digit Support for GTT feature using the enable-ctrl-feat command. Perform the Activating the Hex Digit Support for GTT Feature procedure.

   Note:

   Once this feature is enabled, the feature is also turned on. The chg-ctrl-feat cannot be used to turn this feature on. Once this feature is enabled, the feature cannot be turned off.
3. Provision the required destination point codes, linksets, signaling links, and routes, by performing these procedures.
   • Destination Point Codes - Adding a Destination Point Code procedure in Database Administration - SS7 User's Guide.
   • Linksets - Perform one of these procedures depending on the type of linkset.
     • SS7 Linkset - Adding an SS7 Linkset procedure in Database Administration - SS7 User's Guide
     • These procedures in Database Administration - IP7 User's Guide.
       • IP Gateway Linkset - Configuring an IPGWx Linkset
       • IPSG M2PA Linkset - Adding an IPSG M2PA Linkset
       • IPSG M3UA Linkset - Adding an IPSG M3UA Linkset
   • Signaling Links - Perform one of these procedures depending on the type of signaling link.
     • A low-speed SS7 signaling link - Adding an SS7 Signaling Link procedure in Database Administration - SS7 User's Guide
     • An E1 signaling link - Adding an E1 Signaling Link procedure in the Database Administration Manual - SS7
     • A T1 signaling link - Adding a T1 Signaling Link procedure in Database Administration - SS7 User's Guide
     • An ATM signaling link - Adding an ATM High-Speed Signaling Link procedure in Database Administration - SS7 User's Guide
     • These procedures in Database Administration - IP7 User's Guide.
       • IPLIMx Signaling Link - Adding an IPLIMx Signaling Link
       • IPGWx Signaling Link - Adding an IPGWx Signaling Link
       • IPSG M2PA Signaling Link - Adding an IPSG M2PA Signaling Link
       • IPSG M3UA Signaling Link - Adding an IPSG M3UA Signaling Link
   • Routes - Perform one of these procedures in Database Administration - SS7 User's Guide depending on the type of route.
     • A route containing an SS7 DPC - Adding a Route Containing an SS7 DPC procedure
     • A route containing a cluster point code - Adding a Route Containing a Cluster Point Code procedure
     • A route containing an IPGWx Linkset - Adding a Route Containing an IPGWx Linkset procedure

   Note:

   If only the GTT feature was turned on in step 1, perform steps 4 and 5. If the EGTT feature was turned on in step 1, skip steps 4 and 5 and perform steps 6, 7, and 8.
4. Provision the required translation types using the ent-tt command. Perform the Adding a Translation Type procedure.
5. Provision the required global title translations using the ent-gtt command. Perform the Adding a Global Title Translation procedure.

   Note:

   After the required global title translations have been provisioned in step 5, skip steps 6, 7, and 8.
6. Provision the required GTT sets using the ent-gttset command. Perform the Adding a GTT Set procedure.
7. Provision the required GTT translations using the ent-gta command. Perform the Adding Global Title Address Information procedure.

   Note:

   The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the ent-gta command are too long to fit on the ent-gta command line, perform the chg-gta command to complete adding the GTA entry. If the parameters and values specified with the chg-gta command are too long to fit on the chg-gta command line, perform the chg-gta command as many times as necessary to complete the GTA entry.
8. Provision the required GTT selectors using the ent-gttsel command. Perform the Adding a GTT Selector procedure.