Inbound calls

The initial call handling can be done in two ways:

Blueworx Voice Response automatically answers each inbound call, and uses information in the call to identify a corresponding application profile; it can then pass the call to the appropriate voice application and continue as in steps 1 to 7 below. Many different applications can be running simultaneously, possibly in a combination of the CCXML, VoiceXML, Java and state table programming environments.
As an alternative, Blueworx Voice Response can be configured so that incoming calls are passed directly to a CCXML application (in ALERTING state) before the call is answered. This has the advantage that the CCXML application, prior to connecting the call, can query:
- Call information
- Application availability
- For service providers, play a simple information message (if the switch supports this facility)
CCXML could reject or redirect the call, in which case the inbound call would be terminated, and the remaining steps below would not apply. However, if CCXML connects the call, it can then invoke VoiceXML or Java applications to handle the dialogs, and continue as below:

The application plays a greeting (sometimes called an announcement) to callers, and then prompts them to indicate the information they want. The greeting can be prerecorded or can use text-to-speech technology. Callers can interrupt the prompt if they already know what they want to do.
The application can be designed to play greetings in different languages depending on information such as the number that callers dialed, or the callers' own numbers.
The application waits for callers to respond for a set period of time. Callers can either respond, either by
- speaking (if speech recognition is implemented)
- pressing keys on a DTMF phone, ranging from a single digit (such as 1 for yes or 2 for no) to multiple digits (such as a catalog number or personal identification number)
If the response does not match the criteria you have defined (such as a specific number of digits), the voice application can prompt callers to enter the response again.
When the waiting period has elapsed, the application can prompt the caller again, as often as you think necessary.
The application takes whatever action is appropriate to the caller's response; for example, retrieving information from a database, host system, or file system and speaking it to callers; updating information in a database; storing or retrieving a voice message; or making another call.
After taking action, the application should tell the caller again what to do next.
The caller might indicate, in response to a prompt, that the interaction is over. The application can respond by saying good-bye, then disconnect, or the caller might simply hang up. If the caller hangs up, the application can detect this, and automatically disconnect itself.