Copyright © 2005-2006 Ericsson
Version: 1.0
Behaviour: gen_server.
Authors: Freek Sanders (freekisanders@gmail.com) [web site: http://www.freeksanders.tk].
idefisk_supervisor) and communicates with a given Ext-Ast-Interface instance through its process id.
Use-Case-Stub uses Use-Case-Call (see use_case_call) to keep an intern record of created calls, legs and resources, as well as to receive messages.
DESCRIPTION OF THE FLOW OF EVENTS
Set asterisk_ext_module to 'use_case_stub' : {asterisk_ext_module, use_case_stub}
Set asterisk_ext_module_start to 'true' : {asterisk_ext_module_start, true}
Set asterisk_ext_module_args to the Stub : {asterisk_ext_module_args, [StubArgs::Stub_args()]}
StartId is where the id of the place where the Stub begins.
This can be a integer, atom or string.
Use-Case-Stub 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 see ext_ast_interface.
id() = integer() | atom() | string()
| die/0 | Destroys the use case. |
die() -> ok
Destroys the use case.
Introduced in: 1.0