Troubleshooting Guide for Cisco Unity Release 5.x (With IBM Lotus Domino)
Diagnostic Trace Utilities and Logs
Downloads: This chapterpdf (PDF - 204.0KB) The complete bookPDF (PDF - 4.73MB) | Feedback

Diagnostic Trace Utilities and Logs

Table Of Contents

Diagnostic Trace Utilities and Logs

Using Diagnostic Utilities for Cisco Unity

Event Log

Macro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)

Available Macro Traces

Enabling Macro Traces

Micro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)

Available Micro Traces

Enabling Micro Traces

Viewing Individual Micro Trace Logs

How to Interpret Micro Trace Information in the Cisco Unity Diagnostic Tool (UDT)

Gathering Micro Trace Logs into Files

Dialogic TSP Diagnostic Traces

Dr. Watson Logs

Trace Settings for Troubleshooting Cisco Unity Components

Domino Directory Monitor Diagnostic Traces

AMIS Diagnostic Traces

Basic Incoming and Outgoing AMIS Message Trace

General Incoming AMIS Message Traces

Extensive Incoming AMIS Message Traces

General Outgoing AMIS Message Traces

Extensive Outgoing AMIS Message Traces


Diagnostic Trace Utilities and Logs


In this chapter, you will find information about the diagnostic utilities that enable you to troubleshoot problems and to maintain Cisco Unity. The information in this chapter will help you select, use, and set the applicable diagnostic utilities.

This chapter contains the following sections:

Using Diagnostic Utilities for Cisco Unity

Trace Settings for Troubleshooting Cisco Unity Components

Using Diagnostic Utilities for Cisco Unity

The diagnostic utilities for Cisco Unity are described in Table 2-1.

Table 2-1 Diagnostic Utilities for Cisco Unity 

Utility
Uses

Event log

The Event log should be the first resource you search for information when troubleshooting a problem. The Event log is used by Windows applications to report information events, warnings, and errors. Reviewing the Event log for Cisco Unity events provides a good overview of how the system is functioning.

For details, see the "Event Log" section.

Macro trace logs in the UDT

In the Cisco Unity Diagnostic tool (UDT), you can enable a preselected group of individual micro trace levels to obtain diagnostic trace output on several Cisco Unity components at once.

For details, see the "Macro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)" section.

Micro trace logs in the UDT

The Cisco Unity Diagnostic tool (UDT) can enable most Cisco Unity components to write diagnostic traces to a log. The diagnostic trace output is essential to troubleshooting problems that involve individual components.

For details, see the "Micro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)" section.

Dialogic TSP trace logs

(circuit-switched phone system integrations via voice cards only)

This utility is used to troubleshoot problems with the Dialogic TSP that is installed for use with voice cards. For example, when calls between Cisco Unity and the voice cards show unusual behavior, this utility provides information on how the Dialogic TSP is handling calls.

For details, see the "Dialogic TSP Diagnostic Traces" section.

Dr. Watson logs

This utility is invoked by Windows 2000 when a serious problem occurs that is not handled by Cisco Unity. When invoked, the Dr. Watson utility displays a dialog box that contains an error message (for example, "Dr. Watson encountering an error in the AvCsMgr.exe process"). Dr. Watson errors may occur in other processes as well.

For details, see the "Dr. Watson Logs" section.


Event Log

The Event log is the first resource you should search for information when troubleshooting a problem. Cisco Unity components report information events, warnings, and errors in the Event log. Reviewing the Event log for Cisco Unity events provides a good overview of how the system is functioning.


Note The raw data within the files in the Event log is stamped with time stamps recorded in GMT (Greenwich mean time) rather than in the local time of the Cisco Unity server. The time stamps for the Event log files themselves, however, are in the local time of the Cisco Unity server. Using GMT for the time stamps of the raw data provides for an accurate comparison of events when Cisco Unity servers are not all in the same time zone. The Cisco Unity reports convert the GMT time stamps to local time.


To Obtain an Event Log Trace


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Event Viewer.

Step 2 In the Tree pane, click Application Log.

Step 3 Search for Cisco Unity events.


Note For further instructions on Event Viewer functions, see the Event Viewer Help.



Macro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)

The Cisco Unity Diagnostic tool (UDT) lets you create and view diagnostic trace logs for troubleshooting problems. Diagnostic trace logs of a problem occurring can be critical to determining the cause of the problem.

