> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/sigtran/sigtran-m2ua.md).
# SIGTRAN M2UA
The SIGTRAN M2UA (Message Transfer Part 2 User Adaptation Layer) is used to interface the [MTP2](/telecom-references/ss7-and-signalling/mtp2.md) of the signaling gateway to the [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) of a media gateway controller (MGC). M2UA can also be seen as way to extend an MTP2 link. An M2UA link is always bound to an MTP2 link.
The following diagram illustrates the setup using M2UA:
The M2UA layer can interface with either a NIF (Nodal Inter-working Function) or an MTP3 layer; therefore, M2UA has two modes of operation. Furthermore, Toolpack can configure M2UA in both modes.
### TelcoBridges and M2UA
TelcoBridges supports M2UA as part of its [SIGTRAN](/telecom-references/ss7-and-signalling/sigtran.md) implementation.
### Sigtran use cases
You can see some use cases for Sigtran here: [Sigtran use cases](https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/use-cases/redirect/sigtran-configuration)
### Configuration
* [M2UA configuration v3.2](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-3-2/protocol-stack/protocol-stack-settings#sigtran)
* [M2UA configuration v3.0](https://tmediadocs.telcobridges.com/other-pages/protocol-stacks-general/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks)
Click here for other versions
* [M2UA configuration v2.10](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-protocol-stacks)
* [M2UA configuration v2.9](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-protocol-stacks)
* M2UA configuration v2.8 and earlier: documentation is no longer published. Contact [technical support](https://tmediadocs.telcobridges.com/operations-and-support/support/contacting-telcobridges-technical-support) if you need it.
### References
* [Article at Protocols.com](http://www.protocols.com/pbook/sigtran.htm#m2ua)
* RFC 3331 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer
### Other links
* [M3UA configurations](https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/use-cases/m3ua/use-cases-m3ua-configuration)
---
# 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://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/sigtran/sigtran-m2ua.md?ask=&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.