> 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/products/tmedia/installation/tdm-module-options.md).

# TDM Module Options

The Tmedia [TMG3200](/products/tmedia/tmg3200.md) and TMP6400 units are furnished with a variety of [TDM](https://tmediadocs.telcobridges.com/telecom-references/transmission-and-lines/tdm) modules configured with the following capacities:

* 16 RJ48F ports providing connection for 16 (T1/E1/J1) lines
* 4 SCSI ports providing connection for 64 (T1/E1/J1) lines (via optional patch panel)
* 3 sets of dual BNC ports for connection to 3 DS3 lines
* 2 sets of electrical or optical ports for connection to two OC3/STM-1 lines (one line is for automatic protection switching).

See figure below for a rear view layout of the four TDM options.

![Schematic TMD module options](https://docs.telcobridges.com/w/images/d/d6/Schematic-TMD-module_options.jpg)

Regardless of the option, each TDM module requires that it be added as a line interface to the configuration of the Tmedia unit; furthermore, line services are required in order to transport the payload and signaling for each port.


---

# 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/products/tmedia/installation/tdm-module-options.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.