> 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/other-pages/toolpack-engine.md).

# toolpack engine

### Started By

Toolpack\_engine is spawned by [tboamapp](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/tboamapp/README.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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/toolpack-engine/README.md) is a [Active/Standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) type of application. The first [toolpack\_engine](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/toolpack-engine/README.md) instance to be ready will become [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md), if other instances are ready they will remain [standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md). The [standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) instances won't take any actions on the system as long as the [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) instance is functioning. In the eventuality where the [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) instance crash or is stop, the [standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) instance will become [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md).

The [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) instance of toolpack\_engine is responsible for:

* Sending call leg events to the [gateway](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/gateway/README.md) or user application.
* Handling call legs requests from the [gateway](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/gateway/README.md) or user application.
* Allocating / modifying / freeing call legs.
* Handling the [resynchronization](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/resynchronization/README.md) of the calls after a [switchover](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/switchover/README.md).

The toolpack\_engine is not responsible for:

* Handling call flow (this responsibility falls to the [gateway](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/gateway/README.md) or user application).

**NOTE:**

* The toolpack\_engine cannot be controlled by more than one application (one [gateway](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/gateway/README.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://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/resynchronization/README.md), the toolpack\_engine will keep the [active calls](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-calls/README.md) but will terminate all the [transient calls](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/transient-calls/README.md).

### Logs

* Where the logs are located?

> \[InstallDir]/toolpack/setup/[*SystemId*](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/system-id/README.md)/*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 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/other-pages/toolpack-engine.md?ask=<question>&goal=<endgoal>
```

`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.