> 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/transmission-and-lines/ds3-interfaces.md).

# DS3 Interfaces

The Tmedia [TMG3200](https://tmediadocs.telcobridges.com/products/tmedia/tmg3200), [TMG7800](https://tmediadocs.telcobridges.com/products/tmedia/tmg7800) and Tdev TMP6400 TDM hardware adapter provides an interface of up to 3 DS3 lines.

For each DS3 line that the Tmedia or Tdev device will use, a line interface with related line services are configured. The DS3 interface can be configured in a one-to-one relationship with DS3 line services; however, unlike a T1/E1/J1 interface, the DS3 line service can be configured to contain subordinate child line services carrying lower bandwidth payload. A conceptual image is shown below:

![Schematic DS3 interfaces](https://docs.telcobridges.com/w/images/6/6f/Schematic-DS3-interfaces.jpg)

### Using BITS ports for signaling

Starting with release 2.3 of Toolpack, it is possible to convert unused BITS ports into [signaling ports](/telecom-references/ss7-and-signalling/ss7/signaling-ports.md), with indices of 1 and 0 respectively, in order to recover a channel on the primary DS3 connection.


---

# 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/transmission-and-lines/ds3-interfaces.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.