> 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/h-248-megaco/selecting-timeslots-for-tdm-interfaces.md).

# Selecting Timeslots for TDM Interfaces

> **Applies to:** Tmedia 3.0, 3.2, 3.3

The final step in the H.248 configuration is to assign timeslots to the TDM interfaces that are associated with the H.248 configuration.

1- Click **H.248** in the naviagtion panel.

![Create H248 0](https://docs.telcobridges.com/w/images/7/7e/Create_H248_0.png)

2- Select the line service you wish to configure, in the H.248 configuration window

(**NOTE:** A timeslot mask can be applied to all line services at once by selecting **Timeslot mask for all line services** instead)

![Configure H248 LS 0](https://docs.telcobridges.com/w/images/1/17/Configure_H248_LS_0.png)

3- Select timeslots:

* Add the desired timeslots by **checking individual boxes**, or simply select all timeslots by clicking **Select all**
* Click **Save**

![Configure H248 LS 1](https://docs.telcobridges.com/w/images/f/f6/Configure_H248_LS_1.png)

4- Verify that the **"h248\_fix\_term\_cfg was successfully updated"** message appears

![Configure H248 LS 2](https://docs.telcobridges.com/w/images/8/89/Configure_H248_LS_2.png)

<details>

<summary>Northbound Interface</summary>

**Path**

```
h248_statcks->gateway_h248->h248_tdm_terminations->YourTrunk->TimeslotMask
```

</details>


---

# 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/h-248-megaco/selecting-timeslots-for-tdm-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.
