> 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/developer-reference/toolpack-api/toolpack-engine.md). # toolpack engine ### Started By Toolpack\_engine is spawned by [tboamapp](/telecom-references/developer-reference/toolpack-api/tboamapp.md). ### Role Toolpack\_engine is use to allocate the 'dynamic' part of the call. It receives the nap list from the toolpack\_sys\_manager, sends events and receives command from the Toolpack application(Gateway application). It is responsible for: * Process incoming call, sends an event to the Toolpack application(Gateway application) * Allocate resources (stream, dsp) * Connect resources together. ### High Availability [Toolpack\_engine](/telecom-references/developer-reference/toolpack-api/toolpack-engine.md) is a [Active/Standby](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) type of application. The first [toolpack\_engine](/telecom-references/developer-reference/toolpack-api/toolpack-engine.md) instance to be ready will become [active](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby), if other instances are ready they will remain [standby](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby). The [standby](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) instances won't take any actions on the system as long as the [active](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) instance is functioning. In the eventuality where the [active](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) instance crash or is stop, the [standby](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) instance will become [active](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby). The [active](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby) instance of toolpack\_engine is responsible for: * Sending call leg events to the [gateway](/telecom-references/parameter-reference/gateway.md) or user application. * Handling call legs requests from the [gateway](/telecom-references/parameter-reference/gateway.md) or user application. * Allocating / modifying / freeing call legs. * Handling the [resynchronization](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/resynchronization) of the calls after a [switchover](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/switchover). The toolpack\_engine is not responsible for: * Handling call flow (this responsibility falls to the [gateway](/telecom-references/parameter-reference/gateway.md) or user application). **NOTE:** * The toolpack\_engine cannot be controlled by more than one application (one [gateway](/telecom-references/parameter-reference/gateway.md) application for example). * The application that controls the toolpack\_engine must work in active/standby fashion too. * The toolpack\_engine will grant control to the first application that connects to it. ### Resynchronization During the [resynchronization](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/resynchronization), the toolpack\_engine will keep the [active calls](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-calls) but will terminate all the [transient calls](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/transient-calls). ### Logs * Where the logs are located? > \[InstallDir]/toolpack/setup/[*SystemId*](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/system-id)/*MajorVersion*/apps/toolpack\_engine/ /lib/tb/toolpack/setup/12358/3.3/apps/toolpack\_engine/ --- # 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/telecom-references/developer-reference/toolpack-api/toolpack-engine.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.