Cisco Cisco Customer Response Solution Downloads Troubleshooting Guide

You can create a trace file for any of the following Cisco Unified CCX components:

Cisco Unified CCX Engine

Cisco Unified CCX Administration

Cisco Unified CCX Editor

Cisco Unified CCX Node Manager

Cisco Unified CCX SQL Server

The component trace file contains information about each of the component's subfacilities. To set up this 
trace file, you perform the following general procedures:

For information about reading the trace file, see the 

.

By default, the Cisco Unified CCX system sends information about subfacilities to a trace file, for 
example, CiscoMIVRnn.log. The system replaces nn with a number, starting with 01. You can configure 
the size of the trace file. When the size you configured is reached, or if a Cisco Unified CCX component 
is restarted, the system creates a new trace file, incrementing nn by one. After creating the tenth trace 
file (by default), the trace file begins overwriting existing files, starting with the first trace file created. 

Note that the examples shown here are for the Cisco Unified CCX Engine component. Follow the same 
procedures for the other components, substituting the component's name. 

To change any of these default trace file parameters, follow these steps:

From the Cisco Unified CCX Administration menu, choose System > Tracing. 

The Trace Configuration page appears.

Choose and expand a component from the navigation bar. 

Change the following information under Trace File as needed:

Trace File Output—Check this check box to send information to a trace file. Uncheck this box if 
you do not want to send information to a trace file. By default, this check box is checked.

File Name—Enter the base name and the extension of the trace file. A trace file name is made up of 
the base facility name, the file number, and the extension (for example, CiscoMIVR01.log). The 
default file name is Cisco<facility_code>.log 

where the <facility_code> could be MIVR, MCVD, MADM, MEDT, or MARC.