Audium Knowledge Base

Knowledgebase Home | Contact Knowledgebase Home | Contact
Search the Knowledgebase Jump to ID Browse by Category
How to debug calls that experience an unexpected error message
Categories: Step-by-step debugging tips
Article ID: 290
Last updated: January 12, 2007
User Opinions
No users have voted.

How would you rate this answer?
Helpful
Not helpful

When I call into my application, system hangs up up on me without any message, an error message is played back or I hear TTS instead of pre-recorded audio files

Make sure that Call Services started properly and that there were no errors during startup.

The following article helps to debug issues related to Call Services startup:

Make sure that the voice application loads properly and that there are no errors during startup.

The following article helps to debug issues related to loading a voice application:

When I call, system hangs up without any error messages
When I call, I hear a generic error message: "Sorry. There has been an error." 
When I call into my application I do not hear my prerecorded audio files, only TTS text.

How to debug calls that end in an immediate hangup with no error audio

How to debug issues when an application plays back an error message

This issue can be caused by two most common errors:

  • incorrect URL and/or missing audio files
  • audio encoding format is not supported by the voice browser

Note that it is a voice browser that fetches and plays back those files, not Call Services; therefore, those files have to be accessible and supported by the voice browser.

The following articles describe those two most common issues and steps to address those problems:

Visitor Comments
No visitor comments posted. Post a comment
Related Questions
No related questions were found.
Attachments
No attachments were found.

Copyright (c) 2005 Audium Corporation. All rights reserved.
Audium Home | Audium Support Center Home | Audium Customer Care Home