> 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/ss7-and-signalling/ss7/gtt.md).

# GTT

Global title translation (GTT) is SS7's equivalent of IP routing: how SCCP translates a global title into a point code and sub-system number.

**Global title translation** (GTT) is the [SS7](/telecom-references/ss7-and-signalling/ss7.md) equivalent to IP routing. Translation examines the destination address (e.g. the number being called) and decides how to identify it over the telephone network. This process can include *global title analysis*, which is the act of looking up the number and finding a result address, and *global title modification*.

It is possible for the result of **Global Title Translation** to be **Route on** [**SSN**](/telecom-references/parameter-reference/sub-system-number.md). This means that, instead of the Global Title routing, lower level MTP routing will be used for this message from this point on. Equivalently, in a system using [SIGTRAN](/telecom-references/ss7-and-signalling/sigtran.md), the result from Global Title Translation may be to a route to an IP server.

### Reference

<http://en.wikipedia.org/wiki/Global\\_Title>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/gtt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.