Why gt routing is used

There are three optional add-on features that enhance the functionality of the global title translation feature:. The GTT feature requires one of the following cards:. For more information on these cards, refer to the Adding a Service Module procedure or to Hardware Reference. The VGTT feature must be purchased before enabling this feature. 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 or entries, the XMAP Table Expansion feature must be enabled with the enable-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. 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.

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. Verify this with the rtrv-ctrl-feat command. 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. 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.

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 , or 1,, entries, the XGTT Table Expansion feature must be enabled with the enable-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. With this feature enabled, loopsets are provisioned. These loopsets are assigned to Global Title Translations.

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

The EGTT feature must be purchased before turning on the feature. The VGTT feature must be purchased before turning it on. This procedure is used to add a service module to support the Global Title Translation or Enhanced Global Title Translation feature to the database using the ent-card command. The card that is used as a service module depends on the GTT related features that are being used and the features that will enabled after this procedure is performed. The features that are currently being used by the EAGLE are shown in the rtrv-feat or rtrv-ctrl-feat command outputs.

The E5-SM8G-B can be inserted only in the odd numbered card slots of the control or the extension shelf. The ent-card command uses these parameters:. The value of this parameter is dsm or slic. The value of this parameter is vsccp. The shelf to which the card is to be added must already be in the database. This can be verified with the rtrv-shlf command. The card cannot be added to the database if the specified card location already has a card assigned to it. This is an example of the possible output:.

If service modules are not shown in the rtrv-card output, continue the procedure with 2. If the GTT feature is on, continue the procedure with 4. If the GTT feature is off, continue the procedure with 3. The GTT feature must be purchased before turning it on. When the chg-feat has successfully completed, this message should appear. Notes :. If the rept-stat-sccp output shows that the EAGLE has the maximum number of service modules, as shown in Table , the remainder of this procedure cannot be performed.

This is an example of the possible output. Once the HIPR2 cards have been installed, continue the procedure with 7. IP address for the specified port. IP addresses consist of the network number of the system and the unique host number. Subnet mask of the IP interface in the form of an IP address with a restricted range of values.

Media Access Control Type of the interface. When a Service Module card is entered into the database, these values are automatically configured. Multicast Control to enable or disable multicast support for the interface. Tells hardware whether to automatically determine duplex and speed. Host name. The fourth octet identifies the SM card and must have a unique octet identifier for the card IP address.

Most customer private networks do not require setting up a default router for the SM card. If your network configuration requires a default router to connect the Service Module card communication to the EPAP, then only one default router is assignable to each Service Module card. Assign the default router address to each Service Module card as shown in this step. Default router IP address. Command string passed to Service Module card for processing. If the pass commands with the ping parameter are not successful, verify the correct connection of the hardware cabling and repeat this step.

If the command fails again, contact the unresolvable-reference. When this command has successfully completed, this message should appear. The EGTT feature must be purchased before turning it on. This procedure is used to remove a service module, used by global title translation, from the database using the dlt-card command. The card cannot be removed if it does not exist in the database.

The examples in this procedure are used to remove the service module in card location For this example, enter this command. The dlt-card command has only one parameter, loc , which is the location of the card. This procedure is used to add a mapped SS7 message translation type to the database.

The mapped translation type is added to the database using the ent-ttmap command and is assigned to an ANSI SS7 linkset. The ent-ttmap command uses these parameters. The examples in this procedure are used to map the SS7 message translation type to the translation type for any incoming messages on linkset lsn Because the rtrv-ls command used in this procedure can output information for a long period of time, the rtrv-ls command can be canceled and the output to the terminal stopped.

There are three ways that the rtrv-ls command can be canceled. Press the F9 function key on the keyboard at the terminal where the rtrv-ls command was entered. Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls command was entered. For more information about the canc-cmd command, go to Commands User's Guide. This procedure is used to remove a mapped SS7 message translation type from the database using the dlt-ttmap command.

