| |
| | Java Call Control, Coordination, and Transactions |
 | | While there are important differences among these call models, reflecting the architecture or application for which they were intended, their overall goal is generally similar: to initiate, control, and manipulate calls, and to facilitate the development of applications that execute before, during, or after a call. |
 | | When call processing reaches a state in the FSM where a trigger is defined and enabled, processing is suspended and a program (called service logic) executing at a remote network element such as the SCP is invoked; call processing is resumed once the service logic completes execution. |
 | | The state of a telephone call is maintained by finite state machines associated with Call, Connection, and Terminal Connection objects (e.g., when a call is answered by the called party, the originating Connection object moves to the CONNECTED state). |
| www.comsoc.org /~ci/private/2000/jan/Jain.html (5707 words) |
|