> 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/mtp3/mtp3-routing.md).

# MTP3 Routing

By directing messages to the appropriate [signaling point](/telecom-references/ss7-and-signalling/ss7/sp.md), the routing mechanism establishes the connection between the calling and the called party.

Message routes pass through a minimum number of intermediate signaling transfer points. Routing at each signaling transfer point is not affected by the message routes used up to the concerned signaling transfer point. If more than one message route is available, signaling traffic is load-shared by the available message routes. Messages related to a given user transaction and sent in a given direction are routed over the same message route.

Routing between functional blocks depends on whether transfer capability is enabled:

* If transfer capability is enabled, messages can be routed between signaling links, or between a signaling link and the upper layer or signaling network management.
* If transfer capability is disabled, messages cannot be routed between signaling links, though they can be routed between a signaling link and MTP3 service users or signaling network management.


---

# 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/mtp3/mtp3-routing.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.