Toolpack Application:toolpack engine: Difference between revisions
(Updated with new parameter names.) |
(merge information from other toolpack engine page) |
||
| Line 1: | Line 1: | ||
== Started By == | |||
Toolpack_engine is spawned by [[Toolpack_Application:tboamapp |tboamapp]]. | |||
== Role == | == 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). | 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). | ||
| Line 6: | Line 11: | ||
*Allocate resources (stream, dsp) | *Allocate resources (stream, dsp) | ||
*Connect resources together. | *Connect resources together. | ||
== High Availability == | |||
Toolpack_engine is a [[Active/Standby]] type of application. The toolpack_engine instance running on the [[Primary/Secondary |primary]] host will always be preferred. Therefore the [[Active/Standby |active]] instance will always fallback to the [[Primary/Secondary|primary]] host when available. The [[Active/Standby |standby]] instances won't take any actions on the system as long as the [[Active/Standby |active]] instance is functioning. In the eventuality where the [[Active/Standby |active]] instance crash or is stop, the [[Active/Standby |standby]] instance will become [[Active/Standby |active]]. | |||
The [[Active/Standby |active]] instance of toolpack_engine is responsible for: | |||
*Sending call leg events to the [[Toolpack_Application:gateway |gateway]] or user application. | |||
*Handling call legs requests from the [[Toolpack_Application:gateway |gateway]] or user application. | |||
*Allocating / modifying / freeing call legs. | |||
*Handling the [[Resynchronization |resynchronization]] of the calls after a [[Switchover |switchover]]. | |||
The toolpack_engine is not responsible for: | |||
*Handling call flow (this responsibility falls to the [[Toolpack_Application:gateway |gateway]] or user application). | |||
'''NOTE:''' | |||
*The toolpack_engine cannot be controlled by more than one application (one [[Toolpack_Application:gateway |gateway]] 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 |resynchronization]], the toolpack_engine will keep the [[Active_Calls |active calls]] but will terminate all the [[Transient_Calls |transient calls]]. | |||
Revision as of 16:37, 15 February 2011
Started By
Toolpack_engine is spawned by tboamapp.
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 is a Active/Standby type of application. The toolpack_engine instance running on the primary host will always be preferred. Therefore the active instance will always fallback to the primary host when available. The standby instances won't take any actions on the system as long as the active instance is functioning. In the eventuality where the active instance crash or is stop, the standby instance will become active.
The active instance of toolpack_engine is responsible for:
- Sending call leg events to the gateway or user application.
- Handling call legs requests from the gateway or user application.
- Allocating / modifying / freeing call legs.
- Handling the resynchronization of the calls after a switchover.
The toolpack_engine is not responsible for:
- Handling call flow (this responsibility falls to the gateway or user application).
NOTE:
- The toolpack_engine cannot be controlled by more than one application (one gateway 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, the toolpack_engine will keep the active calls but will terminate all the transient calls.
Logs
- Where the logs are located?
- [InstallDir]/toolpack/setup/SystemId/MajorVersion/apps/toolpack_engine/
- /lib/tb/toolpack/setup/12358/2.3/apps/toolpack_engine/
- C:\TelcoBridges\toolpack\setup\12358\2.3\apps\toolpack_engine\