Macro traces in the UDT let you enable preselected groups of micro traces. For details on viewing, interpreting and gathering the micro traces that the macro traces use, see the "Micro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)" section.

Diagnostic traces that are set before a Cisco Unity software upgrade are not preserved and must be reset after the upgrade.

See the following:

Available Macro Traces

Enabling Macro Traces

Available Macro Traces

Table 2-2 lists the macro traces that are available and what each macro trace analyzes.

Table 2-2 Macro Traces 

Macro Trace Name
What the Trace Analyzes

AMIS Message Traces

Incoming and Outgoing AMIS messages, to confirm that Cisco Unity can send and receive AMIS messages

Call Flow Diagnostics

The flow of a call through Cisco Unity

Conversation State Traces

The conversation that the caller hears

Bridge Directory Synchronization Traces

Cisco Unity Bridge directory synchronization for subscriber information

VPIM Directory Synchronization Traces

VPIM directory synchronization

Directory Monitor Traces

Replication with Cisco Unity and the directory

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

Skinny TSP Traces

The Skinny networking layer; useful only when Cisco Unity is integrated with Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager)

Unity Startup

Cisco Unity startup functions

Media (Wave) Traces 1 - High-Level

Media and WAV file usage

Media (Wave) Traces 2 - Medium-Level

Media and WAV file usage; logs more information than high-level traces

Media (Wave) Traces 3 - Low-Level

Media and WAV file usage; logs detailed information and should be used only when there is significant free hard drive space

Text to Speech (TTS) Traces

The Text to Speech (TTS) feature; also can log traces on other Cisco Unity components that interact with TTS


Enabling Macro Traces

Enable the macro trace diagnostics when you are troubleshooting problems with Cisco Unity features. For example, if there are MWI problems, enable the Traces for MWI Problems macro trace. However, keep in mind that running diagnostics can affect system performance and hard drive space.

To Enable Macro Trace Diagnostics


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Diagnostic Tool. The Cisco Unity Diagnostic Viewer window appears.

Step 2 Click the Configure Macro Traces icon. The Configure Macro Traces wizard appears.

Step 3 On the Welcome page, click Next.

Step 4 On the Configure Macro Traces page, check the check boxes for the applicable traces.

Step 5 Click Next.

Step 6 On the Completing page, click Finish.

Step 7 On the Cisco Unity Diagnostic Viewer screen, click the Start New Log Files icon.

Step 8 Reproduce the problem.


Note After obtaining the diagnostic trace logs that you want, disable the traces that you enabled.



Micro Trace Logs in the Cisco Unity Diagnostic Tool (UDT)

The Cisco Unity Diagnostic tool (UDT) lets you create and view diagnostic trace logs for troubleshooting problems. Diagnostic trace logs of a problem that is occurring can be critical to determining the cause of the problem.

Micro traces in the UDT let you enable specific Cisco Unity components and trace levels, which makes the trace logs as precise as possible. This is particularly critical when the problem occurs seldom, such as only once a day, as it can be difficult to find the actual occurrence of the problem in a diagnostic trace log.


Caution Diagnostic traces that are set before a Cisco Unity software upgrade are not preserved and must be reset after the upgrade.

See the following:

Available Micro Traces

Enabling Micro Traces

Viewing Individual Micro Trace Logs

How to Interpret Micro Trace Information in the Cisco Unity Diagnostic Tool (UDT)

Gathering Micro Trace Logs into Files

Available Micro Traces

Table 2-3 lists the micro traces that are available and describes what each micro trace analyzes.

Table 2-3 Micro Traces 

Micro Trace Name
What the Trace Analyzes

AlCommon

This is a shared diagnostic trace; use it when diagnosing Doh, MAL, DAL, SAL, and AvRdbSvr

Arbiter

Conversations, ports, and call routing rules that are used for calls

AuthenticationMgr

Cisco Unity authentication activities

AuthorizationMgr

Access that is granted or denied

AvCsGateway

Starting and stopping Cisco Unity; access to AvCsMgr; access to Cisco Unity components

AvCsMgr

Main Cisco Unity process; starting and stopping Cisco Unity

AvLic

The use of Cisco Unity license files

AvLogMgr

Writing diagnostic traces and Event log

AvRdbSvr

Access to SQL from within the Doh

AvSaDbConn

