> 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/operations/telcobridges-license-server.md).

# TelcoBridges License Server

**Note:** Starting from March 1 2022, the License server has been replaced with the [Customer Dashboard](/operations-and-support/customer-dashboard.md).

Our partners can view the list of units they have from TelcoBridges on the license server. For each unit it shows the **license expiration** date (if it is a temporary license), and the **warranty expiration** date for this unit.

Our partners can generate licenses from the license server at this URL:

<https://licenses.telcobridges.com>

For partners who do not have a login for the above site, please contact \[mailto:<support@telcobridges.com> TelcoBridges TB Support].

### Retrieve a license

For more details use one of these links:

* [Retrieving a license for TMG units](/other-pages/system-settings-licences-and-releases/retrieving-a-license.md)
* [Retrieving a license for FreeSBC and ProSBC units](/other-pages/software-releases-and-backups/downloading-a-license-for-sbc-units.md)

### Upload a license on the system

2.8 and onward: [Upload a license](/configuration/web-portal-3-3/system/upload-software-license/uploading-a-license.md)

2.7 and previous release: [Upload a license 2.7](/configuration/web-portal-3-3/system/upload-software-license/uploading-a-license.md)


---

# 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/operations/telcobridges-license-server.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.