Document ID: 51779
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Problem
Solution
Related Information
Introduction
This document describes why the AgentCfg utility fails to generate an output log file, AgentCfg.log and provides a solution in a Cisco Intelligent Contact Management (ICM) environment.
Prerequisites
Requirements
Readers of this document should have knowledge of these topics:
-
Cisco ICM
-
AgentCfg Utility
Components Used
The information in this document is based on these software and hardware versions:
-
Cisco ICM
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Problem
The AgentCfg utility loads a tab-delimited agent configuration data file into Agent and/or Skill_Group_Member configuration table. When running the AgentCfg utility, it fails to generate the associated log file, AgentCfg.log.
Solution
This is a configuration issue. The agent configuration process generates an output log file called AgentCfg.log, if the registry key value for ShowDebug is set to Yes and the registry key value for DebugLevel is set to 0xffff, respectively:
-
For ICM versions prior to version 5.0:
HKEY_LOCAL_MACHINE\Software\GeoTel\ICR\<cust_inst>\AW\ICR Configure\ Debug\ShowDebug
-
For ICM version 5.0 and later:
HKEY_LOCAL_MACHINE\Software\Cisco Systems, Inc.\ICM\<cust_inst>\AW\ ICM Configure\Debug\ShowDebug
Note: The above registry keys are displayed over two lines due to space limitations.
After the ShowDebug value is set to Yes and the DebugLevel is set to 0xffff, the AgentCfg utility begins to generate a log file.
Related Information
| Updated: Jul 13, 2005 | Document ID: 51779 |