> 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/configuration/web-portal-3-3/hardware/new-hardware/adding-an-adapter.md).

# Adding an Adapter

> **Applies to:** Tmedia 2.5

When you receive a new system, by default at least one hardware configuration will have been set in the Toolpack application server. To add other hardware devices, you must use the Tmedia [Web Portal](/other-pages/other/web-portal.md).

![Schematic showing 2 TMP6400 devices with an external server and a second machine with a web browser](https://docs.telcobridges.com/w/images/2/2d/Schematic-pair-of-tmp6400s.jpg)

To add one or more additional hardware devices to the Toolpack system configuration, their serial numbers must be registered with the Toolpack application server.

**To add a hardware device:**

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

![Toolpack v2.5 Navigation Panel Hardware](https://docs.telcobridges.com/w/images/7/78/Toolpack_v2.5_Navigation_Panel_Hardware.png)

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

![Toolpack v2.5 Create Hardware](https://docs.telcobridges.com/w/images/9/9d/Toolpack_v2.5_Create_Hardware.png)

3- 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 the appropriate **hardware device** from the Adapter Type field.
* Select **Enabled** from the Target State field.
* Click **Create**

![Toolpack v2.5 Creating Hardware](https://docs.telcobridges.com/w/images/c/c3/Toolpack_v2.5_Creating_Hardware.png)

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

![Toolpack v2.5 Hardware Created](https://docs.telcobridges.com/w/images/4/49/Toolpack_v2.5_Hardware_Created.png)

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Serial](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#s)
* [Adapter Type](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#a)
* [Graceful Upgrade Timeout](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#g)
* [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)


---

# 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/configuration/web-portal-3-3/hardware/new-hardware/adding-an-adapter.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.