Table Of Contents
Logs and Traces
Cisco Unity and Third-Party Logs and Traces
Dr. Watson Logs
Event Log Traces
Miu Diagnostics
TSP Traces
Exchange 5.5 Directory Monitor Diagnostic Traces
Active 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
Cisco Unity Voice Connector Logs
Performance Logging
Changing the Voice Connector Logging Properties
Retaining Outbound VPIM, Bridge, and SMTP Messages Temporarily
Logs and Traces
In this chapter you will find information to help you gather logs and traces when troubleshooting Cisco Unity.
Cisco Unity and Third-Party Logs and Traces
For problems in the Miu or TSP, Cisco TAC may ask for logs and traces before the problem can be diagnosed and fixed. Miu diagnostic logs, along with the Event log and/or Dr. Watson logs, if available, are usually sufficient for the initial phase of diagnosing a problem.
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 sections for details about third-party logs and traces:
•Dr. Watson Logs
•Event Log Traces
Most Cisco Unity components such as the Miu, Arbiter, Notifier, Conversations, and the Cisco Unity Administrator (also known as the "SA" or "System Administrator") can write diagnostic information to a log file. Diagnostic output of the problem occurring is critical to determining what caused the problem. If the problem seldom occurs, such as only once a day, it can be difficult to find the actual occurrence of the problem in the diagnostic log.
Note The raw data within the files in the Event logs 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.
See the following sections for details about Cisco Unity diagnostic traces:
•Miu Diagnostics
•TSP Traces
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 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.
Event Log Traces
The Event log is used by Windows applications to report errors and warnings. The Miu reports serious failures to the Event log (for example, "Component Miu: thread <XXX> had a failure on port <YYY> in AvWav").
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 Look for failure messages in the Application log. These can include errors from the Miu or AvWav, as well as errors from other Cisco Unity components or Exchange errors.
Step 4 If failure messages are present in the Application log, in the Tree pane, click Application Log. Then, on the Action menu, click Save Log File As.
Step 5 In the Save as Type field, click CSV, then click Save. Do not save the raw Event log data in a *.evt file.
Miu Diagnostics
Enable the Miu diagnostics when you are obtaining traces for an Miu problem. For example, if there are AvWav errors in the Event log, enable the AvWav diagnostics. However, keep in mind that running additional diagnostics can affect system performance and hard drive space.
You can use micro traces to set individual levels for selected MUI traces, or you can use macro traces to select preset combinations of traces.
To Obtain Micro Trace Miu Diagnostics
Step 1 On the Windows Start menu, click Programs > Cisco Unity > Unity Diagnostic Tool.
Step 2 On the Cisco Unity Diagnostic Viewer screen, 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 for selected traces in components beginning with Miu.
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.
Step 9 To view the log files, in the Tree pane, click Processes > AvCsMgr, and then click the Current log file.
Step 10 The selected log file appears in the right pane.
Step 11 To export or save a copy of the log file, on the Action menu, click Export List.
Step 12 Name the file and save it to a location of your choice in .txt or .csv format, then click Save.
Step 13 To turn off the traces set in Step 4, on the Cisco Unity Diagnostic Viewer screen, click the Disable All Traces icon.
Step 14 In the Disable All Traces Wizard screen, check the Disable All Traces check box, and click Finish.
To Obtain Macro Trace Miu Diagnostics
Step 1 On the Windows Start menu, click Programs > Cisco Unity > Unity Diagnostic Tool.
Step 2 On the Cisco Unity Diagnostic Viewer screen, 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 selected 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.
Step 9 To view the log files, in the Tree pane, click Processes > AvCsMgr, and then click the Current log file.
Step 10 The selected log file appears in the right pane.
Step 11 To export or save a copy of the log file, on the Action menu, click Export List.
Step 12 Name the file and save it to a location of your choice in .txt or .csv format, then click Save.
Step 13 To turn off the traces set in Step 4, on the Cisco Unity Diagnostic Viewer screen, click the Disable All Traces icon.
Step 14 In the Disable All Traces Wizard screen, check the Disable All Traces check box, and click Finish.
TSP Traces
If Cisco TAC determines that TSP traces are needed, they will ask you to provide them. The method to obtain TSP traces varies, depending on the TSP.
To Obtain Dialogic TSP 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 CommServer\Dialogic\Debug directory, and locate the file D41mt.tsp (debug TSP).
Caution The debug version of the Dialogic TSP can have a significant impact 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 5 Copy the file you located in Step 4 to the System32 directory.
Step 6 On the Windows Start menu, click Programs > Administrative Tools > Services.
Step 7 Right-click AvCsGateway, and click Properties.
Step 8 In the Startup Type field, click Manual, and click OK.
Step 9 Restart the Cisco Unity server.
Step 10 Log on and open a command prompt window.
Step 11 Browse to the CommServer\Dialogic\Debug directory.
Step 12 In the command prompt, enter dbmon > dbmon.txt to begin tracing the TSP. The output will go to the Dbmon.txt file.
Step 13 On the Windows Start menu, click Programs > Administrative Tools > Services.
Step 14 Right-click AvCsGateway, and click Start.
Step 15 Reproduce the problem.
Step 16 After the problem has been reproduced, press Ctrl-C to stop Dbmon.
Step 17 Copy the dbmon.txt file. Send the file to Cisco TAC.
Step 18 Replace the debug version of the TSP in the System32 directory with the original file (D41mt.tsp), which is in the CommServer\Dialogic\Lib directory.
Step 19 On the Windows Start menu, click Programs > Administrative Tools > Services.
Step 20 Right-click AvCsGateway, and click Properties.
Step 21 In the Startup Type field, click Automatic, and click OK.
Step 22 For the changes to take effect, restart the Cisco Unity server.
To Obtain Cisco Unity-CM TSP Traces
Step 1 Confirm that the clocks on Cisco Unity and Cisco CallManager are synchronized.
Step 2 Enable tracing on the Cisco CallManager system.
Step 3 On the Windows Start menu, click Programs > Cisco Unity > Unity Diagnostic Tool.
Step 4 On the Cisco Unity Diagnostic Viewer screen, click the Configure Macro Traces icon. The Configure Macro Traces wizard appears.
Step 5 On the Welcome page, click Next.
Step 6 On the Configure Macro Traces page, check the Skinny TSP check box.
Step 7 Click Next.
Step 8 On the Completing page, click Finish.
Step 9 On the Cisco Unity Diagnostic Viewer screen, click Start New Log Files.
Step 10 Reproduce the problem.
Step 11 To view the log files, in the Tree pane, click Processes > Svchost, and then click the Current log file.
Step 12 The selected log file is appears in the right pane.
Step 13 To export or save a copy of the log file, on the Action menu, click Export List.
Step 14 Name the file and save it to a location of your choice in .txt or .csv format, then click Save.
Step 15 To turn off the traces set in Step 6, on the Cisco Unity Diagnostic Viewer screen, click the Disable All Traces icon.
Step 16 In the Disable All Traces Wizard screen, check the Disable All Traces check box, and click Finish.
Exchange 5.5 Directory Monitor Diagnostic Traces
You use the Unity Diagnostic Tool to set micro traces for the Exchange 5.5 directory monitor. The micro traces to enable are in the DSEx55 group.
Flags to Enable
•If the creation, modification, or deletion of subscriber accounts, distribution lists, or location objects in the Cisco Unity Administrator fails, enable flags 00 and 10. If the diagnostics show an error when accessing the directory with LDAP, also enable flag 13 to get more details.
•If changes made in the Exchange 5.5 directory are not reflected in Cisco Unity, enable flags 10, 11, and 12. If the error is related to inconsistency in distribution list membership, also enable flag 17.
•If the directory monitor service logs an error to the Windows Event log saying that it has thrown an exception, enable flags 00, 01, and 10.
See Table 2-1 for descriptions of the diagnostic flags.
Table 2-1 Diagnostics Flags for the Exchange 5.5 Directory Monitor
Diagnostic Flag
|
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 calls to internal methods.
Note that enabling this flag will produce very large diagnostic files.
|
02—Memory
|
Traces memory allocation and deallocation. There is seldom a need to enable this flag.
|
10—General
|
Traces main events and all errors associated with them. This flag should always be enabled when a diagnostic file is needed.
|
11—Synchronization Start and End
|
Records the time when a synchronization cycle starts and ends.
|
12—Objects Queued for Change App
|
Traces the change or deletion of every object that has been detected and sent to Cisco Unity.
|
13—LDAP
|
The Exchange 5.5 monitor uses LDAP to access the Exchange 5.5 directory. When this flag is enabled, all LDAP operations are traced.
Note that enabling this flag will produce very large diagnostic files.
|
14—Initialization
|
Traces all initialization activity for the directory monitor service.
|
15—Shutdown
|
Traces all shutdown activity for the directory monitor service.
|
16—Configuration
|
Traces all configuration activity: reading and writing from the registry, default settings at initialization time, and access to internal configuration at run time.
|
17—Database Access
|
For performance reasons, the directory monitor keeps some information in a SQL database: the names of all distribution lists and their members, and a list of all Cisco Unity objects and the domain that they are in. Enable this flag when investigating errors in these areas.
|
18—Import Directory Connector
|
The import directory connector (IDC) is used by the Cisco Unity Administrator and the Cisco Unity Import utility to get lists of directory user objects that have not been imported into Cisco Unity. For example, when you choose to import a subscriber from the Cisco Unity Administrator, the list of directory objects it generates comes from the IDC.
The IDC returns properties on the non-imported users, which is how the Cisco Unity Administrator and the Cisco Unity Import utility fill in things like first name, last name, phone number, and so on. If you enable flag 18, you get traces that show the names and values of the retrieved attributes.
Enable this flag for troubleshooting import problems. For example, if the Cisco Unity Administrator does not display the first name of a person in the import list, enable this flag to see if the import directory component is correctly returning the value to the calling application.
|
Active Directory Monitor Diagnostic Traces
You use the Unity Diagnostic Tool to set micro traces for the Active Directory monitors. The diagnostics for the DC monitor are in the DSAD group. The diagnostics for the GC monitor are in the DSGlobalCatalog group. The flags that can be enabled are the same for both monitors.
Flags to Enable
•If the creation, modification, or deletion of subscriber accounts, distribution lists, or location objects in the Cisco Unity Administrator fails, enable flags 00 and 10. If the diagnostics show an error when accessing Active Directory, also enable flag 12 to get more details.
•If changes made in Active Directory are not reflected in Cisco Unity, enable flags 10, 11, and 17. If the error is related to inconsistency in distribution list membership, also enable flag 16.
•If the directory monitor service logs an error to the Windows Event log saying that it has thrown an exception, enable flags 00, 01, and 10.
See Table 2-2 for descriptions of the diagnostic flags.
Table 2-2 Diagnostic Flags for the Active Directory Monitors
Diagnostic Flag
|
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 flag will produce very large diagnostic files.
|
02—Memory
|
Traces memory allocation and deallocation. There is seldom a need to enable this flag.
|
10—General
|
Traces main events and all errors associated with them. This flag should always be enabled when a diagnostic file is needed.
|
11—Changes Queued
|
Traces the change or deletion of every object that has been detected and sent to Cisco Unity.
|
12—ADSI Operations
|
The monitor uses ADSI (Active Directory Services Interface) to access Active Directory. When this flag is enabled, all ADSI operations are traced.
Note that enabling this flag will produce very large diagnostic files.
|
13—Initialization
|
Traces all initialization activity for the directory monitor service.
|
14—Shutdown
|
Traces all shutdown activity for the directory monitor service.
|
15—Configuration
|
Traces all configuration activity: reading and writing from the registry, default settings at initialization time, and access to internal configuration at run time.
|
16—Database Access
|
For performance reasons, the monitor keeps some information in a SQL database: the names of all distribution lists and their members, and a list of all Cisco Unity objects and the domain that they are in. Enable this flag when investigating errors in these areas.
|
17—Synchronization Start and End
|
Records the time when a synchronization cycle starts and ends, and also the start and end time for the synchronization of each single domain (if enabled in the DSAD group).
|
18—Import Directory Connector
(DSGlobalCatalog only)
|
The import directory connector (IDC) is used by the Cisco Unity Administrator and the Cisco Unity Import utility to get lists of directory user objects that have not been imported into Cisco Unity. For example, when you choose to import a subscriber from the Cisco Unity Administrator, the list of directory objects it generates comes from the IDC.
The IDC returns properties on the non-imported users, which is how the Cisco Unity Administrator and the Cisco Unity Import utility fill in things like first name, last name, phone number, and so on. If you enable flag 18, you get traces that show the names and values of the retrieved attributes.
Enable this flag for troubleshooting import problems. For example, if the Cisco Unity Administrator does not display the first name of a person in the import list, enable this flag to see if the import directory component is correctly returning the value to the calling application.
|
18—Input Property Lists
(DSAD only)
|
Low-level diagnostic trace. Do not enable unless requested to do so by Cisco TAC.
|
19—Output Property Lists
(DSAD only)
|
Low-level diagnostic trace. Do not enable unless requested to do so by Cisco TAC.
|
AMIS Diagnostic Traces
The Unity Diagnostic Tool provides macro and micro traces to help you troubleshoot AMIS message delivery problems. See the "To Set and Retrieve Traces for AMIS Messages" section for information on using the Unity Diagnostic tool. 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:
•Conv AMIS—28
•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
•Conv AMIS—28
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
•Conv AMIS—13, 14, 15, 17, 20, 23, 25, 26, 27, 28
•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
•Conv AMIS—28
•Notifier—13, 19, 24, 26, 28
•ExchangeMonitor—13 (Note that if no information is logged from the Exchange Monitor 13 trace, this indicates 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
•Conv AMIS—13, 14, 15, 17, 20, 23, 25, 26, 27, 28
•FailureConv—11
•PhraseServer—12
•Notifier—13, 19, 20, 21, 24, 26, 28
•ExchangeMonitor—13 (Note that if no information is logged from the Exchange Monitor 13 trace, this indicates a problem.)
Cisco Unity Voice Connector Logs
With the Voice Connector version 10.0(1) and later, logging is enabled by default at the Warning level. Also by default, the log files are kept for 14 days before being deleted. The default location for the log files is on the Exchange server on which the Voice Connector is installed, in the following directory, as applicable:
•Exchange 2000: <Exchange Server Path>\VoiceGateway\LogFiles
•Exchange 5.5: <Exchange Server Path>\IvcData\LogFiles
The Voice Connector provides several logging levels that allow you to control the level of detail that is logged to the files. The logging levels are:
•Function (level 5)
•Information (level 4)
•Warning (level 3)
•Error (level 2)
•Core (level 1)
•No Logging (level 0)
The higher levels provide more detail, and each level includes all levels below it. For example, the Information level includes Warning, Error and Core. When logging is enabled at any level, performance data is logged to a separate file. (See the "Performance Logging" section for more information.) Changing the logging level does not change the data written to the performance log.
The Voice Connector allows you to set the logging level, the number of days to keep log files, and the location of the log files. The logging properties for the Voice Connector for Exchange 2000 can be modified in the Exchange System manager. See the "To Change the Voice Connector Logging Settings (Exchange 2000)" procedure.
The logging properties for the Voice Connector for Exchange 5.5 must be modified in the registry. You use the logging level numbers listed above when changing the logging level in the registry. See the "To Change the Voice Connector Logging Settings (Exchange 5.5)" procedure.
Note that the Voice Connector service must be restarted for logging changes to take effect.
Two log files per day are created:
•Voice Connector log files are named GwIvc_YyMmDd.log, where Yy is the year, Mm is the month and Dd is the day.
•Voice Connector performance log files are named GwIvc_perf_ YyMmDd.log, where Yy is the year, Mm is the month and Dd is the day.
Performance Logging
By examining the performance log (or writing a tool to extract the data), the following information can be obtained:
•The total number of inbound messages accepted.
•The total number of outbound messages sent.
•The rate at which inbound messages are being received (messages/second).
•The rate at which outbound messages are being sent (messages/second).
•The total number of bytes sent.
•The total number of bytes received.
•The rate that bytes are being received (bytes/second).
•The rate that bytes are being sent (bytes/second).
•The number of NDRs generated.
•The time that it takes for messages to be sent by the Voice Connector.
The format for the performance log is:
Date Time ThreadId Address Type=<Type> Message Status=<Status> Size=<size KB> Time In Queue=(time sec)
The following table defines the fields:
Table 2-3 Performance Log Fields
Field
|
Description
|
Type
|
Indicates the message address type:
•AMIS
•VOICE
•VPIM
•Bridge
|
Status
|
Indicates the status of the message, as follows:
•Incoming
•Outgoing
•NDR for Incoming
•NDR for Outgoing
|
Time in Queue
|
The Time in Queue—measured in seconds—has a different meaning depending on the message status:
•Outgoing Message—equals the difference between the current time and the time the message was submitted by the telephone user interface (TUI), ViewMail, or the Cisco Unity Inbox. This includes the time taken by the Exchange MTA to process the message and deliver it to the Voice Connector queue.
•Incoming Message—equals the difference between the current time and the time the message was received by Exchange.
•NDR Messages—equals the difference between the current time and the time the original message was processed (and the NDR was generated). Typically, this will be 0 or close to 0.
|
Changing the Voice Connector Logging Properties
Use the applicable procedure to change the Voice Connector logging:
•To Change the Voice Connector Logging Settings (Exchange 2000)
•To Change the Voice Connector Logging Settings (Exchange 5.5)
To Change the Voice Connector Logging Settings (Exchange 2000)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Programs > Microsoft Exchange > Exchange System Manager.
Step 3 Expand the Connectors container in the left-hand pane.
Step 4 Right-click Exchange 2000 Voice Connector (<Server Name>), and select Properties.
Note that the properties pages for administering the Voice Connector are always displayed in English.
Step 5 Click the Advanced tab.
Step 6 Adjust the logging level and the other settings as needed. If you change the directory where the log files are created, be sure to end the path with a backslash ("\").
Note that if you increase the logging level (the default is Warning), the log file size increases. This could become an issue if hard-disk space is a concern.
Step 7 Click OK and exit Exchange System Manager.
Step 8 Open the Windows Services Applet.
Step 9 Right-click Exchange 2000 Voice Connector and select Restart.
Step 10 Exit the Windows Services Applet.
To Change the Voice Connector Logging Settings (Exchange 5.5)
Step 1 Log on to the Exchange server on which the Voice Connector is installed, and start Regedit.
Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.
Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.
Step 3 To change the number of days to keep the log files before they are deleted:
a. Expand the key HKEY_LOCAL_MACHINE\Software\ActiveVoice\AvIVC.
b. Double-click LogCycleDays to display the Edit DWORD Value dialog box.
c. Select Hexidecimal or Decimal to indicate the base of the value that you will enter.
d. Enter the number and click OK.
Step 4 To change the logging level:
a. Expand the key HKEY_LOCAL_MACHINE\Software\ActiveVoice\AvIVC.
b. Double-click LogLevel to display the Edit DWORD Value dialog box.
c. Enter a number from 0 to 5, where 0 indicates no logging and 5 indicates the highest logging level, and click OK.
Step 5 To change the location of the log files:
a. Expand the key HKEY_LOCAL_MACHINE\Software\ActiveVoice\AvIVC.
b. Double-click LoggingPath to display the Edit String dialog box.
c. Enter the full directory path where the log files are to be created. Be sure to end the path with a backslash ("\").
Step 6 Click OK, and close Regedit.
Step 7 Open the Windows Services Applet.
Step 8 Right-click Exchange 2000 Voice Connector and select Restart.
Step 9 Close the Windows Services Applet.
Retaining Outbound VPIM, Bridge, and SMTP Messages Temporarily
If needed for troubleshooting message delivery problems, you can change a registry setting so that outbound VPIM, Bridge, and SMTP messages processed by the Voice Connector are copied as text files to a specified directory. This setting does not apply to outbound AMIS messages.
To Retain Outbound VPIM, Bridge, and SMTP Messages Processed by the Voice Connector
Step 1 Log on to the Exchange server on which the Voice Connector is installed, and start Regedit.
Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.
Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.
Step 3 Expand the key HKEY_LOCAL_MACHINE\Software\ActiveVoice\AvIVC.
Step 4 Click Edit > New > String Value.
Step 5 Enter StoreFiles as the name.
Step 6 Double-click StoreFiles to display the Edit String dialog box.
Step 7 Enter the full directory path where the log files are to be created. Be sure to end the path with a backslash ("\").
Step 8 Click OK and close Regedit.
Step 9 Open the Windows Services Applet.
Step 10 Right-click Exchange 2000 Voice Connector and select Restart.
Step 11 Close the Windows Services Applet.
Note When finished troubleshooting, be sure to delete the StoreFiles key that you created in the registry, and restart the Voice Connector service.
Feedback
