on 01-24-2014 02:37 PM
In the VMXL Activity Log, I'm getting the error
"Warning, A session has timed out after 1 minutes. This is most likely caused by a start of call class or action element at the top of the callflow not completing before the voice browser's fetch timeout occurred. To resolve it ensure this class executes in a timely manner or run it in the background. Session timeouts may also occur under high load or if there are issues with a load balancer or voice browser."
What is happening to the call is I'm hearing silence for about 30-40 seconds and then the call fails and is routed to my default error path, which is just an external recording/VM.
The funny thing to me is the application "ChkHours" we are using is used across several Line of Business with over 70+ locations, i.e. ingress points. So why are we not having this issue at any of the other locations? Also, I don't know what is affected if I were to increase the timeout. My guess is the call would just hang and I'd get the same result but instead of "1 minutes" it would say "30 minutes"
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: