Toolpack Application:gateway

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(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...)
 
(High Availability)
 
(7 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
== Started By ==
 +
 +
Gateway is spawned by [[Toolpack_Application:tboamapp |tboamapp]].
 +
 +
 
== Role ==
 
== 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.
+
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:
 
It is responsible for:
*Found a matching route to the incoming call leg through routing scheme.
+
*Handling call flow
*Remap call parameters when it is required
+
*Accepting / rejecting call legs.
*Tell the toolpack_engine to create an outgoing call leg.
+
*Routing call legs to the destination naps, according to routing script, and call profile parameters
*Once the call is answer, tell the toolpack_engine to connect both legs.
+
*Sending / writing [[Text_Call_Detail_Records_(CDR)|CDR]] information.
*Once hang up, tell the toolpack_engine to unjoin and free the call.
+
*Starting play / relay stream for [[Early_Media |early media]].
 +
*Remapping call parameters when required
 +
 
 +
== 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|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 ==
 +
 
 +
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]].
  
  
 
== Logs ==
 
== Logs ==
*Where the logs are located?
+
The logs for the Toolpack Gateway Application as follows:
: [InstallDir]/toolpack/setup/''TbxGwPort''/''MajorVersion''/apps/gateway/
+
: [InstallDir]/toolpack/setup/[[System_Id|''SystemId'']]/''MajorVersion''/apps/gateway/
 
: /lib/tb/toolpack/setup/12358/2.3/apps/gateway/
 
: /lib/tb/toolpack/setup/12358/2.3/apps/gateway/
 
: C:\TelcoBridges\toolpack\setup\12358\2.3\apps\gateway\
 
: C:\TelcoBridges\toolpack\setup\12358\2.3\apps\gateway\

Latest revision as of 22:05, 23 July 2013

Contents

Started By

Gateway is spawned by tboamapp.


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.

It is responsible for:

  • Handling call flow
  • Accepting / rejecting call legs.
  • Routing call legs to the destination naps, according to routing script, and call profile parameters
  • Sending / writing CDR information.
  • Starting play / relay stream for early media.
  • Remapping call parameters when required

High Availability

Gateway is a Active/Standby type of application. The first instance of the Gateway application to be detected by the toolpack_engine will become active and will be the only instance to take action in the system. In the eventuality where the active instance is unavailable the Standby instance will become active. Since there is no preferred instances, the Gateway application don't fall back to the primary host.

Resynchronization

When becoming active, the Gateway instance retrieves all the active calls from Toolpack_engine. The transient calls will be released by the Toolpack_engine.


Logs

The logs for the Toolpack Gateway Application as follows:

[InstallDir]/toolpack/setup/SystemId/MajorVersion/apps/gateway/
/lib/tb/toolpack/setup/12358/2.3/apps/gateway/
C:\TelcoBridges\toolpack\setup\12358\2.3\apps\gateway\
Personal tools