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

# M2PA

M2PA, the MTP2 peer-to-peer adaptation layer: how it replaces MTP2 entirely to carry SS7 links over IP, and how it differs from M2UA.

The *Message Transfer Part 2 Peer-to-Peer Adaptation Layer* (M2PA) is used to replace the [MTP2](/telecom-references/ss7-and-signalling/mtp2.md) layer entirely. In contrast with [M2UA](/telecom-references/ss7-and-signalling/sigtran/sigtran-m2ua.md), M2PA does not include MTP2 links between the two point codes; however, it still requires the [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) layer.

The following figures show two different configurations of M2PA:

**FIGURE 1:**

![m2pa\_sg\_setup.png](https://docs.telcobridges.com/w/images/d/d7/M2pa_sg_setup.png)

**FIGURE 2:**

![m2pa\_ipsp\_setup.png](https://docs.telcobridges.com/w/images/0/0a/M2pa_ipsp_setup.png)

The first figure includes a setup featuring the signaling gateway as an STP, from the [SS7](/telecom-references/ss7-and-signalling/ss7.md) point of view.

### TelcoBridges and M2PA

TelcoBridges supports M2PA as part of its [SIGTRAN](/telecom-references/ss7-and-signalling/sigtran.md) implementation.

### Configuration

* [SS7-M2PA configuration v3.2](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-3-2/protocol-stack/protocol-stack-settings#ss7-isup)
* [SS7-M2PA configuration v3.0](https://tmediadocs.telcobridges.com/other-pages/protocol-stacks-general/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks#ss7-isup)

<details>

<summary>Click here for other versions</summary>

* [SS7-M2PA 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#ss7-isup)
* [SS7-M2PA configuration v2.9](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-protocol-stacks#ss7-isup)
* SS7-M2PA 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.

</details>

### References

* [Article at Protocols.com](http://www.protocols.com/pbook/sigtran.htm#M2PA)
* RFC 4165 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)


---

# 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/m2pa.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.