Cisco Unity Administrator screens and their connection to Cisco Unity components and other products used by Cisco Unity; for Windows 2000, the events are collected in the diag_inetinfo log; for Windows 2003, the events are collected in the diag_w3wp log

AvXML

AvXML component and the Cisco Personal Communications Assistant (PCA) connection to Cisco Unity

CDE

Conversation engine and conversation events; the logs are written to a file

Conversation

Conversations, phone handlers, call handler, AMIS activity

Conversation Utilities

Live reply, pause, and other support functions

CsBMsgConnector

Incoming system broadcast messages

CSBridgeConnector

Cisco Unity Bridge directory synchronization for subscriber information

DALDb

Access to directory information such as subscribers, distribution lists, interview handlers, and call handlers

DALEx

(Not used)

DeliveryDialout

The function that enters after-dial digits for notification to pagers and for message delivery

DGateway
(For Domino only)

IBM Lotus Domino gateway

Directory Change Queue

Replication between the directory and the Cisco Unity SQL database

Directory Change Writer

Replication between the directory and the Cisco Unity SQL database

DiRTD
(For Domino only)

DiRT utility used for Domino

Doh

Directory access and messaging access

DominoMonitor
(For Domino only)

Monitoring the Domino message store for changed message status

DSDomino
(For Domino only)

Creations, modifications, deletions, and changes in the Domino directories that Cisco Unity monitors; by default, DSDomino monitors the Domino Domain directory (typically called names.nsf), but Cisco Unity can be configured to monitor additional directories

FailoverConfig

Failover configuration wizard

FailureConv

Failsafe mode

FaxSend Conversation

Sending faxes to a fax machine or faxing e-mail messages to a fax machine

MaestroTestComponent

(Not used)

MALLn
(For Domino only)

Message creation and delivery

MiuCall

The process between the Miu and conversations

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

MiuIntegration

Integrations with circuit-switched phone systems; call information in integrations with circuit-switched phone systems; turning message waiting indicators (MWIs) on and off in integrations with circuit-switched phone systems

MiuIO

Media or WAV file usage with TAPI (circuit-switched or Cisco Unified Communications Manager) integrations

MiuMethods

Handling of incoming calls; call control; turning message waiting indicators (MWIs) on and off; notification and outdial functions; media or WAV file usage

MiuSa

The interaction between the Miu and the Cisco Unity Administrator

MiuSCBus

Fax engine and fax tone detection

NodeMgr
(Only when Cisco Unity is configured for failover)

Status monitoring, file replication, and failover between the primary and secondary servers

NotesCommon
(For Domino only)

IBM Lotus Notes API calls that Cisco Unity uses

Notifier

Notification of messages and selected events; turning message waiting indicators on and off

NotifyQ

Notifier queue

PerfMonitor

Performance of system objects that Cisco Unity uses

PhraseServer

The prompts that play and the user DTMF input; the logs are written to a file

PhraseServer to Monitor

The prompts that play and the user DTMF input; the logs are written to the monitor

ReportCrunch

Processing reports database tables and reports localization

ReportExtractor

Copying data from data files to the reports database

ReportPostprocess

Cleanup after reports are generated

ReportPreprocess

Creation of reports database tables required for reports generation

ReportPump

Writing of data to log files

ReportRunrep

Formatting of reports database tables and report generation

Resource Loader

Using the selected language in the GUI; filling strings with product or message information

Resource Manager

Monitoring and providing available resources to the Arbiter as needed

RulerDomain

Routing rules

RulerSvr

Routing rules

Scheduler

Currently active Cisco Unity schedule (whether during normal business hours or during nonbusiness hours) or holiday

SkinnyTSP

(Circuit-switched or Cisco Unified Communications Manager integrations) Media or WAV file usage

(Cisco Unified Communications Manager integrations only) Skinny networking layer

Sql Change Writer

Requests to synchronize the Cisco Unity SQL database with the directory

SystemConfig

Configuration Manager that runs during the installation of Cisco Unity

Tds Proxy

Cisco Unity database connections made via ADO, ODBC, JDBC, and other standard APIs that use the Microsoft TDS (Tabular Data Stream) protocol

Text to Speech

Text to Speech feature

TrapConnector

Telephone Record and Playback (TRAP), which lets clients use the phone as a recording and playback device

TUI Security

Password-protected logon conversation

UMR

