Article ID:	215
Last updated:	January 14, 2007

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

This article provides one solution to the problem of an Audium application that produces no audio, but also does not log errors.  In this case, it is related to the ASR engine's license.

SYMPTOMS

An Audium application is called, but no audio is heard.  Examining the Audium logs does not reveal any errors.  The voice browser log may show an error related to the ASR engine.

RESOLUTION

If the license for your ASR engine is either expired or invalid, then no audio will be heard when an Audium application is called.  This scenario may also apply to Audium applications that only accept DTMF input, if they are deployed in an environment that normally includes an ASR engine.

When the voice browser processes the VoiceXML that the Audium application produces, it encounters requests to access the ASR engine.  If the engine is not accessible, then no audio will be heard.  While the Audium logs will not log this error, the voice browser logs will.  Replacing the ASR engine's license with a valid license will resolve this issue.

Please note that some voice browsers may play an error message to the caller, rather than only silence.  Additionally, other ASR engine problems (i.e. other than an invalid license) may result in similar behavior.