Cisco Cisco Computer Telephony Integration Option 8.5 Reference Guide

The following instructions describe how to increase Driver log file sizes and save them for a 
configured amount of time, so they will not be overwritten:

Change the following registry values to the HKEY_LOCAL_MACHINE\SOFTWARE\Cisco 
Systems, Inc.\CTIOS Tracing registry key for additional control of client tracing.

DWORD "MaxFileSizeKb"

Maximum size of a single trace file (default is 
2048)

DWORD "MaxFiles"

Maximum number of trace files before the Trace 
Server starts deleting the oldest file (default is 5)

DWORD 
"MaxDaysBeforeExpire"

Maximum number of days before log file is 
rolled over to a new file regardless of size 
(default is 7)

DWORD 
"FlushIntervalSeconds"

Number of seconds before the Trace Server 
transfers output to the log file (default is 30)

The Service:AutoLogout parameter, if enabled, sends a logout request automatically every time an agent 
logs out of Siebel, if the AgentState is not already set to Logout. The logout request fails if the current 
agent state does not allow transition to the Logout state. In this case, a ControlFailureConf error displays 
in the Driver log as a response to the AutoLogout request.

Use the following guidelines to troubleshoot the ControlFailureConf error when using the 
Service:AutoLogout parameter:

On Aspect, IPCC, and Spectrum, the agent should be in the NotReady state in order to log out; 
otherwise, when the Siebel application closes a ControlFailureConf error occurs.

On most switches, the agent can not log out while in the Talking state.

AutoLogout might fail if the AutoLogoutReasonCode is not provided or was entered incorrectly.

The above cases where ControlFailureConf occurs should be considered normal behavior.

Each Siebel CTI user has a separate Siebel SCOMM log with the naming convention SCOMM_<Siebel 
User Name>.log. These logs are very useful for troubleshooting purposes.

The location of these logs depends on which type of Siebel client you are using. (Refer to the Siebel 
documentation set for more details.)

Siebel Dedicated client: SCOMM logs are located in the 

 

<SiebelRoot>/web client/LOG directory.

Siebel Thin client: SCOMM client logs are located in the <SiebelRoot>/Siebsrvr/LOG directory.