Unity Messaging Repository (UMR), which holds messages when the message store is not available

UnityDiagnostics

When micro traces are enabled; when macro traces are enabled and disabled

VirtualQueue

Call queuing


Enabling Micro Traces

Enable the micro trace diagnostics when you are troubleshooting problems with specific Cisco Unity components. For example, if there are AvWav errors in the Event log, enable the AvWav diagnostics. However, keep in mind that running diagnostics can affect system performance and hard drive space.

To Enable Micro Trace Diagnostics


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Diagnostic Tool. The Cisco Unity Diagnostic Viewer window appears.

Step 2 In the right pane of the Cisco Unity Diagnostic Viewer window, click the Configure Micro Traces icon. The Configure Micro Traces wizard appears.

Step 3 On the Welcome page, click Next.

Step 4 On the Configure Micro Traces page, check the check boxes to select the component traces and the trace levels that you want to enable.

Step 5 Click Next.

Step 6 On the Completing page, click Finish.

Step 7 In the right pane of the Cisco Unity Diagnostic Viewer window, click the Start New Log Files icon.

Step 8 Reproduce the problem.


Note After obtaining the diagnostic trace logs that you want, disable the traces that you enabled.



Viewing Individual Micro Trace Logs

Do the following procedure to use the UDT to view individual micro trace logs. For information on interpreting the micro trace information in the UDT, see the "How to Interpret Micro Trace Information in the Cisco Unity Diagnostic Tool (UDT)" section. For instructions on saving trace logs, see the "To Gather Micro Trace Logs into Files" procedure.

To View Individual Micro Trace Logs


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Diagnostic Tool. The Cisco Unity Diagnostic Viewer window appears.

Step 2 In the left pane of the Cisco Unity Diagnostic Viewer window, expand the Processes node.

Step 3 In the left pane, expand the process (or component) that you enabled traces for, and click the log file that you want to view. The log file is formatted and appears in the right pane.


How to Interpret Micro Trace Information in the Cisco Unity Diagnostic Tool (UDT)

When you open a trace log in the UDT, the information is formatted and displayed in columns in the right pane. Table 2-4 lists the information contained in each column of trace logs.

Table 2-4 Information in Trace Logs 

Column Name
Information Contained in the Column

#

The line number in the trace log. This number is provided by the UDT and is not contained in the trace log.

Timestamp

The date and time of the trace log.

Source

The source of the trace log text.

Trace No.

The number of the message string that was used from the source identified in the Source column.

Component

The micro trace component that was selected in the Configure Micro Traces wizard.

Level

The trace level that was selected in the Configure Micro Traces wizard.

Thread

The thread of the process from which the micro trace information was taken.

Port

The number of the voice messaging port that was used by the process. If no voice messaging port was used, the value is -1.

Call ID

The call identification number of the call that was handled by the process.

Trace

The raw data, delimited by commas, from the micro trace.


Gathering Micro Trace Logs into Files

When you are requested to send micro trace logs for examination, you must gather the logs into files. Do the following procedure for gathering micro trace logs into files.

To Gather Micro Trace Logs into Files


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Diagnostic Tool. The Cisco Unity Diagnostic Viewer window appears.

Step 2 In the right pane of the Cisco Unity Diagnostic Viewer window, click the Gather Log Files icon. The Gather Logs wizard appears.

Step 3 On the Welcome page, click Select Logs.

Step 4 If you want to change the directory where the files are saved, do the following sub-steps. Otherwise, skip to Step 5.

a. Click Browse to select a destination for the files. The Browse for Folder dialog box appears.

b. Click the destination directory where you want the files to be saved, and click OK.

Step 5 On the Welcome page, click Next.

Step 6 On the Select Logs to Gather page, expand the micro trace processes that you enabled and check the check box for the most recent log for each micro trace.

Step 7 Click Next.

Step 8 On the Completing page (after the logs are gathered and formatted), click View Directory to open the directory where the files were saved.

Step 9 On the Completing page, click Finish to exit the wizard.

Step 10 Close the Cisco Unity Diagnostic Viewer window.


Dialogic TSP Diagnostic Traces

When Cisco Unity is integrated with a circuit-switched phone system via voice cards, it may be necessary to obtain Dialogic TSP diagnostic traces. Do the following procedure.

To Obtain Dialogic TSP Diagnostic Traces


