|
| Voice Extensible Markup Language (VoiceXML) |
|
Training Schedule
26 to 30 January 2009
4 to 8 May 2009
Go to the Training Page
This site serves as an addional resource to the host of VoiceXML resources on the web. But with a difference, the
online tutorial is a quick quick start guide to go from "Hallo World" to a complete and fully fledged VoiceXML application.
The basic VoiceXML architecture can be explained as follow:
Document Server
A document server (for example a web server) receives requests from a VoiceXML browser through the VoiceXML browser context.
The VoiceXML browser context is the platform on which the VoiceXML browser is running. The document server produces in reply, these
documents are VoiceXML documents which the VoiceXML browser can in turn interpret. The VoiceXML browser context, the platfrom on
which the voiceXML browser is running, also handles the network intefacing, be it normal PSTN or VoIP.
This VoiceXML browser context may also monitor user inputs in parallel with the VoiceXML browser. For instance,these inputs can be voice,
DTMF or a voice message.
Implementation Platform
The Implementation Platfrom is controlled by the VoiceXML browser context and by the VoiceXML browser. Usualy the VoiceXML browser contct is responsible for
detecting an incoming call, acquiring the initial VoiceXML document, and answering the call, while the VoiceXML browser looks
after the call is answered, in terms of the call dialog. The implementation platform generates events in response to user actions (e.g. spoken or character
input received, disconnect) and system events. Some of these events are acted upon by the VoiceXML browser itself, as specified
by the VoiceXML document, while others are acted upon by the VoiceXML browser context.
Applications
An application can be contained within one document. However, to make the application more manageable, n application is a set of documents sharing the
same application root document, this in website terms, can be seen as the index page. Whenever the user interacts with a document whithin an application,
its application root document is also loaded. The application root document remains loaded while the user is transitioning between other documents
in the same application, and it is unloaded when the user transitions to a document that is not in the application. While it is loaded, the application root
document's variables are available to the other documents as application variables.
This site is sponsored by:
C.a.T.S. supports the following platforms:
|