The dlt-ttmap command uses these parameters. The examples in this procedure are used to remove the translation type for any outgoing messages on linkset nc This procedure is used to change a mapped SS7 message translation type in the database using the chg-ttmap command. The chg-ttmap command uses these parameters. Only the mapped translation type mtt can be changed with this procedure.

To change the lsn , io , or ett values, the mapped translation type entry has to be removed from the database using the Removing a Mapped SS7 Message Translation Type procedure, then re-entered with the new lsn , io , or ett values using the Adding a Mapped SS7 Message Translation Type procedure.

The examples in this procedure are used to change the mapped translation type , being mapped for translation type for incoming messages on linkset lsn01 to mapped translation type This procedure is used to add a concerned signaling point code CSPC group to the database using the ent-cspc command.

The ent-cspc command uses these parameters. The examples in this procedure are used to add the concerned signaling point code CSPC groups shown in Table The CSPC cannot be in the database for the indicated group. The point code must exist in the routing table and cannot already exist in the specified group. Verify that the point code is in the routing table by entering the rtrv-rte command with the point code.

If the point code is an ANSI point code, it must be a full point code. The route must contain a minimum of one active signaling link. The database can contain a maximum of CSPC groups. Each CSPC group can contain a maximum of 96 concerned signaling point codes. The mated point codes in the mated application table will not automatically receive CSPC broadcasts unless each mated point code is contained in a CSPC group. A mated application group can contain up to 32 entries, a primary point code and up to 31 mated point codes.

Each mated point code in a mated application group can be assigned to a different CSPC group. If the group name does not exist, and a point code is not specified, a new group will be created.

If the point code is not shown in the rtrv-rte output, perform one the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. Make sure the signaling link is placed into service. When each these commands have successfully completed, this message should appear.

This procedure is used to remove a concerned signaling point code CSPC group from the database using the dlt-cspc command. The dlt-cspc command uses these parameters. The examples in this procedure are used to remove the concerned signaling point code from the CSPC group grp10 from the database. The CSPC must be in the database for the indicated group.

The following is an example of the possible output. After the CSPC group assignments have been changed, go to step 5. If the CSPC group being removed in this procedure is not shown in the rtrv-map output, go to step 5.

This procedure is used to provision a solitary mated application in the database using the ent-map command. A solitary mated application contains only one entry.

The ent-map command use these parameters to provision a solitary mated application. The value for this parameter is 2 to The value for this parameter is shown in the rtrv-cspc output.

If the desired value is not shown in the rtrv-cspc output, perform the Adding a Concerned Signaling Point Code procedure to add the desired group. If this parameter is not specified, then a CSPC group name is not specified for the mated application.

This parameter allows the user the option to have the specified subsystem marked as prohibited even though an MTP-RESUME message has been received by the indicating that the specified point code is allowed. The value for this parameter is on or off. The default value is off. If the Flexible GTT Load Sharing feature is enabled, the point code and subsystem specified for the global title translation must be assigned to the MAP set specified by this parameter.

The mapset parameter has three values. This is the MRN set from which alternate routing indicator searches are performed. The values for this parameter are yes and no. This parameter can be specified for any type of mated application, but this parameter affects only the traffic for a dominant mated application.

The default value for ITU-N24 solitary mated applications is no. The default value for ANSI solitary mated applications is yes. The default value for ITU solitary mated applications is no. Previous Next JavaScript must be enabled to correctly display this content. There are three optional add-on features that enhance the functionality of the enhanced global title translation feature: The Variable-length Global Title Translation feature VGTT , allows global title translation on global title addresses of varying length.

For more information on this feature, refer to the Variable-length Global Title Translation Feature section. Maximum of , global title addresses per GTT set.

The system default is , global title addresses. This quantity can be increased to , by enabling the feature access key for part number , or to 1,, by enabling the feature access key for part number Maximum of , GTT selectors.

