| Audium error VoiceXML page has problems on Nuance voice browsers |
| Categories: Audium 3.3.x |
| Article ID: | 20 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
The Audium backup error VoiceXML page is incompatible with Nuance voice browsers.
SYMPTOMS
On rare occasions, an error prompts the playing of the voice browser specific error message rather than any error message specified by the developer or Audium.
A Nuance voice browser specific error message is heard. Additional symptoms is the Audium global error log (AUDIUM_HOME/logs/error_logDATE.txt) listing "bad_url:".
RESOLUTION
When an error occurs running Audium, there are four levels of consequences for that error. They are listed in priority order.
- The error is thrown by a custom element and is caught within that element. In this case, the element decides what do so, such as returning an appropriate exit state. In this situation, Audium is unaware an error occurred.
- The error is not caught from within a custom element, the error is listed in the error log, and the caller is handled by the Error Element in the application. Each application can define an Error Element which is a voice element that is run when an error occurs. This is simply a way to handle the caller and let them know that something happened. Most of the time this element is an audio or a transfer.
- The Error Element is not defined so when an error occur, the message specified in the application's Settings Pane in the Audium Builder is played followed by a hangup.
- If an error occurs such that the Audium Server is unable to determine which application a caller was meant to access, a backup VoiceXML error page is produced playing an error message followed by a hangup.
It is this backup VoiceXML page which causes the issue. Since the Audium Server could not determine which application the caller meant to access, and since the voice browser choices are made on the application level, the Audium Server does not know which browser to produce VoiceXML for. It therefore produces a VoiceXML page designed to work on as many of the supported voice browsers as possible. The VoiceXML page produced, however, does not contain a DOCTYPE tag within it since that would apply only to Nuance browsers and would cause errors in non-Nuance browsers. Unfortunately, with Nuance browsers, not including the DOCTYPE will prompt the browser to throw an error. It is this error which prompts the playing of the voice browser-specific error message. Note that there are only three situations which would cause this error to occur:
- The browser was configured with an improper URL referring to a non existing application. For example, if the browser was configured to call http://myserver.com/Audium/Server?audium_application=foo and there was no application named "foo" on the Audium Server, this error page would be returned.
- If the Audium session timed out during a phone call, this error would be produced since the voice browser will make a request for a VoiceXML page in a session that no longer exists on the Audium Server side. This would occur only if the session timeout were set to a small value and the caller was encountering a single VoiceXML page on the browser for that length of time. With the session timeout set to 30 minutes by default, this situation would almost never occur.
- The voice browser or some proxy in between produced an HTTP request to the Audium Server that it could not recognize or the Java application server on which Audium is installed somehow independently lost session information. These situations are also extremely rare.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment