M2PA: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:M2PA]] | |||
The ''Message Transfer Part 2 Peer-to-Peer Adaptation Layer'' (M2PA) is used to replace the [[MTP2 Layer|MTP2]] layer entirely. In contrast with [[M2UA]], M2PA does not include MTP2 links between the two point codes; however, it still requires the [[MTP3 Layer|MTP3]] layer. | The ''Message Transfer Part 2 Peer-to-Peer Adaptation Layer'' (M2PA) is used to replace the [[MTP2 Layer|MTP2]] layer entirely. In contrast with [[M2UA]], M2PA does not include MTP2 links between the two point codes; however, it still requires the [[MTP3 Layer|MTP3]] layer. | ||
Revision as of 09:30, 22 June 2023
{{DISPLAYTITLE:M2PA]] The Message Transfer Part 2 Peer-to-Peer Adaptation Layer (M2PA) is used to replace the MTP2 layer entirely. In contrast with M2UA, M2PA does not include MTP2 links between the two point codes; however, it still requires the MTP3 layer.
The following figures show two different configurations of M2PA:
FIGURE 1:
FIGURE 2:
The first figure includes a setup featuring the signaling gateway as an STP, from the SS7 point of view.
TelcoBridges and M2PA
TelcoBridges supports M2PA as part of its SIGTRAN implementation.
Configuration
References
- Article at Protocols.com
- RFC 4165 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)