Hi there, we have recently applied PushKeepAliveTimer parameter so that the CTI send a heartbeat m

Hi there,

we have recently applied PushKeepAliveTimer parameter so that the CTI send a heartbeat msg every 60 seconds, our session timeout is set to 1200 seconds but we have just discovered a problem with this setup. below is the problematic scenario

User logs into siebel & receives calls without any problem, at the end of the day most users dont log off siebel but rather just log off their machines, now for users without CTI this is nota problem as the session will timeout after the 1200 seconds session timeout time has passed.

However for users with CTI functionality this will not be the case, since the session is still alive even after machine logout & since the PushKeepAliveTimer still send a heartbeat every 60 seconds what happens is the session will never time out & whats worse is that the CTI back end will still continue to send calls to this user although he is long logged of the machine.