The system default is mated applications. This quantity can be increased to by enabling the feature access key for part number , or to by enabling the feature access key for part number E Cmd Rej: Exceeding max GTA Lengths supported per GTTSET If the translation type or GTT set 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 or GTT set, 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 or the GTT set.

Advanced GT Modification Feature This feature allows the EAGLE to modify other fields of an MSU in addition to the translation type, destination point code, called party point code, called party SSN, routing indicator, numbering plan, and nature of address indicator when the MSU requires further global title translation and the translation type is to be replaced.

This part number can be specified only if no Advanced GT Modification feature is currently enabled. This feature and its part number is shown in the rtrv-ctrl-feat output only if the MGTT feature from previous releases was turned on when the Eagle was upgraded to the release containing the Advanced GT Modification feature. This part number cannot be specified with the enable-ctrl-feat command.

None of the Advanced GT Modification features have to be enabled to create an entry in the GT modification table that contains only the ntt parameter value. If the final 0 is considered as a filler, then it is ignored during the GT modification process. This parameter has two values, on or off. If the gt0fill value is on , the final 0 in the global title address is a filler.

If the gt0fill value is off, the final 0 in the global title address is a valid digit. This parameter has two values, pfx and sfx. This parameter specifies whether or not calling party global title modification is required. The cggtmod parameter can also be specified for when provisioning a linkset to indicate that calling party global title modification is required for SCCP traffic on the linkset.

This parameter is configured with the ent-gtt , chg-gtt , ent-gta , or chg-gta commands. All the parameters, except the cggtmod parameter, are configured as an entry in the in the GT modification table using either the ent-gtmod or chg-gtmod commands. Each entry in the GT modification table is identified by the gtmodid parameter. Perform one of these procedures to configure these parameters. Advanced GT Modification The Advanced GT Modification feature allows the deletion or substitution of digits from the beginning prefix digit modification or the end suffix digit modification of the global title address in either the called party address or the calling party address of the MSU.

Note: If the value of the cnvcgda , cnvcgdi , or cnvcgdn options is no , and the calling party address of the MSU cannot be converted when the MSU is processed, then the MSU is discarded. The SCCP processing of the message continues. If the randsls parameter value of the chg-stpopts command is either off or class0 , load sharing for all Class 1SCCP messages is supported only in the dominant mode.

PC RC 10 10 10 10 10 10 10 10 When the point code in the intermediate global title translation is translated to , all traffic routed using the global title addresses in the global title translations containing this point code are load shared equally, no matter what the global title address is.

Addition of Flexible GTT Load Sharing Feature When the Intermediate GTT Load Sharing and the Flexible GTT Load Sharing features are enabled and turned on thus allowing Flexible Intermediate GTT Load Sharing to be performed , the intermediate GTT load sharing arrangements are determined by the following: The MRN set assigned to the global title translation The translated point code in the message assigned to the global title translation The global title address in the message assigned to the global title translation When a global title address in a global title translation is translated to a point code, the MRN set assigned to the global title translation and containing the translated point code determines how load sharing is applied to the traffic for this global title translation.

The method of load sharing is determined by the relative cost RC value assigned to each point code in the MRN set. The following shows sample output from the rtrv-mrn command for a dominant map set. If that point code is unavailable, the next point code that is attempted is at the top of the list, relative cost The following shows sample output from the rtrv-mrn command for a load shared map set. MRNSET PC RC DFLT 10 20 20 30 30 40 40 50 In this example, if the preferred point code is , the traffic is shared between the two point codes with a relative cost of If those become unavailable, the traffic is routed to the point codes with a relative cost of If those become unavailable, the traffic gets routed to the point code with a relative cost of If that point code becomes unavailable, the traffic is routed back of the top of the list to the primary point code that has a relative cost of However, traffic will only be load shared among point codes.

