Created by: deniz caglar on 07-03-2013 08:22:58 AM Hi all, We start to get lots of “session timeout errors” in our VXML servers(8.5) nowadays. What can be the reasons for this error, can you advise anything to check? We added two more new applications to our VWML servers, Our core application A_Application calls Subdialog_B_Application with SubDialog element, and Subdialog_B_Application call the Subdialog_C_Application which is an ASR application entegrated with Nuance 8.5. When I look to error logs, there are 71 errors in the A_Application’s error log like: 10.231.50.145.1362659919697.604358.A_Application,03/07/2013 15:08:55.685,A VoiceXML Session timeout occurred at element Subdialog_B_Application: A session has timed out after 30 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. 28 errors in the Subdialog_B_Application’s error log like: 10.231.50.145.1362662739157.619753.Subdialog_B_Application,03/07/2013 15:55:55.786,A VoiceXML Session timeout occurred at element Subdialog_C_Application: A session has timed out after 30 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. Thanks, Deniz
Subject: RE: New Message from deniz caglar in Customer Voice Portal (CVP) - General Replied by: Hemal Mehta on 07-03-2013 08:28:58 AM There are can be so many reasons for this. It could be a timeout issue, issue with backend fetch, even timeout settings on gateway, cpu spike on gateway etc. You would need to provide more details on your app. However the first thing I would recommend is to reduce the 30 minutes session timeout value to 3 mins or so in your project properties. You do not want set it this high. It may potentially block your port for that long even after the call has ended. Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 07, 2013 8:23 AM To: cdicuser@developer.cisco.com Subject: New Message from deniz caglar in Customer Voice Portal (CVP) - General Discussion - All Versions: Session timeout
deniz caglar has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Hi all, We start to get lots of “session timeout errors” in our VXML servers(8.5) nowadays. What can be the reasons for this error, can you advise anything to check? We added two more new applications to our VWML servers, Our core application A_Application calls Subdialog_B_Application with SubDialog element, and Subdialog_B_Application call the Subdialog_C_Application which is an ASR application entegrated with Nuance 8.5. When I look to error logs, there are 71 errors in the A_Application’s error log like: 10.231.50.145.1362659919697.604358.A_Application,03/07/2013 15:08:55.685,A VoiceXML Session timeout occurred at element Subdialog_B_Application: A session has timed out after 30 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. 28 errors in the Subdialog_B_Application’s error log like: 10.231.50.145.1362662739157.619753.Subdialog_B_Application,03/07/2013 15:55:55.786,A VoiceXML Session timeout occurred at element Subdialog_C_Application: A session has timed out after 30 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. Thanks, Deniz -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/12747481 or simply reply to this email.
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:
