The value of 30 mins seems more appropriate to a Web browser/application type of service.

Given the session timeout setting is meant as a safety net, if we determined that, for a particular application, the longest duration for which a response is expected from a caller is in the order of 2 mins, would a value of 5 mins be more reasonable?

Thanks in advance.

I would be very careful making the session timeout that low. While you most likely will not have a problem, there is always a chance that a slow caller, long audio files, error conditions, etc. could cause a situation to exist where you got a false positive here. Remember, its not a pause, its how long they are visiting a VoiceXML page, which is not immediately apparent what the size of it is in an Audium system. If you have a recording with confirm, and the person re-records their message, you could be in a single page for a while (yes, I know 5 minutes is a long time, but its is still a bit risky).

Also, remember, this timeout is used ONLY when there is a problem that should not occur; the browser does not detect a hangup, a load balancer is not configured correctly, a Java class runs too long, the browser becomes innaccessible from a network standpoint, etc. all of which should not occur on a regular basis. So playing with this value is not going to get you better performance or something, its only for rare error conditions.

Another point to consider is that some application servers may not be completely accurate in their timing for these timeouts, they could be slightly longer or shorter.

So if you absolutely needed to reduce this number, you could do something like 10 minutes.

Elam