How Can You Use the ChannelCleanupTimer Parameter To Manage CTI Dangling Sessions? (Doc ID 477541.1)

Goal

The end user occasionally will encounter browser frozen and he most likely will use Windows Task Manager to terminate the freezing browser. This results to an orphan Siebel Object Manager (SOM) session. Typically this orphan SOM session will be collected back after Siebel Session Timeout is reached (e.g. 15 minutes). However if there is a CTI push message happening to this orphan session, it will delay the session timeout or in case you have implemented the Siebel Push Keep Alive Driver it will avoid the SOM session to timeout. Below is the user scenario describes this behavior.

Time 0: user A login Siebel (session A). Assume session timeout is 15 minutes
Time 1: user A kills the browser.
Session A is supposed to be timed out at (time1 + 15 minutes)
; ; ; ;
(10 minutes after time 1)
Time 2 (time 1 + 10 minutes): a CTI push message is delivered from CommSessionMgr to Object Manager. This could be because of an inbound call event or any status text that communications drivers would like to deliver to the browser. This push messages will exercise the OM session A. The new session timeout is now at (time 2 + 15 minutes = time 1 + 10 minutes + 15 minutes)

As you can see from this scenario, CTI push message is delaying the session timeout. To resolve this and to manage the orphan CTI sessions effectively, you need to use "ChannelCleanupTimer" parameter at Communications Configuration (Site Map>Administration - Communications>All Configurations>Parameter tab.

More information about this parameter can be found in Bookshelf>Siebel Communications Server Administration Guide>Configuring Session Communications> Creating or Modifying a Communications Configuration>ChannelCleanupTimer

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.