Toolpack Application:gateway
(merge information from other gateway page) |
m (remove self links) |
||
| Line 18: | Line 18: | ||
== High Availability == | == 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. | |
== Resynchronization == | == Resynchronization == | ||
| − | When becoming [[Active/Standby|active]], the | + | 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]]. |
Revision as of 16:56, 15 February 2011
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 scheme.
- 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 slave 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\
