> 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/software-releases-and-backups/packages.md). # Packages The Packages section of the [Web Portal](/other-pages/other/web-portal.md) provides a list of releases of the system software installed on the device. These releases are called packages. A Package corresponds to a given release of the Toolpack system software comprising the Web Portal software, the Toolpack engine, the Media Gateway application, and code from the Toolpack API. The Toolpack software sees major upgrades between 2 and 3 times a year, with additional minor or point releases available more frequently. These can be installed on an optional basis. You should contact the TelcoBridges technical support department for questions regarding upgrades. They can be reached by e-mail at \[mailto: ]. While the actual installation of a new package is performed outside of the Web Portal, you can, using the web portal, upgrade from or rollback to a given version of the Toolpack system software. In fact multiple versions of this software, located in discreet directories, can be stored on the device at any given time, as long as required storage capacity is available. However, only a single version of the Toolpack system software can be active at any given moment. --- # 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/software-releases-and-backups/packages.md?ask=&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.