> 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/ip-network/adding-transcoding-unit.md).

# Adding Transcoding Unit

> **Applies to:** SBC 3.1, 3.3

**To add a transcoding unit:**

1- Click **Hardware Units** in the navigation panel

![AddTranscodingHardware Tsbc 0](https://docs.telcobridges.com/w/images/e/e7/AddTranscodingHardware_Tsbc_0.png)

2- Click **Create New Unit**, to add a new hardware device

![Hardware 1 A](https://docs.telcobridges.com/w/images/e/e9/Hardware_1_A.png)

3- Enter information for the following parameters:

* Enter a **name** for the hardware device
* Enter the **serial number** of the new hardware device (filling in the Serial Number field will cause auto-completion of the field to occur).
* Select **TDM and/or IP** from the Type field.
* Enter the location in which the hardware device is installed.
* Enter a meaningful description about the use or purpose of the hardware device.
* Select **Enabled** from the Target State field.
* Select the type of TDM lines that the hardware device will support.
* Leave the Is N+1 Backup field empty.
* Provide the amount of time in seconds, that the system will wait for calls to complete before shutting down for an upgrade.
* Click **Create**

![AddTranscodingHardware Tsbc 1](https://docs.telcobridges.com/w/images/1/11/AddTranscodingHardware_Tsbc_1.png)

4- Verify that the **Unit was successfully created** message appears, and that the newly added hardware device appears in the **Hardware List**.

![Hardware 4 AA](https://docs.telcobridges.com/w/images/6/65/Hardware_4_AA.png)

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Serial Number](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#s)
* [Type](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#a)
* [Location](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#l)
* [Description](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#d)
* [Target State](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#t)
* [TDM Lines Type](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#t)
* [Is N+1 Backup](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#i)
* [Graceful Upgrade Timeout](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#g)


---

# 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/ip-network/adding-transcoding-unit.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.