In the following example, the point code is assigned to three MRN sets. In MRN set 2, point code is one of eight point codes in a load shared MRN set, each with a relative cost value of Addition of Flexible GTT Load Sharing Feature When the Flexible GTT Load Sharing feature enabled and turned on, allowing Flexible Final GTT Load Sharing to be performed, the GTT load sharing arrangements are determined by: The MAP set assigned to the final global title translation The translated point code and subsystem The global title address in the message assigned to the global title translation When a global title address in a final global title translation is translated to a point code and subsystem, the MAP set assigned to the final global title translation containing the translated point code and subsystem determines how load sharing is applied to the traffic for this final global title translation.

The method of load sharing is determined by the relative cost RC value assigned to each point code and subsystem in the MAP set.

The following shows sample output from the rtrv-map command for a solitary map set. The following shows sample output from the rtrv-map command for a dominant map set.

If that point code and subsystem becomes unavailable, the traffic is routed down the list to the next available point code and subsystem relative cost If that point code and subsystem becomes unavailable, the traffic is routed to the top of the list to that primary point code and subsystem relative cost 10 , and so on.

The following shows sample output from the rtrv-map command for a load shared map set. If those become unavailable, the traffic is sent to , subsystem , which has a relative cost of In the following example, the point code , subsystem , is assigned to three MAP sets.

In MAP set 2, point code , subsystem , is one of eight point codes and subsystems in a load shared MAP set, each with a relative cost value of CgPA global title address, translation type, global title indicator, and subsystem number in the incoming message. If the global title indicator value in the message is 4, the CgPA numbering plan and nature of address indicator is also used in the CgPA global title translation mode. CgPA point code, translation type, global title indicator, and subsystem number in the incoming message.

Enter the rtrv-card command to verify the cards that are provisioned in the database. Perform the Adding a Service Module procedure. Note: If you wish to use a GTT mode hierarchy for the linkset other than the system default GTT mode hierarchy, specify the gttmode parameter when provisioning the linkset. Note: The command line on the terminal can contain up to 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.

Note: If the required database entity is shown in the output of the retrieve command for that database entity, the procedure for provisioning the database entity does not need to be performed. 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.

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. Note: After the required global title translations have been provisioned in step 5, skip steps 6, 7, and 8.

Individual Weighting Individual weighting is a method for assigning a different load capacity to each member of an RC group. The preferred entity is the outcome of GTT. It is the first entity used for load-sharing after initialization, and is the primary entity for Class 1 SCCP Sequenced traffic. When weights are applied, no entity has any preference over another based on GTT information. Individual Weighting Example Table shows how weighting affects traffic delivery.

In-Service Threshold The in-service threshold defines the minimum percentage of weight that must be available for an RC group to be considered available. Traffic can routed to the RC group in all circumstances. No traffic can be routed to this RC group. RC Group Wt. In-Service Threshold Req. Entity Status Entity Avail. RC Group Avail.

Entity Available Weight — the entity receives a percentage of the traffic determined by its weight relative to the total available weight of the RC group. RC group status - refer to Table Add the required E5-SM4G cards to the database using the ent-card command.

Perform Adding a Service Module. Perform one of these procedures: Provisioning a Solitary Mated Application. Provisioning a Dominant Mated Application. This section describes the various components of the SCCP address.

This is the first byte in the SCCP address. SCCP address indicator represents the parameters present in the address and how the routing will be done. Address Indicator has the following sub-parameters. Routing Indicator RI , a one-bit parameter. GT indicator, mentions what type of GT is present in the address. The possible values are from zero to four.

Following is the table for possible GT indicator values. Mostly SSN is mandatory to add while sending ss7 messages from one application to another. Then only update location can reach the HLR, else the receiver can not know, to which application message has to deliver. If point code is present and routing is set on the route on GT. Then routing does not use the point code. SS7 Point Code , this is the address of an ss7 node. If a point code is an international point code, then from anywhere in the world a message can be sent to the node by doing point code-based routing.

Value [1] Entry Attribute. Bit 0 - Wild Card bit. Bits Not Used. See API Reference for format. Value [n] Translation Result Option. Value [n] Translation Result 1. See in the API Reference for format. The following values apply to the sample below:.

Value[0] Group ID.