Toolpack Application:toolpack engine - Revision history

Lucas Trottier: Correct high availability explanation - Engine does not fallback on primary.

2013-07-24T03:22:43Z

Correct high availability explanation - Engine does not fallback on primary.

Cbilodeau: merge information from other toolpack engine page

2011-02-15T20:37:39Z

merge information from other toolpack engine page

Sylvain Fontaine: Updated with new parameter names.

2009-07-07T21:14:32Z

Updated with new parameter names.

Cbilodeau at 17:39, 29 May 2009

2009-05-29T17:39:10Z

Cbilodeau: New page: == 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 ap...

2009-05-21T19:53:06Z

New page: == 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 ap...

New page

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

== Logs ==
*Where the logs are located?
: [InstallDir]/toolpack/setup/''TbxGwPort''/''MajorVersion''/apps/toolpack_engine/
: /lib/tb/toolpack/setup/12358/2.3/apps/toolpack_engine/
: C:\TelcoBridges\toolpack\setup\12358\2.3\apps\toolpack_engine\

@@ Line 15: / Line 15: @@
 == 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]].
+[[Toolpack_Application:toolpack_engine |Toolpack_engine]] is a [[Active/Standby]] type of application. The first [[Toolpack_Application:toolpack_engine |toolpack_engine]] instance to be ready will become [[Active/Standby |active]], if other instances are ready they will remain [[Active/Standby |standby]]. 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:
@@ Line 30: / Line 30: @@
 *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 ==

@@ Line 1: / Line 1: @@
 == 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).
@@ Line 6: / Line 11: @@
 *Allocate resources (stream, dsp)
 *Connect resources together.

@@ Line 10: / Line 10: @@
 == Logs ==
 *Where the logs are located?
-: [InstallDir]/toolpack/setup/[[Gateway_Port|''TbxGwPort'']]/''MajorVersion''/apps/toolpack_engine/
+: [InstallDir]/toolpack/setup/[[System_Id|''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\