Turning on Unified CCX Telephony Client traces

From DocWiki

Revision as of 10:11, 12 January 2010 by Sakkumar (Talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Turning on Unified CCX Telephony Client traces

Problem Summary For any call processing related issues the JTAPI client traces are required. This tip explains how to turn on those traces.
Error Message NA
Possible Cause NA
Recommended Action
  1. On the Unified CCX node, login to "Cisco Unified CCX Serviceability"
  2. Go to Trace --> Configuration
  3. Select "Cisco Unified CM Telephony client" and click Go.
  4. Check/Enable WARNING, INFORMATIONAL, DEBUG, JTAPI_DEBUGGING, JTAPIIMPL_DEBUGGING, CTI_DEBUGGING, CTIIMPL_DEBUGGING, PROTOCOL_DEBUGGING and MISC_DEBUGGING
  5. Increase the file size to 5MB and number of files to 100.
  6. Click Save.
  7. The trace changes will be saved and a message will ask you to restart Cisco Unified CCX Engine for the changes to take effect.


Snapshot of JTAPI Client traces being turned on


After the traces are turned on and the scenario is simulated, use the Real Time Monitoring Tool (RTMT) to collect the logs using the "Collect Files" option. The modules for which the traces are to be collected are "Unified CCX Engine" and "Unified CM Telephony client"/"Jtapi Client" from the UCCX Services screen.

Release Release 8.0(1)
Associated CDETS # NA

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Turning_on_Unified_CCX_Telephony_Client_traces"
Personal tools