Actions

Toolpack Application:gateway: Difference between revisions

No edit summary
(Updated with new parameter names.)
Line 12: Line 12:
== Logs ==
== Logs ==
The logs for the Toolpack Gateway Application as follows:
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/
: /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\

Revision as of 17:14, 7 July 2009

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:

  • Finding a matching route to the incoming call leg through routing scheme
  • 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


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\