> 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/creating-the-m2ua-configuration.md).

# Creating the M2UA Configuration

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

To create your [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) system, you must create a new M2UA configuration.

M2UA (Message Transfer Part 2 User Adaptation Layer) is used to interface the [MTP2 Layer](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) of a signaling gateway to the [MTP3 Layer](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp3/README.md) of a media gateway controller (MGC). M2UA can also be seen as a way to extend an MTP2 link. An M2UA link is always bound to an MTP2 link.

To create an M2UA configuration:

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

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

2- Create the M2UA configuration:

* Enter a **name** for the M2UA service
* Select a **Node Type** (SG, ASP, M2UA-MTP2 Relay)
* Click **Create**

![Create M2ua 1](https://docs.telcobridges.com/w/images/d/dd/Create_M2ua_1.png)

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

![Create M2ua 2](https://docs.telcobridges.com/w/images/b/bb/Create_M2ua_2.png)

**Path**

```
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]
```

**Parameters (text)**

```
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]
enabled             = true
name                = "@[m2ua_stack]"
node_type           = "Signaling Gateway (SG)"

/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]/advanced_parameters
one_identifier_per_primitive = false

/configurations/@[configuration_name]/hardware_units/@[hardware_name]/m2ua_stacks/@[m2ua_stack]/timers
ack_timer           = "1 second"
as_pending_timer    = "1 second"
heartbeat_timer     = ""
nb_aspm_retry       = 5
sctp_poll_timer     = "1 second"
ss7_cong_poll_timer = "1 second"
```

**Parameters (json)**

```
{
  "advanced_parameters" : {
    "one_identifier_per_primitive" : false
  },
  "enabled" : true,
  "name" : "@[m2ua_stack]",
  "node_type" : "Signaling Gateway (SG)",
  "timers" : {
    "ack_timer" : "1 second",
    "as_pending_timer" : "1 second",
    "heartbeat_timer" : "",
    "nb_aspm_retry" : 5,
    "sctp_poll_timer" : "1 second",
    "ss7_cong_poll_timer" : "1 second"
 }
```

### List of Parameters

* [Name](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/name/README.md)
* [M2UA Node Type](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/m2ua-node-type/README.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/creating-the-m2ua-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.