> 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/other-pages/operations/verify-licenses.md).

# Verify Licenses

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

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 following the addition of a hardware module. After you have installed the license, you need to verify the license installation result.

###

Verifying licenses via the Web portal

1. Got to the Hardware Unit's Status page ![Verify Licenses 1](https://docs.telcobridges.com/w/images/9/95/Verify_Licenses_1.png)
2. Select the hardware serial number
3. In the "States" tab, look for the below fields:
4. Oam last license install result
5. Oam last license install time
6. License about to expire
7. License expired
8. License days left ![Verify Licenses 2](https://docs.telcobridges.com/w/images/4/41/Verify_Licenses_2.png)
9. Try to reload the page in case if the license installation is still in progress. Monitor the process by pressing the *now* button from time to time. ![Verify Licenses 3](https://docs.telcobridges.com/w/images/e/e1/Verify_Licenses_3.png)
10. Check the license details in the "Licensed features" tab ![Verify Licenses 4](https://docs.telcobridges.com/w/images/8/88/Verify_Licenses_4.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://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/verify-licenses.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.