> 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/global-title-translation-association.md).

# Global Title Translation Association

A [GTT](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt/README.md) association defines a particular global title format and associated fields. It is assumed that all global titles included in this association have specific translation needs and therefore can be served by a single translation function set.

Each entry in the table below defines a GTT association for ITU.

| Format   | Indicator            | Numbering Plan           | Encoding Scheme | Translation Type |
| -------- | -------------------- | ------------------------ | --------------- | ---------------- |
| FORMAT 1 | International number | Not required             | Not required    | Not required     |
| FORMAT 2 | Not required         | Not required             | Not required    | 01               |
| FORMAT 3 | Not required         | Telephony numbering plan | BCD odd         | 02               |
| FORMAT 4 | Don’t care           | ISDN numbering           | Don’t care      | 03               |

**Note:** 'Don't care' values indicate that all values are allowed for this field in this GTT association.

***

GTT associations are provided as run-time configurable options with GTT Association Allocation message. You must configure one entry per association for which you require global title translation to be performed in the system. Any incoming GT that requires translation must match at least one configured association.

The GTT associations configuration should ensure that associations do not overlap. For configuring the associations as defined in the table above, the structure is filled as follows:

**Association Format 1** ProtocolVariant = TB640\_SS7\_SCCP\_PROTOCOL\_VARIANT\_ITU; GtFormat = TB640\_SS7\_SCCP\_GT\_FORMAT\_TYPE\_1; Format1.OddEven = TB640\_SS7\_SCCP\_GT\_ODD\_EVEN\_TYPE\_NOT\_USED; Format1.NatureOfAddress = TB640\_SS7\_SCCP\_GT\_NATURE\_OF\_ADDR\_IND\_INTERNATIONAL;

**Association Format 2**

```
ProtocolVariant = TB640_SS7_SCCP_PROTOCOL_VARIANT_ITU;
GtFormat = TB640_SS7_SCCP_GT_FORMAT_TYPE_2;
Format2.fUseTypeValue = TBX_TRUE;
Format2.un32TypeValue = 1;
```

**Association Format 3** ProtocolVariant = TB640\_SS7\_SCCP\_PROTOCOL\_VARIANT\_ITU; GtFormat = TB640\_SS7\_SCCP\_GT\_FORMAT\_TYPE\_3; Format3.fUseTypeValue = TBX\_TRUE; Format3.un32TypeValue = 2; Format3.NumberingPlan = TB640\_SS7\_SCCP\_GT\_NUMB\_PLAN\_TYPE\_TELEPHONY; Format3.EncodingScheme = TB640\_SS7\_SCCP\_GT\_ENCODING\_TYPE\_BCD\_ODD;

**Association Format 4** ProtocolVariant = TB640\_SS7\_SCCP\_PROTOCOL\_VARIANT\_ITU; GtFormat = TB640\_SS7\_SCCP\_GT\_FORMAT\_TYPE\_4; Format4.fUseTypeValue = TBX\_TRUE; Format4.un32TypeValue = 1; Format4.NumberingPlan = TB640\_SS7\_SCCP\_GT\_NUMB\_PLAN\_TYPE\_ISDN; Format4.EncodingScheme = TB640\_SS7\_SCCP\_GT\_ENCODING\_TYPE\_NOT\_USED; Format4.NatureOfAddress = TB640\_SS7\_SCCP\_GT\_NATURE\_OF\_ADDR\_IND\_NOT\_USED;

The action list defines the list of searching operations to be performed by the GTT function for a particular GTT association. The GTT function performs the search in the same sequence as given by the list. For example, the first action specified in the list is performed first. The action list serves as input to the GTT function for performing the global title translation.

**Note:** An actions list must be configured for a GTT Association instance.


---

# 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/global-title-translation-association.md?ask=<question>&goal=<endgoal>
```

`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.