> 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/system/upload-software-license/uploading-a-license.md).

# Uploading a License

> **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3

TelcoBridges uses a license-based approach to activate various software or hardware functions in Toolpack or the underlying hardware. When installing Toolpack, implementing new software capabilities, or after the addition of a hardware module, you may need to add or modify a license. The following instructions will enable you to do so.

###

Uploading licenses via the Web portal

1. Click **Packages & Licenses** from the navigation panel. ![UploadSoftwareLicense 0 A](https://docs.telcobridges.com/w/images/b/be/UploadSoftwareLicense_0_A.png)
2. Click **Browse** and select the software license.
3. Click **Upload License**. ![UploadSoftwareLicense 2 A](https://docs.telcobridges.com/w/images/3/35/UploadSoftwareLicense_2_A.png)
4. Wait for the page to reload and monitor the process by pressing the *now* button, from time to time.
5. After a license update, click [here](/tmedia-documentation/other-pages/operations/verify-licenses.md) to see how to verify the license installation status.

**IMPORTANT: If you have hardware units, you will need to restart it to apply the changes after installing a new license, unless it is for extending the end date, or making it permanent.**

To do this, reboot the hardware unit (will drop active calls) Status -> Hardware Units -> Click on the unit Serial Number -> Reboot unit It will take about 1.5 minutes to restart the unit.

For more information see the [host control](/tmedia-documentation/other-pages/operations/host-control.md) page


---

# 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/system/upload-software-license/uploading-a-license.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.