> 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/other-pages/protocol-stacks-ss7/creating-mtp3-links-m2pa.md).

# Creating MTP3 Links (M2PA)

#### ***Applies to version(s): v2.5, v2.6.***

Now that you have created an MTP3 linkset, you must create MTP3 links for it. This can be done from the MTP3 linkset configuration window. A linkset is used to logically combine multiple MTP3 links going to the same DPC into a single entity. One linkset could be comprised of the links between a point code identifying the Tmedia/Tdev SS7 node and a point code identifying the adjacent SS7 equipment.

To create an MTP3 link:

1- Click **Create New Mtp3 Link** in the MTP3 linkset configuration window

![Toolpack v2.5 Create M2PA Link](https://docs.telcobridges.com/w/images/9/95/Toolpack_v2.5_Create_M2PA_Link.png)

2- Configure the new MTP3 link:

* Enter a **name** for the link
* Under **Type of link to bind**, select **M2PA**.
* Select an **MTP2 link**
* Select a **priority level** (from 0 to 3)
* Select a **message priority** (from "none" to 3)
* Set the **C Link** value
* Enter a **Link Test Slc** (this value is unique in the link list)
* Enter **Link Test Characters**
* Click **Create**

![Toolpack v2.5 Creating MTP3 Link M2PA](https://docs.telcobridges.com/w/images/7/7f/Toolpack_v2.5_Creating_MTP3_Link_M2PA.png)

3- Verify that the **"Mtp3Link was successfully created"** message appears

![Toolpack v2.5 MTP3 Link Created](https://docs.telcobridges.com/w/images/d/d0/Toolpack_v2.5_MTP3_Link_Created.png)

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Type of Link to Bind](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#t)
* [MTP2 Link](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#m)
* [Priority Level](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#p)
* [Message Priority](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#m)
* [C Link](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#c)
* [Link Test Slc](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#l)
* [Link Test Characters](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#l)


---

# 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/other-pages/protocol-stacks-ss7/creating-mtp3-links-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.