> 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/telecom-references/transmission-and-lines/t1-e1-and-j1-interfaces.md).

# T1, E1, and J1 interfaces

The Tmedia [TMG3200](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmg3200) and Tdev TMP6400 TDM hardware adapters for T1, E1, and J1 lines provide for up to 64 lines. It is important that you verify the TDM module installed in your Tmedia unit.

For each T1/E1/J1 line that the Tmedia unit will use, a line interface with a related line service is configured in a one-to-one relationship. The configuring of the line interface activates the hardware and the line service is configured to transport traffic and signaling payload. A conceptual image is shown below:

![T1 e1 j1 line interfaces](https://docs.telcobridges.com/w/images/d/d9/T1-e1-j1-line-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 STM-1 connection. However, the converted ports will be used as trunks, and not as clocking sources.


---

# 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/telecom-references/transmission-and-lines/t1-e1-and-j1-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.