> 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-m2ua-links.md).

# Creating M2UA Links

> **Applies to:** Tmedia 3.0, 3.2, 3.3

After you create an [M2UA](https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/sigtran/sigtran-m2ua) cluster, you must create M2UA links for your system.

An M2UA link is always bound to an [MTP2](https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp2) link, and can be seen a way of extending MTP2 functionality.

To create an M2UA link:

1- Click **M2UA** in the navigation panel

![Create M2ua 0](https://docs.telcobridges.com/w/images/8/88/Create_M2ua_0.png)

2- Select an M2UA SAP

![Select M2uaSap 0](https://docs.telcobridges.com/w/images/8/8e/Select_M2uaSap_0.png)

3- Select an M2UA Cluster

![Select M2uaCluster 0](https://docs.telcobridges.com/w/images/7/7b/Select_M2uaCluster_0.png)

4- Click **Create New M2ua Link** in the M2UA cluster configuration window:

![Create M2UA Link 0](https://docs.telcobridges.com/w/images/5/5d/Create_M2UA_Link_0.png)

5- Configure the new M2UA link:

* Enter a **name** for the link
* **IMPORTANT!**
  * **For a system on a signaling gateway**: Select an **MTP2 link**
  * **For a system on a media gateway controller**: Select **NONE**
* Select a **protocol type** (same as MTP2)
* Select an **interface ID type**
* Enter an appropriate **interface ID** (must be unique to each link)
* Click **Create**

![Create M2UA Link 1](https://docs.telcobridges.com/w/images/6/6f/Create_M2UA_Link_1.png)

6- Verify that the **"M2ua Link was successfully created"** message appears

![Create M2UA Link 2](https://docs.telcobridges.com/w/images/e/ee/Create_M2UA_Link_2.png)

**Path**

```
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]/m2ua_saps/@[m2ua_sap]/m2ua_clusters/@[m2ua_cluster]/m2ua_links/@[m2ua_link]
```

**Parameters (text)**

```
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]/m2ua_saps/@[m2ua_sap]/m2ua_clusters/@[m2ua_cluster]/m2ua_links/@[m2ua_link]
intf_id       = "1"
intf_id_type  = "Integer"
mtp2_link     = "NONE"
name          = "@[m2ua_link]"
protocol_type = "ITU"

/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]/m2ua_saps/@[m2ua_sap]/m2ua_clusters/@[m2ua_cluster]/m2ua_links/@[m2ua_link]/state
target_link_state = "Connected"
```

**Parameters (json)**

```
{
  "intf_id" : "1",
  "intf_id_type" : "Integer",
  "mtp2_link" : "NONE",
  "name" : "@[m2ua_link]",
  "protocol_type" : "ITU",
  "state" : {
    "target_link_state" : "Connected"
  }
}
```

### List of Parameters

* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [MTP2 Link](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#m)
* [Protocol Type](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#p)
* [Interface ID Type](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#i)
* [Interface ID](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#i)


---

# 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-m2ua-links.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.