> 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/telecom-references/apis-and-integration/toolpack-version-2-5-adb.md). # Toolpack version 2.5 ADB Important Notice: The \*\*A\*\*dvanced \*\*D\*\*evelopment \*\*B\*\*ranch is no longer supported. It is NOT possible to use the configuration created with the ADB with the regular Toolpack 2.5 branch. To install Toolpack 2.5 on an \*\*A\*\*dvanced \*\*D\*\*evelopment \*\*B\*\*ranch system you are require to: * Completely uninstall Toolpack from the system. * Erase the toolpack\_0 database in MySQL. * It is highly recommended to run the [validation guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/legacy/validate-toolpack-installation-2-5/README.md) to verify that all prerequisites are correctly installed before installing the new version ### Advanced Development Branch The **A**dvanced **D**evelopment **B**ranch currently known as Toolpack 2.5 is an advanced release of the Toolpack framework containing new APIs and functionalities. It is meant for system integrators and solution vendors requiring access to these new features and system calls to engage their development or testing process. The traditional release cycle has been accelerated to allow an early access of these new features and reduce the development cycle of our customers' systems. They can now build and test their new application in lab while synchronizing the release of the complete system with TelcoBridges' release of the final Toolpack 2.5 branch. This branch went through the standard TelcoBridges Q\&A process to insure that critical portions of the product are stable (i.e. installation, migration, system startup, configuration). However, in order to bring the functionality into the hands of developing customers earlier, there are a few important differences between an Advanced Development Branch and a regular product branch: * The main focus for the Advanced Development Branch is to deliver a specific feature set to developer. Complete regression testing and cross-dependency tests may have been omitted. * Q\&A will not have covered testing on all supported OSes. Only a few have been targeted. * Although TelcoBridges has invested large effort to run Q\&A tests and fixes across the complete Toolpack feature set, some features or options may not be fully working. Any blocking issue for testing can be addressed through the support department using the regular process. * The Advanced Development Branch is NOT to be installed in a production setup. It is meant for lab integration, development and testing only. Deploying a system using that branch is not recommenced and the customer will do it as his own risks. Please contact TelcoBridges' support up-front in case an early deployment is desired. * Although TelcoBridges will try to minimizes the changes, subsequent releases of the advanced development branch may include API and service affecting behavior changes which is not usually permitted between minor releases of a normal branch. * Eventually, the advanced development branch will be replaced with an official release of the branch. At that point, TelcoBridges will be commited in maintaining the official release of the branch. Any previous version of the Advanced Development Branch will be obsoleted. ### Advance Development Branch New Feature Toolpack version 2.5 ADB provides the following new feature: **Support for** [**Media Leg API**](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/caf-working-with-call-legs/README.md) * This release of Toolpack allows the use of the media resources (TDM channels, RTP streams), without having to use the signaling stacks provided by TelcoBridges. This allows customers to use their own SIP stack, and use the high-performance RTP and vocoding from TelcoBridges. The same can be done with SS7 and Sigtran on the TDM network. The Media Leg API can be used in conjunction with the Call Leg API, thus having a hybrid system. **List of releases that are included in the v2.5 Advanced Development Branch:** Please use [Version 2.5](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/legacy/toolpack-version-2-5/README.md) *Updated September 29 2010* ### References * [Toolpack system v2.5 installation guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/legacy/toolpack-installation-2-5/README.md) * [Uninstall procedure for release v2.5 (same as v2.3)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/uninstalling-toolpack-manually/README.md) * [Major upgrade procedure for Toolpack release v2.5](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/legacy/toolpack-major-upgrades-2-5/README.md) * Minor upgrade procedure for Toolpack release v2.5 * [License upgrade procedure for Toolpack release v2.5 (same as v2.3)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/add-change-licenses/README.md#change-licenses) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/apis-and-integration/toolpack-version-2-5-adb.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.