| When I use the XML over HTTP API, timeout errors are logged |
| Categories: Audium Call Services 3.4.x and 3.5, Audium OpenSDK |
| Article ID: | 79 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article explains why there may be timeout errors logged while using the XML over HTTP API, and how to address them.
SYMPTOMS
There are timeout errors present in the application's log files, and it is apparent from the activity log that the timeout occurs while an element using the XML over HTTP API is being accessed.
SOLUTION
There is a built-in timeout threshold of 5 seconds while accessing custom code via the XML over HTTP API. This means that if, after Audium Call Services requests the XML from the configured URI, it takes more than 5 seconds to receive a response, an error will occur.
If you are using a script to dynamically generate XML that conforms to the XML over HTTP API, this script may be taking longer than 5 seconds to produce the XML.
How the solution for this problem is implemented is highly dependent on the requirements of your application. However, on the high level, you could have an Action element that kicks off the process on your backend system. The XML API result would return success or fail depending on whether the process started without error. Then, the application could have a callflow "loop" that checks that the process (using the XML API with a Decision element) is complete and if so, return the data as well. In the callflow "loop", if the process is not complete, the application could play some audio to indicate to the caller to wait. You would have to make sure that your backend system is properly designed to support this behavior (i.e. the backend logic should run as a separate process and have the ability to check that the process is complete using the XML API).
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|