Hi,
 
I just wanted to know how do we arrive at the session
timeout value of a CallStudio application?
 
In our application we are using the modular approach, where
in the control shall be passed by subdialog invoke to other module. And I
wanted to know if the Module A passes the control and caller spends more time
than the configured session timeout (of module A) in module B - will this have any
impact on releasing the VXML Port or what will be the impact?
 
Is this session timeout value equivalent of the Tomcat Session
value?
 
-Ilias

Few things on timeout based on what I have seen in prod systems. A session timeout of 3 mins is good. A session timeout of 1 min may be too short and could cause the application to abort unecessarily in case of any delay. You could always set it to higher value like 10-30 mins. However what happens is that if you have any errors, say some random bad fetch errors that app could hang for the session timeout value. So if you set it to 5 mins, aftter the bad fetch I have seen the application sometimes not exiting for the session timeout value. It could potentially hold the port for that much time.
This is based on some random bad fetch errors I have seen here and there.
Hemal

________________________________
From: Cisco Developer Community Forums [cdicuser@developer.cisco.com]
Sent: Friday, October 28, 2011 5:47 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Bill Westby in Customer Voice Portal (CVP) - CVP - All Versions: RE: Is there any std way to arrive at a session timeout value of call studi

Bill Westby has created a new message in the forum "CVP - All Versions":

--------------------------------------------------------------
Hi,

I just wanted to know how do we arrive at the session
timeout value of a CallStudio application?

In our application we are using the modular approach, where
in the control shall be passed by subdialog invoke to other module. And I
wanted to know if the Module A passes the control and caller spends more time
than the configured session timeout (of module A) in module B - will this have any
impact on releasing the VXML Port or what will be the impact?

Is this session timeout value equivalent of the Tomcat Session
value?

-Ilias


Ilias

I do not know the answer but what you could could easily test is edit the properties of application "A", General Settings, and change the session to 1 minute. Then change the setting in application "B" to 2 minutes. Then call in and spend more than one minute in Application "B" and see if it times out at 1 minute which then you can assume the root application controls the overall session timeout. Unless Application "A" gets suspended I would "think" it controls the overall session timeout.

Bill.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4693845>

or simply reply to this email.

Thanks all for the suggestions.

Couldn't respond to this thread as forum's webpage gave "you dont have sufficient privileges" (off the topic)

I did experimentetd the various session timeout values as Hemal suggested with about 2-3mins. Most of the time this configuration works fine, however there are cases i have noticed in our lab that some calls gets suddenly dropped at parent application as session timeout(as per config. time), without giving any trace about the invoked application's state. No activity logs to understand this better. I am currently worried of giving a greater value as it can cause potential port blockage in production environment in case of some delay/error..

Janine,

let me incorporate your suggestion in my application and post the result

We are using CVP 8.5.

In all of our previous applications, we held the call control is purely with ICM. But in this case since call control is partially held by CVP - its causing the worry