> 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-an-m3ua-isup-network.md).

# Creating an M3UA ISUP Network

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

Now that you have created an initial ISUP stack, you must create a new ISUP network.

The ISUP network tells the ISUP protocol layer about a collection of SS7 nodes that are accessible through MTP3. Based upon your system configuration, one or more ISUP networks are created. Repeat this section for as many networks as you require.

**NOTE:** An ISUP network can be used by multiple ISUP interfaces even if they are members of different ISUP userpart (e.g., to support multiple switch variants for a single SS7 network).

To create an M3UA ISUP network:

1- Click "Create New ISUP Network" in the ISUP stack configuration window

![Toolpack v2.5 Create ISUP Network](https://docs.telcobridges.com/w/images/2/2c/Toolpack_v2.5_Create_ISUP_Network.png)

2- Configure the new ISUP network:

* Enter a **name** for the network
* Select **M3UA** as the type of network to bind
* Select an **M3UA user part**
* Click **Create**

![Toolpack v2.5 Creating M3UA ISUP Network](https://docs.telcobridges.com/w/images/9/92/Toolpack_v2.5_Creating_M3UA_ISUP_Network.png)

3. Verify that the **"IsupNetwork was successfully created"** message appears

![Toolpack v2.5 ISUP Network Created](https://docs.telcobridges.com/w/images/8/89/Toolpack_v2.5_ISUP_Network_Created.png)

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Type of Network to Bind](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/isup#t)
* [M3UA Userpart](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#m)


---

# 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-an-m3ua-isup-network.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.