use_case_bridge_server.
Copyright © 2005-2006 Ericsson
Version: 1.0
Behaviour: gen_server.
Authors: Freek Sanders (freekisanders@gmail.com) [web site: http://www.freeksanders.tk].
use_case_bridge_server.
Use-Case-Single-Bridge is started by the BridgeServer and communicates with both the BridgeServer and ExtENS.
Use-Case-Single-Bridge can be started in two ways:
(see use_case_single_bridge).
Through the BridgeServer, when he calls start_link_incoming, and this is the A party.
When this happens, the SingleBridge sends a message to ExtENS to indicate that a call came in.
After a certain period, a 'hangup' message might be received from BridgeServer, after which SingleBridge passes this message onto ExtENS and dies.
Through ExtENS, when this SingleBridge is the B party.
When this happens, the SingleBridge contacts the BridgeServer so as to create a new leg and route this.
As a result, the SingleBridge gets a leg id back from the BridgeServer (see use_case_single_bridge:set_leg_id/2).
After the leg has attached, the SingleBridge gets a 'attached' message (see use_case_single_bridge:leg_attached/1).
After a certain period, a 'hangup' message might be received from ExtENS, after which SingleBridge passes this message onto the BridgeServer and dies.
Use-Case-Single-Bridge has been implemented using the gen-server behaviour. This means that all function calls returning 'ok' (see below) are gen_server casts, which carry out their function asynchronously. An 'ok' does not mean success. If a function has success or not can only be derived from side-effects and messages printed to the command line.
For more information about the flow of events and an explanation of terms seeext_ast_interface.
| die/0 | Destroys the use case. |
| start_link/4 |
die() -> ok
Destroys the use case.
Introduced in: 1.0