Step 1 Exit the Cisco Unity software, if it is running.

Step 2 Open a command prompt window and browse to the CommServer directory.

Step 3 At the command prompt, enter kill tapisrv and press Enter.

Step 4 Browse to the WinNT/System32 directory, and locate the file D41mt.tsp (standard TSP).

Step 5 Save the file to a secure location so that you can restore the standard TSP file later.

Step 6 Browse to the CommServer\DNA\Patch\Debug directory, and locate the file D41mt.tsp (debug TSP).


Caution The debug version of the Dialogic TSP can have a significant affect on system performance. We recommend that this debug TSP be used only while actively reproducing the problem during a period of light system usage.

Step 7 Copy the file you located in Step 6 to the WinNT\System32 directory.

Step 8 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 9 Right-click AvCsGateway, and click Properties.

Step 10 In the Startup Type field, click Manual, and click OK.

Step 11 Restart the Cisco Unity server.

Step 12 Log on and open a command prompt window.

Step 13 Browse to the CommServer\DNA\Patch\Debug directory.

Step 14 In the command prompt, enter dbmon > dbmon.txt to begin tracing the TSP. The output will go to the Dbmon.txt file.

Step 15 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 16 Right-click AvCsGateway, and click Start.

Step 17 Reproduce the problem.

Step 18 After the problem has been reproduced, press Ctrl-C to stop Dbmon.

Step 19 Copy the dbmon.txt file to a location where you want to keep it.

Step 20 Replace the debug version of the TSP in the System32 directory with the standard TSP file (D41mt.tsp), which you saved to a secure location in Step 5.

Step 21 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 22 Right-click AvCsGateway, and click Properties.

Step 23 In the Startup Type field, click Automatic, and click OK.

Step 24 For the changes to take effect, restart the Cisco Unity server.


Dr. Watson Logs

Dr. Watson is a program invoked by Windows 2000 when a serious problem occurs that is not handled by Cisco Unity. When Dr. Watson is invoked, a dialog box that contains an error message appears (for example, "Dr. Watson encountering an error in the AvCsMgr.exe process"). Dr. Watson errors may occur in other processes such as Tapisrv.exe and Dlgc_srv.exe.

To Obtain a Dr. Watson Log


Step 1 When a Dr. Watson error occurs, make a copy of the file Winnt\Drwtsn32.log.

Step 2 Before you attempt to reproduce the problem, from a command prompt, enter drwtsn32 and press Enter.

Step 3 In the Number of Instructions field, enter 50.

Step 4 In the Number of Errors to Save field, enter the number of errors that you want to record. The default is 10.

Step 5 Under Options, confirm that the Dump All Thread Contexts, Append to Existing Log File, Visual Notification, and Create Crash Dump File check boxes are checked.

Step 6 Click OK to close the dialog box.

Step 7 Reproduce the problem.

Step 8 Make a copy of the file Winnt\Drwtsn32.log.


Trace Settings for Troubleshooting Cisco Unity Components

This section describes the trace settings that you can use for troubleshooting specific Cisco Unity components, as follows:

Domino Directory Monitor Diagnostic Traces

AMIS Diagnostic Traces

For information on trace settings that you can use to troubleshoot message waiting indicators (MWIs), see the "Message Waiting Indicators (MWIs)" chapter.

Domino Directory Monitor Diagnostic Traces

You use the Cisco Unity Diagnostic tool (UDT) to set micro traces for the Domino directory monitor. The micro traces to enable are in the DSDomino group.

Diagnostic Trace Levels to Enable

If the creation, modification, or deletion of subscriber accounts, distribution lists, or location objects in the Cisco Unity Administrator fails, enable levels 00, 11, 12, and 17.

If changes made in the Domino directory are not reflected in Cisco Unity, enable levels 15, 16, and 17.

If the directory monitor service logs an error to the Windows Event log saying that it has thrown an exception, enable levels 00, 01, and 18.

See Table 2-5 for descriptions of the diagnostic trace levels.

Table 2-5 Diagnostic Trace Levels for the Domino Directory Monitor 

Diagnostic Trace Level
Description

00—High Level, Method Entry and Exit, and Parameter Values

Traces Cisco Unity Administrator calls to create, modify, delete, and find subscribers, distribution lists, and locations. Also traces calls to get and set system configuration parameters.

01—Low Level, Method Entry and Exit, and Parameter Values

