> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/protocols/gtt-address-map-configuration.md). # GTT Address Map Configuration This step is used to configure an address map instance for a GTT association of the SCCP layer. These address map entries specify the results of translation. Following the association configuration, the user has to configure address map entries in SCCP. ### Description of parameters General explanation of the configuration parameters: * The **Handle SCCP gtt association** parameter specifies the handle of the SCCP global title translation association *** * The **Action** parameter specifies the type of action for this address map. Allowable values: see the 'SCCP GT action type' table in [SCCP:GTT Association Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-association-configuration/README.md). **Note:** The range parameters might not be the same as configured in the association. They can be a subset. *** * The **Replace GT flag** parameter specifies whether to replace the GT in outgoing (post GTT) address with the incoming GT *** * The **Load share flag** parameter specifies the mode of operation of SCCP entities. The mode can be either DOMINANT (if flag set to 'False') or LOADSHARE (if flag set to 'True'). Loadsharing among SCCP entities will be achieved on the basis of SLS for class 1 traffic and on round-robin fashion for class 0 traffic. **Note:** This parameter is applicable only in ITU96. *** * The **Global title** parameter specifies the global title. Apart from the global title address, the user needs to fill up fields used for finding the rule. See Global Title structure definition below * The **Out network identifier** parameter specifies the network id of outgoing addresses *** * The **Number of entities** parameter specifies the number of entities in the 'Out Address' array. Allowable values are 1 - 2. **Note:** In ITU96 it should be defined as 2 and in all other versions it should be defined as 1. *** * The **Array of out address** parameter specifies the SCCP entity outgoing address. See Entity structure definition below. *** #### Global Title-specific information General explanation of the parameters of Global Title specific information: * The **Global title format** parameter specifies the type of the global title format. Allowable values: see the 'SCCP GT format type' table in [SCCP:GTT Association Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-association-configuration/README.md). * The **Address length** parameter specifies the number of bytes the BCD digits occupy * The **BCD address** parameter specifies the BCD digits of SCCP address * For The **Format 1, 2, 3 and 4** parameters (Format1 Format2, Format3 and Format4), see the 'GT Format 1, 2, 3 and 4' explanations and table in [SCCP:GTT Association Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-association-configuration/README.md). *** #### Entity-specific information General explanation of the parameters of Entity-specific information: * The **Present flag** parameter specifies the presence of the address. Allowable values are 'True' or 'False'. * The **No point code in header flag** parameter specifies whether or not to include the point code in the SCCP header. Allowable values are 'True' or 'False'. * The **Sub-service field present flag** parameter indicates whether the sub-service field contains a valid value. Allowable values are 'True' or 'False'. * The **Sub-service** field specifies the type of network. For allowable values, see the 'Sub-service field values' table in [MTP3:Userpart Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp3-userpart-configuration/README.md). * The **Subsystem number present flag** parameter indicates the subsystem number indicator presence. Used to encode the subsystem number indicator in the address indicator octet of the address parameter in an SCCP message. Allowable values are 'True' or 'False'. * The **Point code present flag** parameter indicates the point code indicator presence. Used to encode the point code indicator in the address indicator octet of the address parameter in an SCCP message. Allowable values are 'True' or 'False'. * The **Subsystem number** field specifies the subsystem number used to identify the SCCP user. Allowable values: see the table for 'SCCP SSN value to identify SCCP user' in Toolpack:Create a SCCP route. * The **Point code** field specifies the point code value * The **Network bit** field specifies the network indicator bit. Allowable values: see the table for 'SCCP network bit' in [Toolpack:Create a SCCP network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-a-sccp-network/README.md). *** * The **Routing indicator** field specifies the routing indicator. Used to encode the routing indicator in the address indicator octet of the address parameter in a SCCP message. Allowable values are: | SCCP Routing Type | Description | | ----------------- | ----------------------------------------------------------------------- | | Global title | Routing is based on the global title | | SSN | Routing is based on the destination point code and the subsystem number | *** * The **GT** parameter specifies the global title. See the Global Title explanation above. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/protocols/gtt-address-map-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.