Cisco Cisco Computer Telephony Integration Option 8.5 Troubleshooting Guide

The default trace mask is:

0x7 for Release 6.0 and earlier

0x40000307 in release 7.x.x

Setting the trace mask to 0x40000307 is OK when running one, two or three agent desktops on the 
systems, but it impacts the system if a load test is running and CILTest is used to simulate CTI OS agents. 
When running load testing using CILTest, setting a low trace mask value (0x3 for example) is more 
appropriate.

Set the trace mask higher than 0x40000307 only when debugging a problem. When the requied logs are 
collected, set the trace mask back to its default value. 

For troubleshooting purposes, set the CTI OS Client trace mask to 0xFFF.

For troubleshooting purposes, and to get all evets as described before for the client plus Silent Monitor 
Sniffer, Decoder events/requests, and communication of forwarded VoIP (send/receive of encapsulated 
VoIP in UPD stream); set the trace mask to 0x20003E0F.

TRACE_MASK_ALWAYS

0x0

Used across all CTI OS components.

Only the necessary messages need to use this trace 
mask. Examples: initialization phases, important 
error messages, etc...

The message is always printed, regardless of the 
trace mask setting.

TRACE_MASK_CRITICAL

0x01

Used across all CTI OS components.

Only the necessary messages need to use this trace 
mask. Examples: critical error messages, etc...
The message is printed only if the trace mask bit is set.

TRACE_MASK_WARNING

0x02

Used across all CTI OS components.

This trace mask bit is used for warning messages.
The message is printed only if the trace mask bit is set.

TRACE_MASK_EVT_REQ_HIGH

0x04

Used across all CTI OS components. 

This trace mask bit is used to display high important 
events, confs, and requests names without their 
parameters.
The message is printed only if the trace mask bit is set.

TRACE_MASK_EVT_REQ_HIGH
_PARM

0x08

The same as TRACE_MASK_EVT_REQ_HIGH, but 
the messages include events, confs, and requests 
parameters.