My Oracle Support Banner

How Does CTI Push Keep Alive Driver Work ? (Doc ID 1918827.1)

Last updated on JANUARY 23, 2018

Applies to:

Siebel CTI - Version 7.0.4 [14068] and later
Information in this document applies to any platform.

Goal

The Push Keep Alive communications driver provides a heartbeat message that is useful in maintaining connections for your communications sessions in some environments. You use this driver with Communications Session Manager, such as when you are using Siebel CTI.

The Push Keep Alive driver helps to solve problems that might be experienced in some environments, where push communications sessions between the Application Object Manager and a user's Web browser are sometimes dropped. A connection might be dropped if messages have not been pushed to an agent for a particular length of time.

The Push Keep Alive driver sends a heartbeat message to the Application Object Manager and to each agent user's browser, at a regular interval. This heartbeat message allows the push connection applicable to each agent's communications toolbar not to be dropped in such cases. The heartbeat interval is specified using a driver parameter.

For a typical scenario the PushKeepAliveTimer parameter is usually set around 3 minutes and mandatory ChannelCleanupTimer when using Push Keep Alive Driver is set around 10 minutes. The main goal for PushKeepAliveTimer is to be much lower than any network device idle timeout such as Load Balancer/Proxies/Firewalls.

More details about Push Keep Alive Driver can be found in Siebel CTI Administration Guide > Configuring Advanced Communications Features > Using the Push Keep Alive Driver for Session Connections

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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