Toolpack Application:gateway - Revision history

Lucas Trottier: /* High Availability */

2013-07-24T03:05:29Z

High Availability

Abrassard: /* Role */

2011-05-30T11:47:40Z

Role

Cbilodeau: remove self links

2011-02-15T20:56:33Z

remove self links

Cbilodeau: merge information from other gateway page

2011-02-15T20:52:27Z

merge information from other gateway page

Ktrueman: fixed link

2009-07-17T19:18:33Z

fixed link

Sylvain Fontaine: Updated with new parameter names.

2009-07-07T21:14:58Z

Updated with new parameter names.

Cbilodeau at 17:41, 29 May 2009

2009-05-29T17:41:34Z

10.0.0.210 at 20:48, 22 May 2009

2009-05-22T20:48:40Z

Cbilodeau: New page: == Role == Gateway Application is use to bridge 2 call legs, according to a set of routes. It receives incoming calls from the toolpack_engine, tries to find a matching route, remapped cal...

2009-05-21T20:05:29Z

New page: == Role == Gateway Application is use to bridge 2 call legs, according to a set of routes. It receives incoming calls from the toolpack_engine, tries to find a matching route, remapped cal...

New page

== Role ==
Gateway Application is use to bridge 2 call legs, according to a set of routes. It receives incoming calls from the toolpack_engine, tries to find a matching route, remapped call parameters if needed and tells the toolpack_engine to generate an outgoing call.

It is responsible for:
*Found a matching route to the incoming call leg through routing scheme.
*Remap call parameters when it is required
*Tell the toolpack_engine to create an outgoing call leg.
*Once the call is answer, tell the toolpack_engine to connect both legs.
*Once hang up, tell the toolpack_engine to unjoin and free the call.

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

@@ Line 17: / Line 17: @@
 == High Availability ==
-Gateway is a [[Active/Standby]] type of application. The first instance of the Gateway application to be detected by the [[Toolpack_Application:toolpack_engine |toolpack_engine]] will become [[Active/Standby|active]] and will be the only instance to take action in the system. In the eventuality where the [[Active/Standby|active]] instance is unavailable the [[Active/Standby|slave]] instance will become [[Active/Standby|active]]. Since there is no preferred instances, the Gateway application don't fall back to the [[Primary/Secondary|primary]] host.
+Gateway is a [[Active/Standby]] type of application. The first instance of the Gateway application to be detected by the [[Toolpack_Application:toolpack_engine |toolpack_engine]] will become [[Active/Standby|active]] and will be the only instance to take action in the system. In the eventuality where the [[Active/Standby|active]] instance is unavailable the [[Active/Standby|Standby]] instance will become [[Active/Standby|active]]. Since there is no preferred instances, the Gateway application don't fall back to the [[Primary/Secondary|primary]] host.
-−
 == Resynchronization ==

@@ Line 10: / Line 10: @@
 *Handling call flow
 *Accepting / rejecting call legs.
-*Routing call legs to the destination naps, according to routing scheme.
+*Routing call legs to the destination naps, according to routing script, and call profile parameters
 *Sending / writing [[Text_Call_Detail_Records_(CDR)|CDR]] information.
 *Starting play / relay stream for [[Early_Media |early media]].
 *Remapping call parameters when required
 == High Availability ==

@@ Line 18: / Line 18: @@
 == High Availability ==
-[[Toolpack_Application:gateway |Gateway]] is a [[Active/Standby]] type of application. The first instance of the [[Toolpack_Application:gateway |Gateway]] application to be detected by the [[Toolpack_Application:toolpack_engine |toolpack_engine]] will become [[Active/Standby|active]] and will be the only instance to take action in the system. In the eventuality where the [[Active/Standby|active]] instance is unavailable the [[Active/Standby|slave]] instance will become [[Active/Standby|active]]. Since there is no preferred instances, the [[Toolpack_Application:gateway |Gateway]] application don't fall back to the [[Primary/Secondary|primary]] host.
+Gateway is a [[Active/Standby]] type of application. The first instance of the Gateway application to be detected by the [[Toolpack_Application:toolpack_engine |toolpack_engine]] will become [[Active/Standby|active]] and will be the only instance to take action in the system. In the eventuality where the [[Active/Standby|active]] instance is unavailable the [[Active/Standby|slave]] instance will become [[Active/Standby|active]]. Since there is no preferred instances, the Gateway application don't fall back to the [[Primary/Secondary|primary]] host.
 == Resynchronization ==
-When becoming [[Active/Standby|active]], the [[Toolpack_Application:gateway |Gateway]] instance retrieves all the [[Active_Calls |active calls]] from [[Toolpack_Application:toolpack_engine |Toolpack_engine]]. The [[Transient_Calls |transient calls]] will be released by the [[Toolpack_Application:toolpack_engine |Toolpack_engine]].
+When becoming [[Active/Standby|active]], the Gateway instance retrieves all the [[Active_Calls |active calls]] from [[Toolpack_Application:toolpack_engine |Toolpack_engine]]. The [[Transient_Calls |transient calls]] will be released by the [[Toolpack_Application:toolpack_engine |Toolpack_engine]].

@@ Line 1: / Line 1: @@
 == Role ==
 Gateway Application is used to bridge 2 call legs, according to a set of routes. The Gateway Application receives incoming calls from [[Toolpack Application:toolpack engine|toolpack_engine]], tries to find a matching route, remaps call parameters if required, and then tells toolpack_engine to generate an outgoing call.
 It is responsible for:
-*Finding a matching route to the incoming call leg through routing scheme
+*Handling call flow
 *Remapping call parameters when required
-*Telling toolpack_engine to create an outgoing call leg
-*Once the call is answered, telling toolpack_engine to connect both legs
-*Once the call is hung up, telling toolpack_engine to unjoin and to free the call
+== High Availability ==

@@ Line 1: / Line 1: @@
 == Role ==
-Gateway Application is used to bridge 2 call legs, according to a set of routes. The Gateway Application receives incoming calls from [[toolpack_engine]], tries to find a matching route, remaps call parameters if required, and then tells toolpack_engine to generate an outgoing call.
+Gateway Application is used to bridge 2 call legs, according to a set of routes. The Gateway Application receives incoming calls from [[Toolpack Application:toolpack engine|toolpack_engine]], tries to find a matching route, remaps call parameters if required, and then tells toolpack_engine to generate an outgoing call.
 It is responsible for:

@@ Line 12: / Line 12: @@
 == Logs ==
 The logs for the Toolpack Gateway Application as follows:
-: [InstallDir]/toolpack/setup/[[Gateway_Port|''TbxGwPort'']]/''MajorVersion''/apps/gateway/
+: [InstallDir]/toolpack/setup/[[System_Id|''SystemId'']]/''MajorVersion''/apps/gateway/
 : /lib/tb/toolpack/setup/12358/2.3/apps/gateway/
 : C:\TelcoBridges\toolpack\setup\12358\2.3\apps\gateway\