> 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/telecom-references/ss7-and-signalling/mtp2/connection-mode.md).

# Connection mode

The **Connection mode** parameter specifies the different modes of connection for a [MTP2](/telecom-references/ss7-and-signalling/mtp2.md) link. The following values are allowed:

| Connection mode | Description                                                                                                                                                                           |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Normal          | MTP2 link specifies the use of Nx64/56kbps mode (where N can vary from 1 to 16) with the underneath [MTP1](/telecom-references/ss7-and-signalling/ss7/mtp1-layer.md) (physical) layer |
| HSL             | MTP2 high speed link (HSL) specifies the use of the entire trunk bandwidth as a single link with the underneath MTP1 (physical) layer                                                 |

**NOTE:** The HSL mode uses timeslots 1 to 31 for E1 and 1 to 24 for T1/J1 interfaces. In Normal mode, you pick and choose the timeslots that will be part of the MTP2 link.


---

# 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/telecom-references/ss7-and-signalling/mtp2/connection-mode.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.