10.3.  Overview of Demonstration Programs

An overview of the sequence of events demonstrated by the Console and GUI Demonstration Programs and the various channel and application states is presented in the following paragraphs.

Figure 10.  Application and Channel States illustrates the application states while waiting for and then processing an inbound call. After receiving an inbound call, the application plays an introductory message and listens for an access code to be entered. If the application does not detect an access code, a message can be recorded; otherwise, if an access code is detected, it is validated and if valid, the previously recorded message is played. The application then plays a goodbye message and sets up for the next call.

Figure 10.  Application and Channel States

Table 15.  Demonstration Program States

State	Type	Description
ONHOOK	Channel	Channel is onhook.
WAIT_RING	Application	Application is waiting for an inbound call.
OFFHOOK	Channel	When application detects an inbound call, the channel goes OFFHOOK.
PLAY_INTRO	Application	After receiving an inbound call, application plays an introductory message (i.e., INTRO.VOX file). Channel must be in OFFHOOK state.
GET_DIGIT	Application	If application detects digits being entered while playing the introductory message, it collects and validates the digits.
PLAY_INVALID	Application	Invalid access code was entered and a message (i.e., INVALID.VOX file) is played.
RECORD_FILE	Application	If application does not detect digits being entered after playing the introductory message, a message can be recorded. Channel must be in OFFHOOK state.
PLAY_MSGFILE	Application	If a valid access code was entered after playing the introductory message and GET_DIGIT state, then the previously recorded message is played.
PLAY_GOODBYE	Application	A goodbye message is played (i.e., GOODBYE.VOX file) after one of the following states - PLAY_INVALID, RECORD_FILE, or PLAY_MSGFILE.

Click here to contact Dialogic Customer Engineering