Table Of Contents
Using Traces
Understanding Traces
Configuring Trace Log Files
Enabling Micro Traces
Available Micro Traces
Enabling Macro Traces
Available Macro Traces
Where to Find More Information
Using Traces
This chapter provides information on using traces in Cisco Unity Connection Serviceability and contains the following topics:
•
Understanding Traces
•Configuring Trace Log Files
•Enabling Micro Traces
•Available Micro Traces
•Enabling Macro Traces
•Available Macro Traces
•Where to Find More Information
Understanding Traces
Cisco Unity Connection Serviceability traces help you troubleshoot Cisco Unity Connection problems in the following ways:
•You can specify the log file parameters for each Cisco Unity Connection component, including the maximum number of log files and the maximum file size that can be created when you run traces for a component.
•You can enable micro traces and the level of micro-trace information that you want.
•You can enable macro traces (preselected groups of micro traces) and the level of macro-trace information that you want.
After you have configured the log files and enabled the traces, you can collect trace log files by using the trace and log central option in the Real-Time Monitoring Tool (RTMT). For more information on collecting traces, see the "Trace Collection and Log Central in RTMT" chapter of the Real-Time Monitoring Tool Administration Guide for Cisco Unity Connection.
Note Enabling macro or micro traces decreases system performance. Enable traces only for troubleshooting purposes.
Configuring Trace Log Files
Do the following procedure to configure trace log files for Cisco Unity Connection services.
Note Before trace information can be written to the log files, you must enable micro traces or macro traces that will provide the troubleshooting information in the areas that you select.
To Configure Trace Log Files
Step 1 In Cisco Unity Connection Serviceability, click Trace > Configuration.
The Trace Configuration page appears.
Step 2 In the Server drop-down box, click the Cisco Unity Connection server, and click Go.
Step 3 From the Component drop-down box, choose the component for which you want to configure trace log files, and click Go.
Note The drop-down box displays all components (active and inactive).
Step 4 In the Maximum No. of Files field, enter the maximum number of trace log files that will be created for this component.
Step 5 In the Maximum File Size field, enter the size limit (in megabytes) for the trace log files that will be created for this component.
Step 6 If you want to return to the default settlings, click Set Default. Otherwise, continue to the next step.
Step 7 Click Save.
Step 8 If you want the new trace log files to replace the old trace log files for this component, click Restart Log Files.
Tip After you have configured the log files and enabled the traces, you can collect trace log files by using the trace and log central option in the Real-Time Monitoring Tool (RTMT). For more information on collecting traces, see the "Trace Collection and Log Central in RTMT" chapter of the Real-Time Monitoring Tool Administration Guide for Cisco Unity Connection.
Additional Information
See the "Where to Find More Information" section.
Enabling Micro Traces
Enable the micro traces when you are troubleshooting problems with specific Cisco Unity Connection components. For example, if the Alert Central tool in Real-Time Monitoring Tool (RTMT) has notification errors, enable the Notifier trace. However, keep in mind that running traces can affect system performance and hard drive space.
Note Enabling micro traces decreases system performance. Enable traces only for troubleshooting purposes.
To Enable Micro Traces
Step 1 In Cisco Unity Connection Serviceability, choose Trace > Micro Traces.
The Micro Traces page appears.
Step 2 In the Server drop-down box, click the Cisco Unity Connection server, and click Go.
Step 3 From the Micro Trace drop-down box, click the micro trace that you want to enable, and click Go.
Step 4 Under Micro-Trace Levels, check the check boxes for the micro-trace levels that you want to enable.
Step 5 Click Save.
Tip You may need to enable traces in Cisco Unity Connection Serviceability and Cisco Unified Serviceability to troubleshoot Cisco Unity Connection issues. To troubleshoot Cisco Unity Connection components, enable traces in Cisco Unity Connection Serviceability. Similarly, to troubleshoot services that are supported in Cisco Unified Serviceability, enable traces in Cisco Unified Serviceability. For information on how to enable traces in Cisco Unified Serviceability, refer to the Cisco Unified Serviceability Administration Guide for Cisco Unity Connection.
Additional Information
See the "Where to Find More Information" section.
Available Micro Traces
Table 3-1 lists the micro traces that are available and describes what each micro trace analyzes.
Table 3-1 Micro Traces
Micro Trace Name
|
What the Trace Analyzes
|
Arbiter
|
Conversations, ports, and call routing rules that are used for calls
|
AudioStore
|
The audio recording service used by web-based applications that use Media Master to playback or record audio streams
|
AxlAccess
|
Interaction with the AXL server to get and set phone-related properties
|
BulkAdministrationTool
|
Bulk Administration Tool that is used for creating, updating, and deleting multiple users or system contacts
|
CCL
|
The retrieval of meeting information from Cisco Unified MeetingPlace Express
|
CDE
|
Conversation engine and conversation events
|
CDL
|
Information retrieval from the database
|
CML
|
The retrieval of messages from the Cisco Unity Connection message store; the retrieval of messages from an Exchange server (by using IMAP) for using Text-to-Speech feature to read e-mail messages
|
CiscoPCA
|
The Cisco Personal Communications Assistant (Cisco PCA)
|
Common
|
Low-level activities for components that are shared by Cisco Unity Connection services
|
ConfigData
|
Detection that configuration data has been updated in the database
|
ConvRoutingRules
|
The conversation to which the Arbiter routes calls
|
ConvSub
|
User activities and usage
|
CsLicense
|
Functions related to license processing
|
CsMalUmss
|
Access to the message store by the CML, Notifier, and IMAP server
|
CuCcmSynchronizationTasks
|
Synchronization of the user data from Cisco Unified CM
|
CuCsMgr
|
Main Cisco Unity Connection process; starting and stopping Connection
|
CuEncrypt
|
Encryption (except for messaging) and the encryption audit logs
|
CuGal
|
The retrieval of calendar and contact information from Exchange
|
CuImapSvr
|
Access to voice messages by IMAP clients
|
CuService
|
The activities of Cisco Unity Connection Serviceability
|
Cuca
|
The activities of Cisco Unity Connection Administration
|
DataSysAgentTasks
|
SysAgent tasks
|
DbEvent
|
Component notification of database changes
|
FailureConv
|
Activation of the Failure Conversation when a system error occurs
|
LicenseClient
|
Functions related to license management
|
Logger
|
Writing traces logs and events
|
MTA
|
Delivery of voice messages to the message store
|
MediaMasterControl
|
The Media Master control on the client workstation
|
MediaMasterUMS
|
The UMS service, which handles streams audio recordings between the Media Master and the AudioStore
|
MediaMasterWeb
|
The web page rendering module that is used in web-based applications that have the Media Master control
|
MiuAdm
|
Functions in Cisco Unity Connection Administration relating to testing voice messaging ports and generating certificates
|
MiuCall
|
The process between the Miu and conversations
|
MiuDatatbase
|
Media activities relating to accessing the database
|
MiuGeneral
|
Tracking calls through the telephone user interface (TUI); call control functions; turning message waiting indicators (MWIs) on and off; notification and outdial functions; basic media or WAV file usage
|
MiuIO
|
Media or WAV file usage with TAPI (circuit-switched or Cisco Unified CallManager) integrations
|
MiuMethods
|
Handing of incoming calls; call control; turning messaging waiting indicators (MWIs) on and off; notification and outdial functions; media or WAV file usage
|
MiuSIP
|
SIP call control
|
MiuSIPStack
|
Low-level SIP interactions for call control
|
MiuSkinny
|
SCCP call control
|
MiuTranscode
|
Low-level media functions relating to transcoding
|
Mixer
|
Low-level activities relating to media and the Text-to-Speech feature
|
Monitor
|
Monitoring the status of voice messaging ports and call processing during a call; the server-side functions for displaying port status in Real-Time Monitoring Tool
|
Notifier
|
Notification of messages and selected events; turning message waiting indicators (MWIs) on and off
|
PCAMeetingPlace
|
Activities of the Cisco Personal Communications Assistant relating to the Cisco Unified MeetingPlace Express integration
|
PCAUnifiedCM
|
Activities of the Cisco Personal Communications Assistant relating to the Cisco Unified Communications Manager integration
|
PerfMonitor
|
Activities of performance monitor system objects that Cisco Unity Connection uses
|
PhoneManager
|
The management of IP phone applications
|
PhraseServer
|
The prompts that play and the user DTMF input; the logs are written to a file
|
PhraseServerToMonitor
|
The prompts that play and the user DTMF input; the logs are written to the monitor
|
RSS
|
RSS feeds that are used for checking voice mail from an RSS client
|
ReportDataHarvester
|
Conversion of the content in the data log files to entries in the reports database
|
ResourceLoader
|
Using the selected language in the GUI; filling strings with product or message information
|
ResourceManager
|
Monitoring and providing available resources to the Arbiter as needed
|
RoutingRules
|
Call routing decisions
|
RulesEngine
|
Evaluation of Cisco Unity Personal Call Transfer Rules for a subscriber during a call
|
SMTP
|
SMTP functions
|
Scheduler
|
Currently active Cisco Unity Connection schedule (whether during normal business hours or during nonbusiness hours) or holiday
|
SslInit
|
Initialization procedures for components that use OpenSSL
|
SysAgent
|
System Agent component, which schedules system tasks that the administrator enters (such as resynchronizing MWIs)
|
TRaP
|
Telephone Record and Playback (TRAP), which lets clients use the phone as a recording and playback device
|
TextToSpeech
|
The activities of the Text to Speech feature
|
ThreadPool
|
The use of threads by the processor
|
TimerHelper
|
The timer used by the Conversation Manager component
|
TranscodeWeb
|
The web server audio format transcoding utilities that transcode the incoming audio streams into the audio format that Cisco Unity Connection uses
|
UmssSysAgentTasks
|
Messaging tasks for the System Agent component
|
UnityAssistant
|
The activities of the Cisco Unity Assistant in Cisco Personal Communications Assistant
|
UnityInbox
|
The activities of the Cisco Unity Inbox in Cisco Personal Communications Assistant
|
UnityPCTR
|
The activities of the Cisco Unity Personal Call Transfer Rules in Cisco Personal Communications Assistant
|
VUI
|
The voice user interface
|
VirtualQueue
|
Call queuing
|
Additional Information
See the "Where to Find More Information" section.
Enabling Macro Traces
Enable the macro traces when you are troubleshooting problems with specific Cisco Unity Connection components. For example, if there are MWI problems, enable the Traces for MWI Problems macro trace. However, keep in mind that running traces can affect system performance and hard drive space.
Note Enabling macro traces decreases system performance. Enable traces only for troubleshooting purposes.
To Enable Macro Traces
Step 1 In Cisco Unity Connection Serviceability, click Trace > Macro Traces.
The Macro Traces page appears.
Step 2 In the Server drop-down box, click the Cisco Unity Connection server, and click Go.
Step 3 Check the check box of the macro traces that you want to enable.
Step 4 Expand the macro trace, and check the check box for the levels that you want to enable.
Step 5 Click Save.
Tip You may need to enable traces ins Cisco Unity Connection Serviceability and Cisco Unified Serviceability to troubleshoot Cisco Unity Connection issues. To troubleshoot Cisco Unity Connection components, enable traces in Cisco Unity Connection Serviceability. Similarly, to troubleshoot services that are supported in Cisco Unified Serviceability, enable traces in Cisco Unified Serviceability. For information on how to enable traces in Cisco Unified Serviceability, refer to the Cisco Unified Serviceability Administration Guide for Cisco Unity Connection.
Additional Information
See the "Where to Find More Information" section.
Available Macro Traces
Table 3-2 lists the macro traces that are available and describes what each macro trace analyzes.
Table 3-2 Macro Traces
Macro Trace Name
|
What the Trace Analyzes
|
Call Flow Diagnostics
|
The flow of a call through Cisco Unity Connection
|
Message Objectid Tracking Traces
|
Message handing; the objects that handle messages from delivery to deletion
|
Call Control (Miu) Traces
|
Call control functions
|
Traces for MWI Problems
|
Turning message waiting indicators (MWIs) on and off
|
Traces for Other Notification Problems
|
Notification and outdial functions
|
Unity Startup
|
Cisco Unity Connection startup functions
|
Voice User Interface/Speech Recognition Traces
|
Voice User Interface (VUI)
|
Media (Wave) Traces
|
Media and WAV file usage
|
Text to Speech (TTS) Traces
|
The Text to Speech (TTS) feature; also can log traces on other Cisco Unity Connection components that interact with TTS
|
Connection Serviceability Web Service
|
The activity of Cisco Unified Serviceability
|
Additional Information
See the "Where to Find More Information" section.
Where to Find More Information
•Understanding Traces
•Configuring Trace Log Files
•Enabling Micro Traces
•Available Micro Traces
•Enabling Macro Traces
•Available Macro Traces
•Real-Time Monitoring Tool Administration Guide for Cisco Unity Connection
•Cisco Unified Serviceability Administration Guide for Cisco Unity Connection
Feedback
