> 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/other-pages/hardware-and-clock/status-menus-tdm-lines.md).

# Status Menus:TDM Lines

#### ***Applies to version(s): v2.5, v2.6.***

General and detailed status information about the TDM lines, also referred to as Adapters is accessible from the TDM Lines tab of the Global Status view.

### General view

The TDM Lines general view, shown below, provides information about the physical line interfaces of a TDM module and the line services that they carry. From this view you can know the status of line interfaces and line services by seeing if they are up, down, defective, or in an alarmed state. Selecting an active link will display the detailed view for line interfaces and line services.

![Toolpack v2.5 TDM Lines Tab](https://docs.telcobridges.com/w/images/9/92/Toolpack_v2.5_TDM_Lines_Tab.png)

### Line Interface Detailed Status

The detailed status view for each line interface allows you to reset status, or view extended status.

![Toolpack v2.5 Line Interface Status](https://docs.telcobridges.com/w/images/7/79/Toolpack_v2.5_Line_Interface_Status.png)

### Line Service Detailed Status

The detailed status view for each line service allows you to reset the service's status, or to set the **loopback mode** in the **loopback** drop-down box.

![Toolpack v2.5 Line Service Status](https://docs.telcobridges.com/w/images/2/27/Toolpack_v2.5_Line_Service_Status.png)


---

# 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/other-pages/hardware-and-clock/status-menus-tdm-lines.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.