| An Audium application does not log properly, and terminates prematurely |
| Categories: Audium Call Services 3.4.x and 3.5 |
| Article ID: | 50 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
An Audium application that uses a VoiceXML Insert element is not adding data to the log as expected, and is prematurely terminating calls.
SYMPTOMS
Active callers are dropped when they reach the VoiceXML Insert element in the callflow, and the log after this point may not contain any information. This happens consistently with the application in question, when the problem VoiceXML Insert element is visited. However, the same VoiceXML may work without a problem outside of an Audium application.
RESOLUTION
While few constraints are placed on the VoiceXML used in VoiceXML Insert elements, there are some guidelines that should be followed to ensure compatability with Audium. In this particular problem, the cause is that the Audium log is being written to (i.e. "audium_vxml_log"), and the variable named "audium_element_start_time_millisecs" has not yet been set to the current time. The following line should occur early in the first document of your VoiceXML, certainly before any logging attempts are made:
<assign name="audium_element_start_time_millisecs" expr="new Date().getTime()" />
For more information about this line, as well as detailed information about other guildelines that should be followed when using custom VoiceXML with VoiceXML Insert elements, please refer to the User Guide.
|
| 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