> 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/tdm-interfaces.md).

# Tdm Interfaces

### [E1/T1](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/t1-e1-and-j1-interfaces/README.md), [DS3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/ds3-interfaces/README.md)

For a [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) system that contains multiple telecom units, it is recommended to load share the line interfaces between providers. This will make your service fault tolerant. This is the same principle as the signaling protocol load sharing.

Here is an example of a [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) that load shares its [DS3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/ds3-interfaces/README.md) interfaces to create a service fault tolerant system.

![TMG7800 Line Interface Load sharing](https://docs.telcobridges.com/w/images/6/69/Ha_TMG7800_TDM_Load_Share.png)

The service is still available even if a telecom unit fails

![TMG7800 Fault Tolerant Service](https://docs.telcobridges.com/w/images/7/70/Ha_TMG7800_TDM_Load_Share_Fail.png)

### [STM-1/OC-3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/stm-1/README.md)

The [STM-1/OC-3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/stm-1/README.md) is the only inherently redundant line interface. TelcoBridges TMG7800-STM1 and TMG3200-STM1 support [APS](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/automatic-protection-switching/README.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/transmission-and-lines/tdm-interfaces.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.