Article ID:	291
Last updated:	January 12, 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 explains how to debug a caller being dropped without any error message.

SYMPTOMS

The call is dropped without any error audio and the Call Services logs do not contain any errors.

RESOLUTION

The most likely cause of this issue is on the voice browser side. Note that once a call reaches Call Services, an error message will be played when an error occurs.

A common issue that can cause this behavior is when the URL for an application is misconfigured on the voice browser. The correct URL format is as follows:

http://YOUR_IP:PORT/Audium/Server?application=APP_NAME

where YOUR IP and PORT are the IP address and port number of the application server hosting Call Services, respectively, and APP_NAME is the name of the application to call into. Note that Call Services is case sensitive. Hence, MyFirstApplication is not the same as myfirstapplication.

Note that the application has to be running in order to be able to accept calls. Please refer to the following article describing how to debug issues when your application fails to load:

• How to debug issues when an application fails to load

Moreover, the issue can be related to ASR engine’s configuration and/or licenses. The following article explains this issue in detail:

• Nothing is heard when an Audium application is called, but there are no errors in the Audium logs

To make sure that your application works fine and can be called into, you might test it using a web browser, even from the same machine Call Services is installed on. The following article describes this process:

• How to test deployed Audium applications in a web browser

When debugging this kind of issue, the voice browser’s logs would generally have relevant information regarding the unreachability of the application or playback issues. Please refer to your voice browser’s logs for more details.