> 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-an-mtp3-linkset.md).

# Creating an MTP3 Linkset

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

Once you have created an MTP3 network, you define linksets to logically combine multiple MTP3 links that connect to the same DPC. For example, one linkset could be the links between a point code identifying a Tmedia/Tdev SS7 node and a point code identifying the adjacent SS7 equipment.

To create an MTP3 linkset:

1- Click **MTP3** in the navigation panel.

![Mtp3 0 A](https://docs.telcobridges.com/w/images/9/9b/Mtp3_0_A.png)

2- Select an MTP3 network.

![Create MTP3 Linkset 0](https://docs.telcobridges.com/w/images/6/62/Create_MTP3_Linkset_0.png)

3- Click **Create New Mtp3 Linkset**

![Create MTP3 Linkset 1](https://docs.telcobridges.com/w/images/b/bc/Create_MTP3_Linkset_1.png)

4- Configure the new linkset:

* Enter a **name** for the linkset
* Select an **origin point code** (OPC)
* Select an **adjacent point code**
* Make sure the **desired state** is set to **Active**
* Click **Create**

![Create MTP3 Linkset 2](https://docs.telcobridges.com/w/images/6/66/Create_MTP3_Linkset_2.png)

5- Verify that the **"Mtp3Linkset was successfully created"** message appears

![Create MTP3 Linkset 3](https://docs.telcobridges.com/w/images/8/89/Create_MTP3_Linkset_3.png)

**Path**

```
/configurations/@[configuration_name]/mtp3_stacks/@[mtp3_name]/mtp3_networks/@[mtp3_network]/mtp3_linksets/@[mtp3_linkset]
```

**Parameters (text)**

```
/configurations/@[configuration_name]/mtp3_stacks/@[mtp3_name]/mtp3_networks/@[mtp3_network]/mtp3_linksets/@[mtp3_linkset]
adjacent_point_code = "@[point_code]"
name                = "@[mtp3_linkset]"
origin_point_code   = "@[point_code]"

/configurations/@[configuration_name]/mtp3_stacks/@[mtp3_name]/mtp3_networks/@[mtp3_network]/mtp3_linksets/@[mtp3_linkset]/state
active = true
```

**Parameters (json)**

```
{
  "adjacent_point_code" : "@[point_code]",
  "name" : "@[mtp3_linkset]",
  "origin_point_code" : "@[point_code]",
  "state" : {
    "active" : true
  }
}
```

### List of Parameters

* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Origin Point Code](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/isup#o)
* [Adjacent Point Code](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/mtp3#a)

**Live states**

* [Desired State](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/mtp3#d)


---

# 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-an-mtp3-linkset.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.