Traces internal methods calls.

Note that enabling this level will produce very large diagnostic files.

02—Memory

Traces memory allocation and deallocation. There is seldom a need to enable this level.

10—Password Crypt

Traces handling of the Notes User ID and password.

11—CallProgress

Traces milestones in the internal methods used for importing, updating, and deleting subscribers, distribution lists, and location objects.

12—Method Parameters

Traces the parameters in the internal methods used for importing, updating, and deleting subscribers, distribution lists, and location objects.

13—Sync Start End

Traces synchronization initialization.

14—Monitor Initialization

Traces the initialization of the directory monitor service.

15—DB Access

Traces access to the SQL database on the Cisco Unity server.

16—Sync Progress

Traces milestones during synchronization. Synchronization happens every minute.

17—Errors

Traces internal API errors.

18—Notes API Errors

Traces errors from the Notes API.

19—Notes Fields Read and Write

Traces Notes reads and writes.

Note that enabling this level will produce very large diagnostic files.


AMIS Diagnostic Traces

The UDT provides macro and micro traces to help you troubleshoot AMIS message delivery problems. See the "AMIS Messages Are Not Delivered at All" section on page 6-2 for information on using the Unity Diagnostic tool to troubleshoot AMIS message delivery problems. See the following sections for more information about the applicable AMIS macro traces to set for your situation:

Basic Incoming and Outgoing AMIS Message Trace—These traces help you verify that Cisco Unity can send and receive AMIS messages. You can send test messages with these traces enabled to verify that the AMIS configuration is set up properly.

General Incoming AMIS Message Traces—These traces help you narrow down the problem to a specific Cisco Unity component. When troubleshooting incoming message problems, set these traces first.

Extensive Incoming AMIS Message Traces—These traces include more Cisco Unity components than the general traces, and therefore enable extensive logging. If you cannot determine the problem from the set of general traces, enable the traces specified in this section.

General Outgoing AMIS Message Traces—These traces help you narrow down the problem to a specific Cisco Unity component. When troubleshooting outgoing message problems, set these traces first.

Extensive Outgoing AMIS Message Traces—These traces include additional Cisco Unity components, and therefore enable extensive logging. If you cannot determine the problem from the set of general traces, enable the traces specified in this section.

Basic Incoming and Outgoing AMIS Message Trace

The Basic Incoming and Outgoing AMIS Message macro trace sets the following micro traces, which help you verify that Cisco Unity can send and receive AMIS messages:

Conversation—19

Notifier—28

General Incoming AMIS Message Traces

The General Incoming AMIS Message macro trace sets the following micro traces, which help you narrow down the problem to a specific Cisco Unity component:

CDE—10, 14, 18

AlCommon—10

DalDb—10

DalEx—10

Doh—10

MALEx—10

MALLn—10

Conversation—19

Extensive Incoming AMIS Message Traces

The Extensive Incoming AMIS Message macro trace sets the following micro traces, which include additional Cisco Unity components, and therefore enable extensive logging:

CDE—10, 11, 12, 13, 14, 18, 19

AlCommon—10

DalDb—10

DalEx—10

Doh—10

MALEx—10

MALLn—10

FailureConv—11

PhraseServer—12

Conversation—19

Miu General—13, 14

General Outgoing AMIS Message Traces

The General Outgoing AMIS Message macro trace sets the following micro traces, which help you narrow down the problem to a specific Cisco Unity component:

CDE—10, 14, 18

AlCommon—10

DalDb—10

DalEx—10

Doh—10

MALEx—10

MALLn—10

Conversation—19

Notifier—13, 19, 24, 26, 28

DominoMonitor—13 (Note that if no information is logged from the Domino Monitor 13 trace, it indicates that there is a problem.)

Extensive Outgoing AMIS Message Traces

The Extensive Outgoing AMIS Message macro trace sets the following micro traces, which include additional Cisco Unity components, and therefore enable extensive logging:

CDE—10, 11, 12, 13, 14, 18, 19

AlCommon—10

DalDb—10

DalEx—10

Doh—10

MALEx—10

MALLn—10

Conversation—19

FailureConv—11

PhraseServer—12

Notifier—13, 19, 20, 21, 24, 26, 28

DominoMonitor—13 (Note that if no information is logged from the Domino Monitor 13 trace, it indicates that there is a problem.)