 Feedback
|
Table Of Contents
Release Notes for Cisco Unity Release 4.1(1)
System Requirements, and Supported Hardware and Software
Hewlett-Packard Service Pack for ProLiant DL380 G2 Server
Determining the Software Version
Cisco Unity Voice Connector for Microsoft Exchange
Active Directory Schema Extensions for Cisco Unity with Exchange
Cisco Personal Communications Assistant (PCA)
Cisco Unity ViewMail for Microsoft Outlook
Important Information to Note from Earlier Cisco Unity 4.(x) Release Notes
Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging
Service Pack 3a for SQL Server 2000 and MSDE 2000 Is Required
Voice Cards Are Not Supported When Windows 2003 Is Installed On the Cisco Unity Server
Downloading Software for Cisco Unity 4.1(1)
Downloading Microsoft Updates Recommended for Use With Cisco Unity
Downloading Cisco Unity Service-Pack CD Images
Downloading Cisco Unity 4.1(1) CD Images
Upgrading to Cisco Unity 4.1(1)
New and Changed Requirements and Support—Release 4.1(1)
Cisco Unity-CM TSP Version 8.0(2)
Cisco Unity Documentation Addendum
Cisco Unity Integration Guides
Cisco Unity Documentation Policy Has Changed
Cisco Unity Failover Supports Integrations Through PIMG Units
Cisco Unity ViewMail for Microsoft Outlook Version 4.1(1)
Cisco Unity Voice Connector for Microsoft Exchange
Digital Networking with Older Versions of Cisco Unity
IBM Lotus Domino 5.x and IBM Lotus Notes 5.x Are No Longer Supported
IBM Lotus Domino Unified Communications (DUC) for Cisco
Phone System Integrations Qualified for Use with Cisco Unity
Software Qualified for Use on Cisco Unity Subscriber Workstations
Upgrades to Version 4.1(1) from Localized Versions of Cisco Unity Are Not Supported
WAN Connection to Phone Systems Integrated Through PIMG Units
New Functionality—Release 4.1(1)
Cisco Unity Conversation Enhancements
Cisco Unity with Exchange: Alternate Greeting Notices
Cisco Unity with Exchange: Changing How Cisco Unity Handles Messages That Contain Text
Cisco Unity with Exchange: Disabling Delete Confirmations in the Cisco Unity Inbox
Cisco Unity with Exchange: Message Locator Searches Can Include Receipts
Customizing the Cisco Unity Conversation: Enabling a Post-Greeting Recording
Customizing the Cisco Unity Conversation: Disabling the "Record Your Message at the Tone" Prompt
Customizing the Cisco Unity Conversation: Disabling the "Wait While I Transfer Your Call" Prompt
Changed Functionality—Release 4.1(1)
Cisco Unity Conversation Changes
Cisco Unity Conversation: Messages Are No Longer Marked Urgent Automatically
Cisco Unity Conversation: Phone Menu Response Settings Apply to All Menus
Cisco Unity Conversation: Reduced Delays After Multiple Key Presses
Cisco Unity Conversation: Subscribers Can Press ## or 00 to Switch Search Modes
Cisco Unity Conversation: "Too Many Matching Names" Prompt Clarified
FAQ Available in Cisco Unity Administrator and on Cisco Unity Desktop
Usability Improved on Subscribers > Subscribers > Account Page in the Cisco Unity Administrator
Installation and Upgrade Notes
Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run
Cisco Unity Phone Conversation System Prompts
Cisco Unity with Exchange: Setting to Exclude All Receipts Respected
Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter
Upgrade from Cisco Unity 2.x to Version 4.1(1) May Require Upgrade to Version 4.0(4) First
Upgrades from Cisco Unity Versions Earlier Than 2.3(4.104) Are Not Supported
Cisco Unity 4.1(1) Is Available Only in U.S. English
Cisco Unity Conversation: Delay When Subscribers Press 00 to Switch Search Modes
Cisco Unity Conversation: Unexpected Behavior in Message Playback Help
Cisco Unity with Exchange: Private Secure Messaging
PIMG Integrations Over a WAN That Use the G.729a Codec Must Disable Comfort Noise
System Transfers Not Included in Transfer Call Billing Reports
Text to Speech Does Not Read Name in the From Field in E-mail
Windows Application Event Log May Not Display Third-Party Product Name in Start-Up Log Entry
Resolved Caveats—Release 4.1(1)
Installing a Cisco Unity Demonstration System
Limits on a Cisco Unity Demonstration System
Enabling a Cisco Unity Demonstration System with the Default License File
Enabling a Cisco Unity Demonstration System with the Time-Limited License File
Converting a Cisco Unity Demonstration System to a Standard System
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco Unity Release 4.1(1)
Revised April 10, 2006
These release notes contain information on downloading software, new and changed support, new and changed functionality, limitations and restrictions, and open and resolved caveats for Cisco Unity Release 4.1(1).
CautionCisco Unity 4.1(1) is available only in U.S. English. You can install Cisco Unity 4.1(1) only on a server on which the U.S. English version of Windows 2000 Server or Windows Server 2003 is installed; you cannot change the locale of Windows to a setting other than English (United States); and you cannot upgrade an existing Cisco Unity system that is using a language other than U.S. English to version 4.1(1).
Note that our documentation approach for minor releases, including Cisco Unity 4.1, has changed. See the "Cisco Unity Documentation Policy Has Changed" section.
Note
Contents
These release notes contain the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
System Requirements, and Supported Hardware and Software
The following documents list the most current Cisco Unity requirements and are available on Cisco.com:
•
•
•
Compatibility Information
The following documents list the most current version combinations qualified for use with Cisco Unity and are available on Cisco.com:
•
•
•
Hewlett-Packard Service Pack for ProLiant DL380 G2 Server
A customer-provided Hewlett-Packard ProLiant DL380 G2 server with a Magma expansion chassis requires a system BIOS version P24 dated June 26, 2002 or later, available from the Hewlett-Packard website.
Determining the Software Version
This section contains procedures for determining the version in use for the following software:
•
•
•
•
Cisco Unity
To Determine the Cisco Unity Version in Use by Using the Cisco Unity Administrator
In the Cisco Unity Administrator, go to the System > Configuration > Software Versions page. The Cisco Unity version is displayed in the Cisco Unity Build Number field.
To Determine the Cisco Unity Version in Use by Using the AvCsMgr.exe File (Cisco Unity 3.0(4) and Later)
Step 1
Step 2
Step 3
Step 4
Cisco Unity-CM TSP
To Determine the Cisco Unity-CM TSP Version in Use by Using the Cisco Unity Telephony Integration Manager
Step 1
Step 2
Step 3
To Determine the Cisco Unity-CM TSP Version in Use by Using the AvSkinny.tsp File
Step 1
Step 2
Step 3
Step 4
Cisco Unity Voice Connector for Microsoft Exchange
This section contains two procedures. Do the procedure for your version of Cisco Unity.
To Determine the Voice Connector Version in Use: Cisco Unity 4.0 and Later, Voice Connector 10.0 and Later
Step 1
Step 2
or Exchange 2003<ExchangeServerPath>\VoiceGateway\Bin
<ExchangeServerPath>\Connect\Voice\Bin
Step 3
Step 4
Step 5
To Determine the Voice Connector Version in Use: Cisco Unity 3.0 Through 3.1
Step 1
Step 2
<ExchangeServerPath>\VoiceGateway\Bin\LocalizedFiles\ENU
<ExchangeServerPath>\Voice\Bin\LocalizedFiles\ENU
Step 3
Step 4
Active Directory Schema Extensions for Cisco Unity with Exchange
In Cisco Unity 4.0(1), the attribute cisco-Ecsbu-UM-Schema-Version was added to the LDIF script file Avdirmonex2k.ldf, which contains the Active Directory schema extensions required by Cisco Unity with Exchange 2000 and Exchange 2003. In Cisco Unity 4.0(3), the attribute cisco-Ecsbu-UM-Schema-Version was added to the LDIF script files Omnigateway.ldf and Vpimgateway.ldf, which are used to extend the Active Directory schema for Bridge Networking and VPIM Networking, respectively.
To extend the Active Directory schema, you run a Cisco Unity utility called ADSchemaSetup. The utility applies the schema extensions specified in the LDIF script files located on Cisco Unity DVD 1 and CD 1 in the directory Schema\LdifScripts. (A procedure for running ADSchemaSetup is included in the Cisco Unity installation guide, the Networking in Cisco Unity Guide, the Cisco Unity Bridge Installation Guide, and the Cisco Unity Bridge Networking Guide.)
The user interface for ADSchemaSetup consists of a dialog box with check boxes that correspond to the following LDIF script files:
To View the Version of the Schema Extensions
Step 1
Step 2
Step 3
Step 4
•
•
•
Note that the version displayed is the Cisco Unity version when the LDIF file was last modified, which may be older than your Cisco Unity version. (For example, the last time Vpimgateway.ldf was modified was in 4.0(3), so you will see "Unity VPIM 4.0(3)" as the description even though you have installed a later version.)
In future versions of Cisco Unity, the LDIF scripts will be updated to write a new version description if there are changes between versions. The updated description will be added to the existing description rather than replacing it so that there is a history of the schema extensions that have been applied.
For example, assume that the schema has been extended for Cisco Unity 4.0(2). If in Cisco Unity 4.0(9) there are changes to the file Avdirmonex2k.ldf, the description for cisco-Ecsbu-UM-Schema-Version would be:
Unity 4.0
Unity 4.0(9)Note that the above is just an example. There are no changes planned to Avdirmonex2k.ldf at this time.
G.729a Audio Codec
When the G.729a audio codec has been installed on the Cisco Unity server or on a subscriber workstation, do the following procedure to determine the codec version.
To Determine the G.729a Audio Codec Version in Use
Step 1
Step 2
Step 3
Step 4
Cisco Personal Communications Assistant (PCA)
To Determine the Cisco Personal Communications Assistant (PCA) Version in Use
Step 1
Step 2
Step 3
Step 4
The Cisco Unity version is displayed. The Cisco PCA version is the same as the Cisco Unity version.
Cisco Unity ViewMail for Microsoft Outlook
There are two ways to determine the version of ViewMail in use on a subscriber workstation. Do either procedure, as applicable.
To Determine the ViewMail Version in Use from Add/Remove Programs
Step 1
Step 2
To Determine the ViewMail Version in Use from Outlook
In the Outlook Inbox on the subscriber workstation, on the Help menu, click About ViewMail.
Important Information to Note from Earlier Cisco Unity 4.(x) Release Notes
This section contains information worth noting from the release notes of Cisco Unity versions earlier than 4.1(1). Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging
When Cisco Unity with Exchange is configured as Unified Messaging, Exchange cannot be installed on the Cisco Unity server for Cisco Unity 4.x. You must either move Exchange users to other Exchange servers or, if there are no other Exchange servers, you must install Exchange on another server and move Exchange users to the new server.
(When Cisco Unity is configured as Voice Messaging, Exchange 5.5 is supported on a Cisco Unity 4.x server only if you are upgrading from a previous version of Cisco Unity. Exchange 2000 is supported on the Cisco Unity server both for upgrades and for new installations in the Voice Messaging configuration.)
Service Pack 3a for SQL Server 2000 and MSDE 2000 Is Required
Because of the W32.Slammer worm, Cisco requires Service Pack 3a for Microsoft SQL Server 2000 and MSDE 2000 with Cisco Unity 4.x.
Voice Cards Are Not Supported When Windows 2003 Is Installed On the Cisco Unity Server
When Windows Server 2003 is installed on the Cisco Unity server, voice cards and Dialogic software will not function correctly. Consequently, integrations that use voice cards are not supported for Cisco Unity servers on which Windows Server 2003 is installed. However, IP integrations (Cisco CallManager or Cisco SIP Proxy Server) and PIMG integrations are supported for Cisco Unity servers on which Windows Server 2003 is installed.
Downloading Software for Cisco Unity 4.1(1)
This section contains procedures for downloading the Microsoft updates recommended for use with Cisco Unity, and the CD images of the Cisco Unity Service Packs CDs and of Cisco Unity 4.1(1) CDs.
Caution
Downloading Microsoft Updates Recommended for Use With Cisco Unity
Caution
To Download Microsoft Updates Recommended for Use With Cisco Unity
Step 1
Step 2
Step 3
Note
Step 4
Caution
Step 5
Step 6
Step 7
a.
b.
Step 8
If you have a Post-Installation CD shipped from Cisco, set it aside so you do not accidentally use the wrong CD during installation or upgrade.
Step 9
Downloading Cisco Unity Service-Pack CD Images
Table 1 lists the contents of the service-pack CD images for Cisco Unity 4.1(1).
To Download Service-Pack CD Images
Step 1
Step 2
Step 3
Note
Step 4
Step 5
Step 6
Step 7
a.
b.
Step 8
If you have service pack CDs shipped from Cisco, set them aside so you do not accidentally use the wrong CD during installation or upgrade.
Step 9
Downloading Cisco Unity 4.1(1) CD Images
Table 2 lists the contents of the Cisco Unity 4.1(1) CD images. The images contain only Cisco Unity software. They do not contain any third-party software.
Caution
To Download Cisco Unity 4.1(1) CD Images
Step 1
Step 2
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
a.
b.
Step 10
Step 11
Upgrading to Cisco Unity 4.1(1)
Caution
For upgrades from earlier U.S. English versions of Cisco Unity, refer to the applicable chapter of the Cisco Unity Reconfiguration and Upgrade Guide:
•
•
•
The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/ex/index.htm.
Note
New and Changed Requirements and Support—Release 4.1(1)
This section contains information about new and changed requirements and support in the Cisco Unity Release 4.1(1) time frame only. Refer to the release notes of the applicable version for information on new and changed support with earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Cisco Unity-CM TSP Version 8.0(2)
Cisco Unity-CM TSP 8.0(2) is qualified for use with Cisco Unity version 4.1(1). For information on the Cisco Unity-CM TSP, refer to Release Notes for Cisco Unity-CM TSP Release 8.0(2) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/tsp/tsp802rn.htm.
(The Cisco Unity-CM TSP is used only for the Cisco CallManager and Cisco CallManager Express integrations.)
Cisco Unity Documentation
The section lists new product documentation available with this release.
Cisco Unity Documentation Addendum
New and changed content related to version 4.1(1) is available in the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
The Cisco Unity Documentation Addendum, Release 4.1 should be used with the 4.0(5) and later versions of the Cisco Unity guides on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/tsd_products_support_series_home.html. Everything in those guides applies to 4.1(1), except as noted in the addendum.
See also the "Cisco Unity Documentation Policy Has Changed" section.
Cisco Unity Integration Guides
The following Cisco Unity integration guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html:
•
•
Cisco Unity Documentation Policy Has Changed
Beginning with Cisco Unity 4.1, we are no longer revising product guides for minor releases. Instead, we are publishing a documentation addendum that is designed to be used in conjunction with the last published guides. The Cisco Unity Documentation Addendum, Release 4.1 should be used with the 4.0(5) and later versions of Cisco Unity guides on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/tsd_products_support_series_home.html. Everything in those guides applies to version 4.1(1), except as noted in the addendum.
Each chapter in the addendum corresponds to a guide in the product documentation set. New features are described in sections in the applicable guide chapter. Information that has changed in a guide—either because Cisco Unity functionality changed or because the information is incorrect—is described in the "Errors" section at the end of the guide chapter. (Note that if a guide has no corresponding chapter in the addendum, it means that there is no new or changed content, and the 4.0(5) and later version of the guide on Cisco.com applies to 4.1(1).)
For all release types (major, minor, and maintenance), release notes will continue to be published, and non-versioned documentation (for example, compatibility matrixes and Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge) and Cisco Unity System Requirements, and Supported Hardware and Software will continue to be updated. Release notes also will continue to summarize new and changed functionality, and will refer to the applicable sections in the addendum for more information.
The Cisco Unity Documentation Addendum, Release 4.1 is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm. A link to the addendum appears under the heading "Cisco Unity Version 4.1" on the Cisco.com web page for each guide type (Install and Upgrade Guides, Configuration Guides, Feature Guides, Maintain and Operate Guides, etc.).
Cisco Unity Failover Supports Integrations Through PIMG Units
Integrations with circuit-switched phone systems through PIMG units are supported for use with a Cisco Unity system configured for failover.
Cisco Unity Tools Depot
The Cisco Unity Tools Depot is a collection of utilities that perform a variety of administration, audio management, diagnostic, reporting, and phone system integration functions. To display the Tools Depot, double-click the Cisco Unity Tools Depot icon on the Cisco Unity server desktop or click Programs > Unity > Cisco Unity Tools Depot on the Windows Start menu. The left pane of the Tools Depot lists all of the available utilities by category. To display Help for a utility, click the name in the left pane. To run the utility, double-click the name.
Most of the utilities in the Tools Depot are also available on the Cisco Unity Tools website (http://ciscounitytools.com), where updates to utilities are frequently posted between Cisco Unity releases. If the Cisco Unity server is connected to the Internet and you run a Tools Depot utility that is available on the Cisco Unity Tools website, the utility automatically checks to see whether an updated version is available. If the Cisco Unity server is not connected to the Internet, we recommend that you check the Cisco Unity Tools website to determine whether a later version of the utility is available.
You can sign up to be notified when the utilities posted on the Cisco Unity Tools website are updated. Go to http://ciscounitytools.com and click Sign Up Here.
Some utilities work only with selected versions of Cisco Unity. If a utility does not appear in the Tools Depot, it does not work with the version of Cisco Unity currently running.
Cisco Unity ViewMail for Microsoft Outlook Version 4.1(1)
ViewMail for Outlook version 4.1(1) will be available in the near future on the ViewMail for Microsoft Outlook Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-vmo.
In the meantime, for new installations, you can download previous versions of ViewMail from the ViewMail for Microsoft Outlook Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-vmo.
Note
When ViewMail 4.1(1) is released, Release Notes for Cisco Unity ViewMail for Microsoft Outlook Release 4.1(1) will be available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/vmo/vmo411rn.htm.
Cisco Unity Voice Connector for Microsoft Exchange
Cisco Unity 4.1(1) supports version 11.0(1) and later of the Cisco Unity Voice Connector for Microsoft Exchange for AMIS Networking, VPIM Networking, and SMTP Networking. Voice Connector versions 10.0(2) and 10.0(1) are not supported when the bridgehead Cisco Unity server is running version 4.1(1).
For Bridge Networking, only Voice Connector versions 11.0(3) and later are supported when the bridgehead Cisco Unity server is running version 4.1(1).
We recommend that you use the latest version of the Voice Connector that is supported for your version of Cisco Unity. If you call Cisco TAC with a problem related to networking, the Cisco TAC engineer may require that you upgrade to a newer supported version of the Voice Connector, if one is available.
For the most current compatibility information, refer to the applicable section of Cisco Unity Networking Options Requirements:
•
•
•
•
The document is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/netrq.htm.
Digital Networking with Older Versions of Cisco Unity
Cisco Unity 4.1(1) supports Digital Networking with other Cisco Unity servers running version 4.0(1) or later. Versions earlier than 4.0(1) are not supported.
For the most current version compatibility information, refer to the applicable section of Cisco Unity Networking Options Requirements at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/netrq.htm.
IBM Lotus Domino
IBM Lotus Domino version 7.0 will be supported for use with Cisco Unity 4.1(1) in an engineering special following the 4.1(1) release. Domino 7.0 will be supported only when used with IBM Lotus Domino Unified Communications (DUC) for Cisco version 1.2.3 on Domino servers running IBM AIX or Microsoft Windows.
Neither the Cisco Unity 4.1 engineering special nor DUC for Cisco 1.2.3 were available when Cisco Unity 4.1(1) was released. For information on whether DUC for Cisco 1.2.3 has been released, refer to the IBM Lotus Domino website.The Cisco Unity 4.1 engineering special is expected to be released in November 2005; when the engineering special is released, the Cisco Unity 4.1 Engineering Special Index will be available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/relnote/411index.htm.
For the most current list of all supported Domino versions—including versions qualified since the release of Cisco Unity version 4.1(1)—refer to the "Software Requirements—Message Store" section of Cisco Unity 4.x System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.
IBM Lotus Domino 5.x and IBM Lotus Notes 5.x Are No Longer Supported
IBM Lotus ended service for Lotus Notes 5.x and Lotus Domino 5.x on September 30, 2005. Beginning with version 4.1(1), Lotus Notes 5.x and Domino 5.x are not supported for use with Cisco Unity.
IBM Lotus Domino Unified Communications (DUC) for Cisco
DUC for Cisco version 1.2.3 on Domino servers running IBM AIX or Windows will be supported for use with Cisco Unity 4.1(1) in an engineering special following the 4.1(1) release.
Neither the Cisco Unity 4.1 engineering special nor DUC for Cisco 1.2.3 were available when Cisco Unity 4.1(1) was released. For information on whether DUC for Cisco 1.2.3 has been released, refer to the IBM Lotus Domino website.The Cisco Unity 4.1 engineering special is expected to be released in November 2005; when the engineering special is released, the Cisco Unity 4.1 Engineering Special Index will be available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/relnote/411index.htm.
For the most current list of all supported DUC for Cisco versions—including versions qualified since the release of Cisco Unity version 4.1(1)—refer to the "Software Requirements—Message Store" section of Cisco Unity 4.x System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.
Mobile Message Access for BlackBerry Available for Use with Cisco Unity Unified Messaging with Exchange
Revised April 10, 2006
Cisco Unity Mobile Message Access for BlackBerry version 1.0(1) has been qualified for use with Cisco Unity version 4.1(1) in a Unified Messaging configuration and with BlackBerry Enterprise Server version 4.0 Service Pack 2 and later.
Refer to Release Notes for Cisco Unity Mobile Message Access for BlackBerry Release 1.0(1) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bb/bb101rn.htm.
Before you offer Mobile Message Access for BlackBerry to subscribers in your organization, review the following information in the Cisco Unity Documentation Addendum, Release 4.1:
•
•
The addendum is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Phone System Integrations Qualified for Use with Cisco Unity
The following phone system integrations have been qualified for use with Cisco Unity:
•
•
For the most current list of all supported phone system integrations—including integrations qualified since the release of Cisco Unity version 4.1(1)—refer to the "Supported Phone System Integrations" section of Cisco Unity 4.x System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.
Software Qualified for Use on Cisco Unity Subscriber Workstations
The following software has been qualified for use on Cisco Unity subscriber workstations:
Cisco Unity with Domino
•
–
–
•
Cisco Unity with Exchange
•
–
–
•
For the most current version combinations of software qualified for use on subscriber workstations—including software qualified since the release of Cisco Unity version 4.1(1)—refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/clientmx.htm.
Upgrades to Version 4.1(1) from Localized Versions of Cisco Unity Are Not Supported
Upgrades to Cisco Unity 4.1(1) from localized versions of Cisco Unity are not supported. Version 4.1(1) is available only in U.S. English; no multilingual version of the release is planned.
WAN Connection to Phone Systems Integrated Through PIMG Units
Cisco Unity supports connecting across a WAN to a circuit-switched phone system that integrates through PIMG units. The requirements for the WAN connection are:
•
•
•
•
New Functionality—Release 4.1(1)
This section contains information about new functionality for Cisco Unity Release 4.1(1) only. Refer to the release notes of the applicable version for information on new functionality in earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity 4.1(1). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.
Cisco Unity Conversation Enhancements
The Cisco Unity conversation—also known as the TUI (telephone user interface)—has been enhanced in several ways. The enhancements are described individually within the "New Functionality—Release 4.1(1)" section:
•
•
•
•
•
For a summary of changes made to the default settings and functionality for the Cisco Unity conversation and the Cisco PCA applications for Cisco Unity 4.1(1), see the "Changed Functionality—Release 4.1(1)" section.
Cisco Unity with Exchange: Alternate Greeting Notices
Alternate greeting notices are a type of message receipt and work as follows: whenever a subscriber leaves or sends a message to a subscriber who has the alternate greeting enabled, Cisco Unity delivers the message and also sends the sender an alternate greeting notice. The notice says:
"The alternate greeting for <subscriber name or ID> is on and will remain on until <expiration date for the greeting>. The message you sent was delivered, but the recipient may not be available to play it."
Alternate greeting notices are disabled by default. Consider enabling them so that all subscribers associated with a server are alerted when a message recipient has the alternate greeting enabled. As long as subscribers can access receipts, they can play notices by phone or view the text from the Cisco Unity Inbox. Alternate greeting notices do not trigger message waiting indicators (MWIs).
Alternate greeting notices are supported only for Cisco Unity Voice Messaging configurations and Cisco Unity systems using Microsoft Exchange 2003 or Exchange 2000.
For more information on how alternate greeting notices work and how to enable them, refer to the "Enabling Alternate Greeting Notices (Cisco Unity Voice Messaging with Microsoft Exchange 2003/2000 Only)" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Cisco Unity with Exchange: Changing How Cisco Unity Handles Messages That Contain Text
You can set up Cisco Unity so that it rejects messages sent to Voice Messaging subscribers if the messages contain text. In this way, you can ensure that Voice Messaging subscribers receive only those messages that they can play in their entirety. When Cisco Unity rejects messages that contain text, Unified Messaging subscribers receive a nondelivery receipt (NDR) and can learn to adjust their messaging habits accordingly.
For more information and a task list for enabling the feature, refer to the "Changing How Cisco Unity Handles Messages That Contain Text (Cisco Unity with Exchange)" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Cisco Unity with Exchange: Disabling Delete Confirmations in the Cisco Unity Inbox
You can use the Advanced Settings Tool to change the registry so that the Cisco Unity Inbox either never asks subscribers to confirm a deletion, or asks them to confirm a deletion only when deleting an item will delete it permanently.
For details on setting up this functionality, refer to Advanced Settings Tool Help. The setting is called Unity Inbox-Confirm Deletes.
Cisco Unity with Exchange: Message Locator Searches Can Include Receipts
You can specify whether to include new and saved receipts in Message Locator searches on the applicable Features page for a subscriber template or an individual subscriber in the Cisco Unity Administrator or by using the Bulk Edit utility. By default, receipts are not included in Message Locator searches.
When subscribers search for messages from a particular subscriber and Message Locator is set to include receipts, the following receipts are included in search results, in addition to voice messages: nondelivery receipts (NDRs), return (read and delivery) receipts, and alternate greeting notices. Note that receipts are included in the search results regardless of whether subscribers can access receipts when they check messages by phone or in the Cisco Unity Inbox. (You can use the Advanced Settings Tool in Tools Depot to prevent subscribers from accessing receipts.)
For a procedure, refer to the "Including Receipts in Message Locator Searches (Cisco Unity with Exchange)" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Customizing the Cisco Unity Conversation: Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password
By default, subscribers are prompted for a password before they can log on to Cisco Unity to check messages or to change personal settings. As a convenience to subscribers, you can specify that Cisco Unity does not prompt them for a password when they access their mailbox from their primary extension or alternate devices.
For more information on how the feature works and how to enable it, refer to the "Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Customizing the Cisco Unity Conversation: Enabling a Post-Greeting Recording
You can use the settings on the applicable Subscribers > Class of Service > Greetings page in the Cisco Unity Administrator to specify whether Cisco Unity plays a recording before allowing callers to leave a message for subscribers assigned to a class of service (COS). You can also indicate whether all callers hear the recording or only unidentified callers. For each COS, you use the Media Master control bar on the page to record what you want callers to hear.
Callers hear the recording immediately after listening to the subscriber greeting, regardless of which personal greeting is enabled for the subscriber. The post-greeting recording also plays after a call handler greeting when the call handler is configured to take a message and the message recipient for the call handler is a subscriber who is assigned to a COS that has the recording enabled. Though callers can press # to skip a subscriber or call handler greeting, callers cannot skip the post-greeting recording.
By default, the feature is disabled for all COSes.
For more information on how the post-greeting recordings work and how to enable them, refer to the "Enabling a Post-Greeting Recording" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Customizing the Cisco Unity Conversation: Disabling the "Record Your Message at the Tone" Prompt
By default, Cisco Unity plays the "Record your message at the tone" prompt after playing a subscriber or call handler greeting. Because some subscribers use the same instruction in their greetings, callers can hear it twice. For this reason, you may want to specify that Cisco Unity does not play the prompt after some or all greetings when callers leave messages for particular subscribers or call handlers in your organization.
For a procedure, refer to the "Disabling the "Record Your Message at the Tone" Prompt" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Customizing the Cisco Unity Conversation: Disabling the "Wait While I Transfer Your Call" Prompt
By default, Cisco Unity plays the "Wait While I Transfer Your Call" prompt when it transfers a call to an extension. Some callers do not like hearing the prompt, and for this reason, you may want to specify that Cisco Unity does not play it.
For a procedure, refer to the "Disabling the "Wait While I Transfer Your Call" Prompt" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Customizing the Cisco Unity Conversation: Specifying That Cisco Unity Play New Messages Automatically
By default, subscribers hear the Main menu after they log on to Cisco Unity. You can customize the conversation so that Cisco Unity plays new messages instead. With the feature enabled, subscribers do not have to press a key to play new messages ("Press 1 for new messages") because Cisco Unity begins playing them automatically.
For more information on how the feature works and how to enable it, refer to the "Specifying That Cisco Unity Play New Messages Automatically" section in the "Cisco Unity System Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Changed Functionality—Release 4.1(1)
This section contains information about changed functionality for Cisco Unity Release 4.1(1) only. Refer to the release notes of the applicable version for information on changed functionality in earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity 4.1(1). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.
Cisco Unity Conversation Changes
In addition to the enhancements described in the "New Functionality—Release 4.1(1)" section, some aspects of the Cisco Unity conversation—default settings and functionality—have changed. The changes are described individually within the "Changed Functionality—Release 4.1(1)" section.
•
•
•
•
•
Cisco Unity Conversation: Menu Allowing Subscribers to Delete Items When They Have an Almost Full or Full Mailbox Clarified and the Keys Assigned to Menu Options Remapped
In previous releases of Cisco Unity, when subscribers who had an almost full or full mailbox logged on to Cisco Unity by phone, Cisco Unity alerted them that their mailbox was almost full or full (as applicable), and then offered the following menu to allow them to delete messages from their Deleted Items folder: "For yes, press 1. For no, press 2."
Although offered as a convenience, the menu was problematic for two reasons:
•
•
To improve usability of the menu, the prompt has been reworded and the keys for the two options have been remapped. The menu now says, "To delete messages, press 7. Return to the main menu, 9."
(Note that the new key mapping for the menu is not configurable via the Custom Key Map utility or the Advanced Settings Tool.)
Cisco Unity Conversation: Messages Are No Longer Marked Urgent Automatically
When subscribers forward or reply to an urgent message by phone, they can choose whether to mark the message as urgent. In previous releases, Cisco Unity automatically marked such messages as urgent.
Cisco Unity Conversation: Phone Menu Response Settings Apply to All Menus
The values that you specify for the Phone Menu Response fields in the Cisco Unity Administrator control all Cisco Unity phone menus heard by outside callers and subscribers—except the Sign-In conversations. (For security reasons, you cannot change the number of times Cisco Unity repeats the menus for the Sign-In conversations.)
In Cisco Unity version 4.0(5), the fields were added to the Cisco Unity Administrator but controlled only a few of the menus heard by outside callers and subscribers. The fields appear on the Conversation pages for subscribers and templates, and on the System > Configuration page of the Cisco Unity Administrator:
•
•
•
The location and default values for the fields in the Cisco Unity Administrator have not changed. However, the default values may differ slightly from the menu response settings that were "hard-coded" for the additional menus now controlled by the phone menu response fields.
For additional information on how to use the phone menu response settings, refer to the Cisco Unity Administrator Help on the Conversation pages for subscribers and templates, and on the System > Configuration page.
Cisco Unity Conversation: Reduced Delays After Multiple Key Presses
In previous releases of Cisco Unity, when subscribers pressed more than one key to navigate to another menu or skip ahead within a task, Cisco Unity was often slow to respond, especially when several keys were pressed in a row. For example, when subscribers pressed ##### to skip and save several messages at once, subscribers experienced a noticeable delay before Cisco Unity responded.
Cisco Unity now responds just as quickly to multiple key presses as it does when subscribers press a single key. To hear the difference, listen to the audio examples in the short presentation Reduced Delays After Multiple Key Presses in Cisco Unity 4.1(1) available on the Training page of the Cisco Unity Tools website at http://www.ciscounitytools.com/TOI_Unity41.htm.
Cisco Unity Conversation: Subscribers Can No Longer Press 4 4 to Reply to All When Only One Recipient Will Receive the Reply
When a message is sent to multiple recipients homed on servers that are connected by SMTP or VPIM networking, the message is sometimes delivered to each recipient as a separate message. In such cases, Cisco Unity no longer allows subscribers to press 4 4 to reply to all recipients, as only the recipient is the sender. When subscribers press 4 4, they will hear, "Invalid selection."
For situations in which there are multiple recipients for subscribers to respond to—as when all the recipients are all homed on the same Cisco Unity server or the recipients are homed on servers that are digitally networked, subscribers can press 4 4 to reply to all.
In previous releases, Cisco Unity allowed subscribers to reply to all even when there was only one recipient, which caused confusion as subscribers assumed that Cisco Unity had delivered their reply to multiple recipients.
Cisco Unity Conversation: Subscribers Can Press ## or 00 to Switch Search Modes
When subscribers use Cisco Unity to address messages, edit private lists, or find messages by phone, they search for a subscriber either by spelling the name or by entering the extension. Subscribers can switch search modes by pressing ## or 00. By default, Cisco Unity responds to either key combination. You do not need to configure it to do so.
If subscribers in your organization are likely to press 00 to switch search modes—perhaps because it is a key combination they used with a former voice messaging system, it is important to consider its limitations. See the "Cisco Unity Conversation: Delay When Subscribers Press 00 to Switch Search Modes" section for details.
Cisco Unity Conversation: "Too Many Matching Names" Prompt Clarified
The prompt that subscribers hear when Cisco Unity tells them that there are too many matches to a partial spelling of a name was reworded for clarity. After subscribers enter the letters of a name that matches more than eight other names in the directory, they hear: "Too many matching names. Enter the next few letters. To start over or enter a new name, press *."
In previous releases, subscribers heard, "Too many matching names. Enter more letters." Some subscribers misinterpreted the prompt, and responded by starting again and entering more letters, rather than by entering additional letters beginning with the next letter in the name. As a result, Cisco Unity reported that no matches were found.
Cisco Unity Administrator and ViewMail for Outlook No Longer Require Manual Update to Server Name in the Media Master When Failover or Failback Occur
Cisco Unity administrators no longer need to ask subscribers to update their server name setting during failover or after failback. Assuming that subscribers had already set up the Media Master to use the phone as a recording or playback device for the Cisco Unity Administrator or for Cisco Unity ViewMail for Microsoft Outlook, they can continue to do so when failover or failback occur without having to manually update the Media Master with the applicable server name.
Note that subscribers still need to use the correct URLs to access the Cisco Unity Administrator on the active server. Additionally, subscribers must use ViewMail version 4.1(1) with Cisco Unity version 4.1(1) for the connection to the server to work automatically during failover and failback.
Subscribers enter their extension and the Cisco Unity server name in order to use the phone as a playback and recording device with the Cisco Unity Administrator and ViewMail. Although the connection works anyway, the server name is not updated in the Phone Record and Playback Settings dialog box of the Media Master during failover and failback.
For an overview of how the Cisco Unity Administrator, ViewMail, and other Cisco Unity applications such as the Status Monitor and the Cisco PCA work when failover or failback occur, refer to the "Effects on Cisco Unity Web Applications When Failover or Failback Occurs" section in the "Cisco Unity Failover Configuration and Administration Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Cisco Unity with Exchange: Exchange 2003/2000 Permissions Can Be Granted at Administrative Group Level
You can delegate Exchange Administrator control to the installation account and delegate Exchange Administrator or Exchange View Only Administrator control to the directory services account at the administrative group level. In previous versions of Cisco Unity, you were required to delegate control to those accounts at the Exchange organization level.
If you have multiple Cisco Unity servers and you want to use Digital Networking, for all administrative groups in which Cisco Unity subscriber mailboxes are homed, you must delegate the following controls:
•
•
Otherwise, Digital Networking is not supported.
Using Cisco Unity Bridge Networking, AMIS Networking, or VPIM Networking is supported only when you delegate control to the installation and directory services accounts at the organization level.
For updated documentation, refer to the Cisco Unity Permissions wizard Help file PWHelpExchange_ENU.htm.
Cisco Unity with Exchange: Message Locator Uses Same Search Mode As Specified for Addressing Messages and Editing Lists
The Message Locator feature respects the search mode preference that subscribers set for addressing messages and editing private lists. (Subscribers use the Cisco Unity Assistant to dictate whether Cisco Unity prompts them to spell the last name then the first name, spell the first name then the last name, or to enter the extension.) In Cisco Unity version 4.0(5), when subscribers used the Message Locator to find messages from another subscriber, the Message Locator prompted them to spell the last name then the first name.
FAQ Available in Cisco Unity Administrator and on Cisco Unity Desktop
An FAQ is available from the navigation bar in the Cisco Unity Administrator and on the desktop of the Cisco Unity server. The FAQ addresses questions often asked by Cisco Unity administrators.
Usability Improved on Subscribers > Subscribers > Account Page in the Cisco Unity Administrator
The following field names on the Subscribers > Subscribers > Account page in the Cisco Unity Administrator were clarified to improve usability:
•
•
•
•
In addition, when an account is locked, read-only information is displayed on the page to explain why. For example, if an account is locked because a Cisco Unity administrator has checked either the Cisco Unity TUI Access Status or the Cisco Unity GUI Access Status check boxes on the page, the message "Account locked by administrator" is displayed to the right of the applicable check box. If an account is locked because someone has exceeded the number of invalid logon attempts specified for the account, the message next to the applicable check box indicates that information.
Finally, presentation of the call handlers list (as applicable), and the general spacing and indentation of fields on the page was improved.
Installation and Upgrade Notes
For instructions on installing a new Cisco Unity 4.1(1) system, refer to the Cisco Unity installation guide that matches the configuration you are installing. Installation guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. (For descriptions of the various installation guides, refer to Use the Installation Guide That Matches the Cisco Unity 4.0(5) or Later Configuration at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/inst/inst405/405list.htm.)
For instructions on upgrading to Cisco Unity 4.1(1), refer to the Cisco Unity Reconfiguration and Upgrade Guide. The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/ex/index.htm.
New and changed content related to version 4.1(1) is available in the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run
Microsoft Knowledge Base article 313807, XADM: Enhancing the Security of Exchange 2000 for the Exchange Domain Servers Group, describes how to obtain and use the Microsoft Exchange 2000 script called EDSLock, which restricts access granted to the Exchange Domain Servers groups in a forest. Running the EDSLock script in a forest that includes a Cisco Unity server will cause Cisco Unity to malfunction.
When you install Cisco Unity after you run the EDSLock script, Cisco Unity works properly because the Cisco Unity Permissions wizard sets the permissions on the message store services account that are necessary to counteract the effects of the EDSLock script on Cisco Unity.
You will need to rerun the Permissions wizard to update the permissions on the message store services account when you:
•
•
•
For more information, refer to the tech tip Cisco Unity Malfunctions After Running Exchange 2000 EDSLock Script at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a00801463f3.shtml. For information on the permissions set by the Cisco Unity Permissions wizard, refer to Permissions wizard Help.
Cisco Unity Phone Conversation System Prompts
System prompts are standard recordings that come with the Cisco Unity system, and they cannot be changed by using the Cisco Unity Administrator, the Cisco Unity Assistant, or the phone conversation. System prompts are played in different combinations in multiple places in the phone conversation. All system prompts are located in the CommServer\Localize\Prompts directory and subdirectories.
Do not delete system prompts, as this can cause system errors.
Customizing system prompts is not supported. All system prompts are automatically deleted and replaced whenever you upgrade Cisco Unity, including maintenance upgrades.
Cisco Unity with Exchange: Setting to Exclude All Receipts Respected
In Cisco Unity version 4.0(3) Service Release 1, you could use the Conversation—Exclude All Receipts from Voice Mail Stack setting in the Advanced Settings Tool to change the Cisco Unity conversation so that nondelivery receipts (NDRs) and return receipts were excluded from the list of messages that Cisco Unity played for subscribers checking messages by phone. After an upgrade to Cisco Unity version 4.0(4) however, the value for the setting was ignored. With Cisco Unity version 4.1(1), the setting is again respected.
Cisco Unity with Exchange: ViewMail for Outlook No Longer Controlled by Class of Service in Cisco Unity Version 4.(x)
When upgrading a Cisco Unity 3.x system to version 4.(x), subscribers are no longer required to have special class-of-service privileges to use Cisco Unity ViewMail for Microsoft Outlook. Any subscriber who has ViewMail installed can use it.
Customized Keypad Mapping Must Be Restored After Upgrading to Cisco Unity 4.1(1) from Cisco Unity 4.0(5)
If you used the Custom Key Map utility to create a custom conversation in Cisco Unity version 4.0(5), your custom key mapping is not preserved during an upgrade to version 4.1(1). To restore your custom key mapping, do the following procedure.
To Restore a Custom Key Map After Upgrading to Cisco Unity 4.1(1)
Step 1
Step 2
Step 3
Example Subscriber Account Is No Longer Created During Installation of Cisco Unity Version 4.0(3) and Later
In earlier versions of Cisco Unity, the Example Subscriber account was created during installation to provide an example configuration for subscriber accounts. Beginning with Cisco Unity version 4.0(3), the Example Subscriber account is no longer created, though it is not deleted when you upgrade from an earlier version of Cisco Unity.
Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter
Diagnostic traces that were set before an upgrade are not preserved and must be reset after the upgrade.
The Intel Dialogic quiet parameter is preserved in an upgrade only if the voice card software is not reinstalled from the Cisco Unity Installation and Configuration Assistant. If the Install Voice Card Software check box is checked in the Cisco Unity Setup program, the quiet parameter will be lost and must be reset after the upgrade.
Upgrade from Cisco Unity 2.x to Version 4.1(1) May Require Upgrade to Version 4.0(4) First
The "Upgrading a Cisco Unity 2.x System to the Shipping Version" chapter of the Cisco Unity Reconfiguration and Upgrade Guide implies that you can upgrade directly from Cisco Unity 2.x to Cisco Unity 4.1(1). However, if you are upgrading from Cisco Unity 2.x and you want to export subscriber data from Cisco Unity 2.x and import it into Cisco Unity 4.x, you must:
1.
Cisco Unity4.0(4) is available on the Cisco Unity Archives download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-archives.
2.
The application that imports data from Cisco Unity version 2.x works correctly only through version 4.0(4).
If you want to upgrade without exporting subscriber data from Cisco Unity 2.x, you can follow the documentation in the "Upgrading a Cisco Unity 2.x System to the Shipping Version" chapter to upgrade directly to Cisco Unity 4.1.
The Cisco Unity Reconfiguration and Upgrade Guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/ex/index.htm.
Upgrade from Cisco Unity 4.0(2) or Earlier to Version 4.1(1) Requires Reactivation of Optional Conversation 1
When you upgrade from Cisco Unity version 4.0(2) or earlier, the standard conversation is automatically activated for all subscribers. Therefore, you will need to reactivate Optional Conversation 1 after an upgrade (including maintenance-release upgrades).
To do so, use either the Conversation settings on the template and subscriber pages in the Cisco Unity Administrator or the Bulk Edit utility to select the conversation style for individual subscribers or for a particular group of subscribers. In releases earlier than Cisco Unity 4.0(3), you could specify only a single conversation style for all subscribers associated with a Cisco Unity server by using the Advanced Settings Tool to change the registry.
For information on specifying this and other conversation settings in the Cisco Unity Administrator, refer to the "Subscriber Template Conversation Settings" section in the "Subscriber Template Settings" chapter and the "Subscriber Conversation Settings" section in the "Subscriber Settings" chapter of the Cisco Unity System Administration Guide, Release 4.0(5). (The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/ex/index.htm.)
For information on specifying this and other conversation settings in the Bulk Edit utility, refer to Bulk Edit Help.
Upgrades from Cisco Unity Versions Earlier Than 2.3(4.104) Are Not Supported
The Cisco Unity Database Export and Database Import utilities, which let you export subscriber and other information from a 2.x system and import it into a 4.0(x) system, do not work on a Cisco Unity system earlier than version 2.3(4.104). You must install Cisco Unity 4.0(x) as a new system, and all Cisco Unity data from the old system is lost.
Limitations and Restrictions
Cisco Unity 4.1(1) Is Available Only in U.S. English
Upgrades to version 4.1(1) from localized versions of Cisco Unity are not supported because version 4.1(1) is available only in U.S. English (ENU). All other languages, including TTY English (ENX), are not available for use with Cisco Unity version 4.1(1).
Cisco Unity Conversation: Delay When Subscribers Press 00 to Switch Search Modes
When subscribers press 00 to switch search modes, they will experience a delay before Cisco Unity responds accordingly. To avoid the delay, subscribers can press ## instead of 00. Alternatively, you can reduce the amount of time that Cisco Unity waits for key presses so that subscribers do not experience the delay.
Reducing the amount of time that Cisco Unity waits for more key presses can eliminate the delay when subscribers press 00 to switch search modes, but the change may adversely affect how subscribers interact with the Cisco Unity conversation when they do other tasks. For this reason, we recommend that you reduce the value specified for the How Long Cisco Unity Waits For Additional Key Presses After Subscriber Has Pressed a Key field (also known as the Interdigit Timeout setting) only for individual subscribers who are likely to use 00, rather than for all subscribers associated with a Cisco Unity server.
The How Long Cisco Unity Waits For Additional Key Presses After Subscriber Has Pressed a Key field is on the Conversation pages for individual subscribers in the Cisco Unity Administrator. By default, Cisco Unity waits 3000 milliseconds for additional key presses before it acts.
Cisco Unity Conversation: Unexpected Behavior in Message Playback Help
When a subscriber presses certain keys as Cisco Unity plays the Message Playback Help menu, Cisco Unity may not behave as the subscriber expects. For example, for the keys assigned to the menu options that offer speed and volume control, allow the subscriber to move forward or back within a message, and to pause playback, Cisco Unity plays the After Message menu. This is by design.
Cisco Unity with Exchange: Private Secure Messaging
For limitations of the private secure messaging feature, refer to the "Limitations of Private Secure Messaging" section of the "Securing Subscriber Messages" chapter in the Cisco Unity Security Guide, Release 4.x.
The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/usg/ex/index.htm. The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/usg/dom/index.htm.
PIMG Integrations Over a WAN That Use the G.729a Codec Must Disable Comfort Noise
When Cisco Unity has a single integration with a circuit-switched phone system through PIMG units over a WAN and you use the G.729a codec for the system, you must disable comfort noise. Otherwise, callers will hear loud comfort noise after pressing a DTMF key or between prompts when recording a message.
Note that when Cisco Unity has a dual phone system integration with Cisco CallManager and with a circuit-switched phone system through PIMG units over a WAN, you must use the G.711 Mu-Law codec for the system. Otherwise, the dual phone system integration will not function correctly.
To Disable Comfort Noise
Step 1
Step 2
Caution
Step 3
Step 4
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Avaudio\Parameters
and double-click the ComfortNoise value in the right pane.Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Replacing Disks in a RAID
For any server in a Cisco Unity system (the Cisco Unity server, a failover server, a Cisco Unity Bridge server, a message store server, or a dedicated DC/GC), Cisco Unity supports only replacing a defective disk in a RAID with a blank disk to repair the RAID. Replacing disks in a RAID for any other reason is not supported.
Caution
System Transfers Not Included in Transfer Call Billing Reports
The Transfer Call Billing reports available in the Cisco Unity Administrator do not contain data on system transfers made by outside callers and subscribers.
Text to Speech Does Not Read Name in the From Field in E-mail
By design, when subscribers listen to their e-mail messages by using the Cisco Unity phone conversation, the text-to-speech (TTS) feature does not read the name in the From field. Thus, if the message is from someone who is not a Cisco Unity subscriber, the Cisco Unity conversation does not indicate who sent the message. When a message is from a Cisco Unity subscriber, the conversation plays the name (if one is recorded) or extension for that subscriber.
The design allows better TTS performance, and has worked as described since Cisco Unity 2.4(6). For more information, refer to caveat CSCdx95644. (If you have an account with Cisco.com, you can use Bug Toolkit to find caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.)
Web Pages That Contain the Media Master Control Bar Do Not Load Properly When Google Desktop Search Is Installed
When Google Desktop Search is installed on a subscriber workstation that uses Windows XP, the pages of the Cisco Personal Communications Assistant (PCA) and the Cisco Unity Administrator do not load properly in the browser.
For more information, refer to the "Web Pages That Contain the Media Master Control Bar Do Not Load Properly When Google Desktop Search Is Installed" section in the "Cisco Unity Troubleshooting Guide" chapter of the Cisco Unity Documentation Addendum, Release 4.1 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity41/add/index.htm.
Windows Application Event Log May Not Display Third-Party Product Name in Start-Up Log Entry
When Cisco Unity starts, an Event log entry is created with the version number of installed third-party software. Cisco Unity provides the product name to supplement the version number in the Event log entry. If support for a new version of a product (for example, a service pack) begins between releases of Cisco Unity, however, the Event log entry will not include the product name of the software. Because the information about the new version of the third-party software does not exist in its database, Cisco Unity cannot add the product name to the Event log entry.
Windows Terminal Services
Using Windows Terminal Services on a Cisco Unity 4.x server for the following functions is not supported:
•
•
•
•
Using Windows Terminal Services on subscriber workstations for the recording and playback of messages by using ViewMail for Outlook is not supported.
Caveats
This section describes Severity 1, 2, and select Severity 3 caveats.
If you have an account with Cisco.com, you can use Bug Toolkit to find more information on the caveats in this section, in addition to caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Note that this section contains caveat information for Cisco Unity Release 4.1(1) only. Refer to the release notes of the applicable version for caveat information for earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Open Caveats—Release 4.1(1)
Table 3 Cisco Unity Release 4.1(1) Open Caveats
CSCdx80773
3
conversations
Unknown callers receive failsafe and identified callers messages disappear.
Symptom: There is inconsistency in the way we handle some errors in the conversations. No NDR is received by subscriber attempting to leave a message for subscriber without an Exchange mailbox. Also, the error logged in the event log states: "This message has the following recipients: {}..."
There is no workaround.
CSCdz78721
3
conversations
Reply to message that is resent by NDR RESEND option fails. Symptom: Replying to a message that was resent from another subscriber through non-delivery receipt's RESEND option via Telephone User Interface fails and Cisco Unity plays failsafe conversations.
Condition: This defect exists in Cisco Unity.
There is no workaround.
CSCea01229
3
core
Conversation base logs 2 event logs for circular reference in handlers. Symptom: We get AvConvMsg_MC error in the event log.
Conditions: If a call handler is pointing to itself, then we log 2 event log errors (10020 and 10016) from AvConvMsg_MC. The second event log error message is for failsafe.
Workaround
1.RunDbwalker utility to find out the problem. And follow the link.
2.Find out call handler from the event log. Make sure that in its after greeting action, it is not pointing to itself.
CSCea62478
3
setup
Configuration Wizard fails on secondary after Exchange migration.
Symptom: Configuration Setup (Unity setup part 2) fails after asking which account to use for the System Administrator (SA). The failure indicated that it: Failed to reassign the installer's account to the current user.
Condition: This was seen with Cisco Unity 3.1(5) configured for failover. The failure only occurred on the Secondary server. Also, the Unity servers were recently reconfigured (migrated) from Exchange 5.5 to Exchange 2000.
Workaround
Open SQL and look in the subscriber's table. Note the SubscriberObjectID of the Installer account. Open the registry and look under HKLM\Software\Active Voice\Commserver Setup\1.0\Properties\InstallerObjectID If the two IDs are the same, then you aren't seeing the same defect. If the two IDs are different, make a backup copy of your registry. Copy the Installer account's SubscriberObjectID in SQL. Paste that entry into the InstallerObjectID field in the registry. Run Configuration Wizard again.
CSCeb29171
3
setup
Unity Install: sysconfig check selects incorrect domain tree.
Condition: Unity 4.0 Installation can fail during Message Store setup in environments where there are multiple AD Domains/Trees, and the first domain/tree is not the domain in which the Unity server has been granted membership in the Exchange Servers Admin group. Symptom: Message store install fails with message that Local Machine is not a member of the Domain Exchange Servers Admin group.
Workaround
Call TAC and request to receive a revised syscheck XML application that skips this check and proceeds with the install.
CSCeb41201
3
statusmonitor
Dom: Cannot restart Unity using Web Status Monitor.
Symptom: After stopping Unity with the Tray Icon or with the Web Status Monitor, Unity will not startup when using the Web Status Monitor or the Tray Icon.
Conditions: This is seen in Cisco Unity 4.0(3) and 4.0(4) with Lotus Domino as the messaging partner. Unity fails to start because AvCsGateway is left started (this is current expected behavior).
Workaround
Open a DOS Command Window. Browse to the \CommServer directory. Right-click on the AvCsTrayStatus icon and select "Exit," and type "kill av*." Open the Services applet and verify that all Unity services are stopped. Go to the Start menu and open Programs->Startup->AvCsTrayStatus Right-click on the AvCsTrayStatus icon and select "Start Unity."
CSCeb44165
3
conversations
SubSignIn conversation should prevent infinite loops.
Symptom: One or more voice ports are locked in a busy state and show SubSignIn state in the status monitor.
Conditions: Occasionally Unity may not receive positive disconnect signaling from the phone system even when the original caller is no longer on the call. In this case the Unity conversation will continue without user input. In most cases, the conversation will eventually reach a hang-up termination point. However this may not happen if a routing rule has been created to direct calls to the SubSignIn conversation. Instead the call will continually be re-routed back to the SubSignIn. Ports stuck in the SubSignIn conversation infinite loop can be reset using the port reset button on the status monitor.
Workaround
Instead of using a Routing Rule, create a Call Handler and assign it the ID of the extension the calls are forwarding from, set transfer to no, set the greeting to blank, and set the action after greeting to go to sign in. This will accomplish the same thing as the routing rule. The first thing callers will hear that are forwarding to this Call Handler is "Please enter your ID" the only difference is that by sending the caller through the call handler, Cisco Unity will keep track of how many times the call loops through the Call Handler, and once the call has looped through the Call Handler 25 times, Cisco Unity will play the Failsafe prompt, log and error to the application event log, and hang up.
CSCeb82281
3
reports
Reports are failing.
Symptom: All Unity reports fail to complete successfully. Information similar to the failure below is seen in the reports diagnostic files. 14:50:38:772 **NOT FORMATTED**,AvDiagnostics_MC,20004,3940,-1,,-1,-1,1,RUNREP,0x80004005 14:50:38:773 (CiscoUnity_RepMgr,20004,-1,-1) [Thread 3940] Error in Report Manager while running report with ReportID:1, during RUNREP, error code 0x80004005
Condition: This problem may occur on Unity 3.x and Unity 4.x
There is no workaround.
CSCec07086
3
pca
CiscoPCA: Page cannot be displayed error after upgrade.
Symptom: After a Cisco Unity upgrade, the CiscoPCA is inaccessible. Users receive an error that the page cannot be displayed.
Condition: This may be seen after Cisco Unity has been upgraded from any version to Cisco Unity 4.0(3).
Workaround
Often the culprit is a failed SSL Certificates publication. This can be verified by launching the IIS Manager window, browsing to the Default Website and selecting its properties. Once the properties window opens, go to the Directory Security tab and select the View Certificate button in the lower option pane. This open a window showing the current site certificate information. An little key icon should be visible in the lower part of the text area close to a sentence that says "You have a private key that corresponds to this certificate." If this does not appear the certificate publication failed. You have to: 1- disable ssl for the jakarta virtual folder; 2- remove the certificate from the Default Website; 3- Delete the certificate request file and any pending request in the Certificate Manager service; 3- restart the w3svc service. and optionally 4- create a new certificate. After installing a new certificate the you can re-apply the SSL requirements on the jakarta virtual folder and restart the w3svc service. If the SSL certificate is not the cause of the issue try this work around: Enter the URL as such, specifying the port: http://<servername>:8080/ciscopca
CSCec24637
3
import
DOH lacks diagnostic required to troubleshoot failures.
Symptom: The DOH lacks diagnostics required to troubleshoot failures when adding Internet and AMIS subscribers. Pop-up error msg is: Unrecognized error 0x8004010F has occurred. The new subscriber was not successfully added. DOH Traces (partial): 20:01:40:693 (CiscoUnity_Doh,32028,Doh,14) [Thread 3748] Thread: 0x00000ea4 Instance: 0x048314a0 CAvDohContainerImpl::Create 20:01:40:708 (CiscoUnity_AlCommon,30007,Doh,0) [Thread 3748] Diagnostic: Thread: 00000ea4 Instance: 04831480 - CAvDohMailUsers::CAvDohContainerImpl::Create Exit 20:01:40:723 (CiscoUnity_AlCommon,30000,AlCommon,10) [Thread 3748] Error in CAvDohMailUsers::CreateNoLogon - CAvDohContainerImpl Failed - File: e:\views\cs_ue4.0.0.280\un_Doh1 \Doh\Src\AvDohMailUsers.cpp Line: 574 Error: 8004010FH Thread: 00000EA4H Instance: 04831480H
Conditions: Unity 4.0.1
There is no workaround.
CSCec36146
3
setup
Message Store Conf Wizard does not populate current containers used.
Symptom: When running the Message Store Configuration Wizard for changing Unity message store or object locations, the location for new User and Distribution List objects may appear with a default "/Users" selection even though other AD containers were previously specified.
Conditions: Unity 3.1 and higher versions integrated with Active Directory.
Workaround
Select the correct container already in use via the Change button on the object creation selection page of the wizard.
CSCec45356
3
core
Unhandled exception handler event log is not useful or accurate.
Symptom: An unhanded exception in Unity will generate an event log entry like the following examples: Event Type: Error Event Source: CiscoUnity_AvCs Event Category: None Event ID: 100 Date: 7/9/2003 Time: 3:37:56 PM User: N/A Computer: SERVERNAME Description: Exception occurred and handled. Contact Cisco Technical Support. File: e:\views\Unity4.0.1.55\un_Conv2\AvConvPhoneHandler\AvConvPHGreetingSvr\AvSPl ayGreeting.cpp at Line: 6397 - Error: 80004005H Call stack: 0x5F81AD8D AvConvPHGreetingSvr.dll: <unknown symbol>
Event Type: Error Event Source: CiscoUnity_AvCs Event Category: None Event ID: 100 Date: 8/19/2003 Time: 1:56:04 PM User: N/A Computer: SERVERNAME Description: Exception occurred and handled. File: e:\views\Unity4.0.1.55\un_SA1\SA\avsadbconn\AvSaDbSession.cpp at Line: 15431 - Error: 80004005H Call stack: 0x5DC067BD AvSaDbConn.dll: <unknown symbol> Exception occurred and handled. Contact Cisco Technical Support. File: e:\views\Unity4.0.2.105\un_car \DominoMonitor\AvDominoMonitorSvr\AvDominoMonitor.cpp at Line: 753 - Error: 80004005H Call stack: 0x5E77AB2D AvDominoMonitorSvr.dll: <unknown symbol>
Conditions: Unknown. These error messages do not reflect the actual point of failure, nor do they report the correct line number.
There is no workaround.
Note that these errors may not be fatal, and may be expected. An example of this would be message store connectivity. If a message store (Exchange or Domino) is taken down for maintenance (or some other known reason) while a subscriber is using Unity (or Unity is performing some background function such as MWI), Unity may have data for the message store session that would become invalid (since the message store is not available). This may cause an exception. In this case, the UMR component would correctly handle the situation and the error message would be an expected and non-fatal side-effect.
CSCec51860
3
core
Unity gives no warning when CommServer dir is write protected. Symptom: The Unity SA, PCA, or almost any other Unity feature, does not work in certain contexts while it may work in other contexts. An attempt is made to gather Unity diagnostics, but the diagnostics are either completely missing/empty or are extremely sparse.
Conditions: Some diagnostics may be present, but others not, depending on the component and the context. Files and directories in the Unity Commserver directory have permissions that cause diagnostic failures in some contexts.
Workaround
In the Properties > Security tab for the Commserver directory, check that Full Control is set for Everyone. Note, however, that the problem may be more complex, in that a single file in the Commserver directory may have specific rights set, and may be marked to not inherit permissions from its parent. To force the permissions for all files, in the Advanced section under the Security tab, select Reset permissions on all child objects and enable propagation of inheritable permissions. Further Problem Description: This defect addresses the issue that Unity itself does not handle error conditions caused by permission issues in the Commserver directory. Defect CSCeh03050 is meant to cover the lack of a document that specifies what permissions are required, and what permission settings are supported, especially for diagnostic/logging features.
CSCec57101
3
utilities
Permissions Wizard does not handle distribution list rights in a multi-domain configuration.
When the Cisco Unity system is configured with Digital Networking, distribution lists must be equally owned by each Cisco Unity server in the network. Because distribution lists are shared in this way, the Directory Services Account for each Cisco Unity server must have rights to each Distribution Group in the entire Active Directory forest. Otherwise, the setup syncher will fail and distribution list administration that uses the Cisco Unity Administrator or the Cisco Unity Bulk Import wizard will fail.
Workaround
Using Active Directory Users and Computers, grant the following rights to the Unity Directory Services account on each organizational unit in the forest that contains a Cisco Unity-enabled distribution group: read properties on group objects, write properties on group objects, and list contents on group objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
CSCed48779
3
conversations
Unity Logon silence perfmon counter displays incorrect values.
Symptom: The Logon silence Perfmon counter may show long delays in Performance monitor while Cisco Unity subscribers access their voice mailbox.
Condition: This occurs in Cisco Unity version 4.X when subscribers access their mailbox. Long delays in logons (greater than 4-5 seconds) are normally attributed to performance degradation in Cisco Unity operation. A Unity server with subscribers whose passwords are expired can also result in a large value for this performance counter. This is not a sign of performance degradation but rather a symptom of this counter measuring the time it takes for subscribers to change passwords.
There is no workaround.
CSCed53009
3
database
On a Lotus Domino system, a subscriber import fails, and the Cisco Unity Administrator returns an error with the error code 80040E2F.
Condition: This occurs on Cisco Unity with IBM Lotus Domino systems, version 4.0(4) and later, when the user being imported has a Domino user name that exceeds 64 characters.
Workaround
Ensure that the Domino user name of the subscriber—including the OU and O chain—is no longer than 64 characters.
CSCed82065
3
licensing
AMIS License shows as both Licensed and Unlicensed.
Symptom: Launch Licensing MMC and you will see AMIS as both Licensed and Unlicensed
Conditions: Purchase AMIS license feature
Workaround
Open the license file itself. Edit the LicAmisIsLicensed and make the letters "Amis" as "AMIS"
CSCed82318
3
exdirconnector
MailboxStoreObjectID out of synch in Unity DB.
Symptom: Subscribers receive the failsafe conversation when trying to retrieve messages. In addition, a few subscribers may not be able to address a message to other subscribers.
Condition: The problem can happen if the SQL database on the Cisco Unity server and the directory are not in synch. Specifically, the MailboxStoreObjectID for the affected subscriber might not be present in the MailboxStore table in the UnityDb database in SQL.
Workaround
Initiate a complete directory synch by doing the following 1. On the Cisco Unity server, browse to the <Cisco Unity Path>\CommServerTechTools directory. 2. Double-click DohPropTest.exe. 3. In the Logon dialog box, click OK without entering a password. 4. In Password Check message box, click Ignore, which starts DohPropTest in read-only mode. 5. Click AD Monitor or Ex55 Monitor, as appropriate for your installation. 6. On the Directory Monitor dialog box, click TotalResync. 7. Exit DohPropTest.
CSCee31747
3
exmessaging
SA: PDLs imported across domains do not contain all members.
Symptom: After importing PDL's from various domains into Unity, some PDL's (depending on the domain they were imported from) are missing members from some other domains.
Conditions: This occurs when importing AD distribution lists from a separate domain (not the domain that Unity is homed in) into Unity.
In my scenario, there is a parent, child, and peer domain, and there are distribution lists in each of the domains. Each distribution list contains users from each of the domains. So, the parent domain PDL contains users from the parent, child and peer domains. And so on. If a PDL is imported from the parent or peer domain into the parent domain Unity, the child domain members don't show up in the imported Unity PDL. The only PDL's that contain the child domain members after import are those imported from the child domain.
Workaround
Create the Public Distribution List with the desired subscribers on the child domain Then import the PDL via SA Web Wait for the GC and DC to replicate and then wait another 15 minutes for Unity to replicate You can force the replication via DohPropTest (AD Monitor | Resync Now) and (GC Monitor | Resync Now)
CSCee34403
3
import
Dom CUBI: SHORT_NAME mean different things based on CUBI mode. Symptom: When using the bulk import tool (CUBI) for Lotus Domino, no users are found when running CUBI in CSV modify mode.
Condition: This can occur with CUBI released with Cisco Unity 4.0(4) and higher when modifying users in Lotus Domino via a CSV file.
Workaround
The SHORT_NAME column in the CSV file should contain user names, not short names. Replace the short name data for each user in the SHORT_NAME column with their Domino user name. For example: SHORT_NAME TUser APerson would become: SHORT_NAME Test User/MyCert A Person/QA/MyCert
CSCee40310
3
exdirconnector
Unity mailbox not created when servers have long computer names. Symptom: When attempting to leave messages failsafe is played. The conversation is complaining that it can not find the Unity mailbox. Looking in AD the Unity mailbox is missing.
Condition: This defect only happens when you have two Unity servers using the same OU for their Unity mailboxes and the server names are the full 15 digits in length allowed and only distinguishable between the two servers by the last digit.
There is no workaround.
CSCee49288
3
core
Failover: FCW fails during secondary with WS03 fresh install.
Symptom: Failover Configuration Wizard on the Secondary fails to complete on Windows 2003 (WS03). A popup is produced and states: `Failed to remove Cisco Unity objects that are associated with the secondary server from the Directory. DETAILED INFORMATION: Method IAvRdbConnection::Initialize(<servername>)returned[0x80048807]:" The wizard produces another popup that states: "After resolving the problem, click Configure to resume configuration or Cancel to exit."
Conditions: Environment - Unity 4.0(4) on a Windows 2003 server with failover
Workarounds
In SQL Server Enterprise Manager delete the (local) (Windows NT) SQL Server Registration. Create a new SQL server registration that is associated with the server.
Workaround #1
1. Open SQL Server Enterprise Manager on the Secondary Server. 2. Expand the tree to the SQL server (it should be labeled as (local) (Windows NT) 3. Right-click and select "Delete SQL Server Registration" 4. Verify that the Server Registration is deleted. 5. Select and right-click SQL Server Group. 6. Select "New SQL Server Registration" 7. Choose the <servername> that is associated with the current server. 8. Select defaults. 9. Repeat for Primary Server. 10. Reboot the Primary and Secondary Server. 11. Rerun Failover Configuration Wizard on the Secondary Server per documentation.
Workaround #2
1.Start>Programs>Microsoft SQL Server>Client Network Utility 2.Under General tab, confirmed that Enables protocols by order included TCP/IP and Named Pipes 3. Under Alias, clicked on Add button, Put the machine name of Secondary Unity into "Server Alias", then click OK Repeat above from Secondary Unity and put the machine name of Primary used in step 3.
For more information, see: http://www.CiscoUnitySupport.com/find.php
CSCee54644
3
exmessaging
Unity doesn't start if store up on partner server but MBX logon fails.
Symptom: Unity fails to start. The following is logged to the application log and then there is a delay of ~12 minutes. Source: CiscoUnity_AvWM Category: Startup Enevt ID: 29000 The server monitor thread has started. (AvCsMgr:2840) For more information, click: http://www.CiscoUnitySupport.com/find.php After the delay several errors will follow including: Source: CiscoUnity_Doh Category: Error Enevt ID: 32013 Doh logon failed due to messaging component logon error: 8004052eH For more information, click: http://www.CiscoUnitySupport.com/find.php Description: Starting with 4.0(3), Unity tries to get a MAL at startup again. During startup AvWM begins to monitor the partner Exchange server. If the partner Exchange server is down Unity will fail to get the MAL but it will be able to get the DOH and continue with the startup process. If the AvWM determines the store on the partner Exchange server is up Unity will try to complete a logon to the Unity_<server name> mailbox. If that logon cannot complete, Unity will fail to get the MAL and DOH which results in Unity failing to start. One possible cause for logons failing is that Exchange is not able to contact a GC. Expected functionality is for Unity to not get the MAL until an actually phone call in the system requires it. By then Unity will be up and taking calls.
Workaround
Ensure that partner Exchange server is able to process MAPI logons.
CSCee57654
3
sa
SA import screen goes blank if DC used by AvDSAD is unavailable.
Symptom: A search for subscribers to import for a specific domain in the SA turns white after ~1 minute and no error message is displayed.
Condition: This defect notes the fact that no error message is displayed although the SA does know an error occurred. Ideally the SA would return the error code and decode it as well. The symptom could occur if the DC stored in the registry for the domain is down. This can be confirmed by turning on the AvSaDbConn traces in the Unity Diagnostic Tool. If the DC for the domain is down the following error will be presented: Error initializing Notes thread: ERROR: spIDCAD->GetNonSubscriberObjectList (bstrDomain bstrFilter bstrSort lMaxValues m_spNewImportSubIter.put() failed: 8007203a Error 8007203a decodes to: The server is not operational. If a different error code is present, the last four digits can be converted to decimal using a calculator. For example 203a converts to 8250. Then from command on the Unity server type net helpmsg <decimal code> and get the decoded message.
Workaround
There is no workaround that will cause the SA to present the admin with an error message. If the DC is down and will continue to be down the value can be updated in the registry using the following steps: 1. Log on to the Cisco Unity server by using an account with rights to modify the registry. 2. Stop the service AvDSAD. 3. Start Regedit. 4. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file. 5. Expand the key HKEY_LOCAL_MACHINE\Software\Active Voice\Directory Connectors\DirSynchAD\1.00 \Domains and expand the domain in question. 6. Change the DefaultDomainController value to the FQDN of a known working DC. 7. Start the service AvDSAD service. 8. Close Regedit. 9. On the Cisco Unity server, browse to the location where Cisco Unity is installed (the default is C:\CommServer), and then browse to the TechTools folder. 10. Run DohPropTest.exe. 11. Type the password and click OK. 12. Click on the AD Monitor button, and then click TotalResynch. 13. Click on the GC Monitor button, and then click TotalResynch. 14. Wait until synchronization has completed.
CSCee58992
3
exmessaging
Unity message submit fails with valid address.
Symptom: The Cisco Unity server may reach a state where it stops accepting valid subscribers when addressing a message. Once Cisco Unity reaches this state, any attempt to address and send a message will fail and the conversation will always respond with, "This message has no address." Condition: This occurs in Cisco Unity 4.0(3) and Cisco Unity 4.0(4) but may appear in earlier versions. The problem occurs an error occurs while addressing a message. The error affects all subsequent conversations when a subscriber addresses a message.
There is no workaround. After the Cisco Unity server reaches this state, it is recommended to restart the server.
CSCee62419
3
exmessaging
Email replies to voicemail are still marked as voice.
Symptom: An email reply to a voicemail received via an email client is marked as a voicemail message. MWI lamp status & notification rule triggers may change based on the status of this email.
Conditions: Unity mailstore is MS Exchange & Unity version is 3.1(x) or 4.0(x)
There is no workaround.
Further Problem Description: Message properties are applied to a voicemail when it is initially delivered. Message properties are not altered by Exchange or Unity when a reply is sent.
CSCee67449
3
utilities
Message delivery fails when a Cisco Unity 4.0(2) or earlier system is upgraded to 4.0(3) or later, and the partner Exchange server is changed from Exchange 2000 to Exchange 2003.
For Cisco Unity 4.0(2) and earlier, when the partner Exchange server is running Exchange 2000, Permissions Wizard adds the message store services account to the Exchange Domain Servers group. Having the message store services account be a member of the Exchange Domain Servers group when the partner Exchange server is running Exchange 2003 causes message delivery to fail.
When upgrading from Exchange 2000 to Exchange 2003, you need to run Permissions Wizard for Cisco Unity to function properly with Exchange 2003 Service Pack 1, and Service Pack 1 is required. It would be useful if Permissions Wizard could detect that the message store services account is a member of the Exchange Domain Servers group, caution the installer that this is the case, and maybe even remove the account from that group automatically.
Workaround
Manually remove the message store services account from the Exchange Domain Servers group, and restart Unity.
CSCee80122
3
core
Unity Tray Icon attempts startup when Unity is already running.
Symptom: Errors appear in the event log like: Source: CiscoUnity_CsServices ID: 1065 AvCsGateway: FindCsComponentsEx failed Unity is running. The Unity tray icon shows Unity is stopped.
Conditions: A request is made to start Unity services from the Tray Icon when Unity is running.
Workaround
Exit the Tray Icon and re-open this via the Start menu, choosing Programs, Startup, AvCsTrayStatus. Further Problem Description: This error denotes an issue with the Tray Status Icon displaying the proper running state of Unity on the server.
CSCee95523
3
core
Unity does not start after DC outage.
Symptom: Unity voicemail is not available after a Domain Controller and Unity both lose power.
Conditions: The Unity server completes Windows startup before the Domain Controller has returned to service.
Workaround
Start Unity services manually from the Unity Tray Icon. Further Problem Description: Unity services depend on authentication of the service account through the domain controller. If this fails on the first attempt, the AvCsGateway service will not attempt the startup operation again once the Domain Controller is available. Other services running with a domain service account will also be affected (such as MSSQLSERVER), but may start automatically once the Domain Controller is back in operation.
CSCef08910
3
telephony
Exception on Shutdown in SipLineRedirector.cpp.
Symptom: On shutdown of Cisco Unity 4.0(4), you will see an error message indicating an exception generated in SipLineRedirector.cpp.
Conditions: This is seen with the PIMG integration and Unity. The error is typically seen when shutting down via the Tray icon. It has been seen in the past with a Sip integration, but is not reproducible in the 4.0(4) release. There will be an error message in the application event log also reporting the exception.
Workaround
Press Ok to exit the error message popup. Unity should be shutdown. Restart Unity. To prevent the exception from occurring, uncheck the Register with Proxy Server box on the Sip Info tab for each PIMG set up in Utim.
CSCef17287
3
setup
MSCW - Partner server selection process is not stateful.
Symptom: The Message Store Configuration Wizard may report that Cisco Unity is not properly installed.
Conditions: Cisco Unity version 4.0(x) or greater offers a selection of mailstores the Unity server can home users on. If an incorrect selection is made or the Unity server has not had the proper message store software installed, the Wizard may display an error and finish without configuring the desired mailstore connection.
Workaround
Ensure the System Administration tools for the desired mailstore have been properly installed and patched. Running the message store configuration wizard a second time will not affect the operation of the Unity server given appropriate privileges are granted to the service accounts and the System Administration software for the mailstore is properly installed.
CSCef17332
3
setup
MSCW - cancelling wizard returns NamedProps error.
Symptom: An error "NamedProps error, Property=ServiceAcctName" is received when the Cancel button is clicked in the Message Store Configuration Wizard.
Conditions: Unity version 4.0(4) is confirmed to display this behavior.
There is no workaround. Cancelling the Message Store Configuration Wizard has no impact on the function of the Unity system. The Message Store Configuration Wizard can be run again if desired with no impact to the configuration of the Unity server.
CSCef23621
3
failover
The failover configuration wizard does not check for share permissions. Stream files (personal greetings, and so on) replication from the primary server to the secondary server fails. Rerunning the failover configuration wizard will fail too.
Conditions: Cisco Unity failover 3.1.5 In a working failover system, if you go in the secondary (or failover) server and changes the share permissions or delete the account that has full control share permissions on \\commserver\streamfiles, the replication for the stream files (personal greetings, and so on) will fail. The failover configuration wizard only checks to see the existence of the shares and not the actual permissions on the shares so rerunning failover configuration wizard will not give FULL Control to the appropriate account for replication to continue.
Workaround
Remove the share \\commserver\streamfiles on the secondary (failover) server and re-run the failover configuration wizard. The failover configuration wizard then recreates the share with the sharing permissions set to the account that we ran the failover configuration wizard with. The folders that have the Cisco Unity message store service account listed as FULL Control on Sharing permissions are \\comserver\streamfiles, \\commserver\snapshot, \\commserver\support, \\commserver\UnityMTA.
CSCef41588
3
exdirconnector
Ex55 Monitor fails to synch SID History.
Symptom: Web client applications, such as the PCA, can fail to authenticate users who have a SID History.
Conditions: Unity partners with Exchange 5.5, and the domain has been upgraded from NT to Windows 2000. Unity subscribers existing from before the domain upgrade will have a SID History in AD, but Exchange 5.5 will only store the original NT SID. Because Unity's Exchange 5.5 directory monitor only synchs with Exchange 5.5 properties, the directory monitor will not fill in the SQL SID history table. When a web client application authenticates one of these old Unity subscribers, it will be checking against the current AD SID, and comparing it to the old NT SID, so it won't be able to authenticate the user.
Workaround
Using SQL Query Analyzer, it should be possible to manually fill in the SID History table in SQL, to let Unity know about the new AD SIDs for the migrated users. This kind of manual modification of a SQL table should only be attempted by someone who is very familiar with Unity's database schema.
CSCef53789
3
setup
MSCW should verify services needed when partner server modified.
Symptom: Unity does not start after configuration of the partner Exchange server from Exchange version 5.5 to Exchange version 2000 or 2003
Conditions: All steps in the documentation for Unity version 4.0 reconfiguration have been followed except for running the Service Configuration Wizard. Documentation of this procedure is located here: http: //www.cisco.com/en/US/products /sw/voicesw/ps2237/products_upgrade_guides_chapter09186a0080205 a8b.html#wp1038664
Workaround
Run the Service Configuration Wizard and select the proper mailstore for Unity. Further Problem Description: This defect documents a particular failure when steps of the reconfiguration task are not followed. This defect is not related to other failures that are not resolved by running the Service Configuration Wizard.
CSCef60341
3
exdirconnector
Unitydb SQL Configuration table lastmodifiedtime value is negative.
Symptom: When running the Unity Failover Configuration Wizard, the following error may be seen: "The SQL snapshot agent failed to complete in a reasonable amount of time. As a result, the Cisco Unity Failover will not work properly. Disable all Cisco Unity replication using the SQL Enterprise Manager and run this wizard again."
Conditions: Unity 4.0(x) versions with Failover. The SQL enterprise manager may display replication errors like "The process could not bulk copy out of table '[dbo].syncobj_xxx]" and "Details: Invalid time format (Source: ODBC SQL Server Driver (ODBC);Error number: 0 The Configuration table may contain negative values for entries in the LastModifiedTime column.
Workaround
Update the Configuration table with the following case-sensitive sql statement (from a command line): osql -E -d UnityDb -Q "update Configuration set LastModifiedTime=NULL" Then, re-run the Failover Configuration Wizard.
CSCef63802
3
core
MWI resynchronization event messages do not audit the requestor.
Symptom: MWI Resynchronization events do not show the source of the request.
Conditions: MWI Resynchronization events are requested by the following: UTIM Resynchronize Now button UTIM scheduled resynchronization Unity Initialization Unity Failover or Failback operations
Workaround
For Unity Initialization or failover related events, see other events related to these operations in the Unity application event log. For UTIM scheduled resynchronization events, the latest resynchronization schedule can be viewed from the UTIM utility.
CSCef73914
4
conversations
A text disclosure statement for private secure messaging exists in SMTP\Outlook voice messages, where the message was a non-encrypted and non-private secure reply to an encrypted private secure message. The TUI must have been used for the initial private secure message and the reply. Conditions: Unity 4.0(5) with Private Secure messaging enabled for given subscribers.
There is no workaround for this issue. Just ignore the text.
CSCef94333
3
core
AvCsMgr stuck in stopping when trying to stop Unity service. When trying to stop the Unity service from the System Tray icon, AvCsMgr service may get stuck at "stopping." This problem may happen with Unity version 4.0(3)SR1.
Workaround
To get around this problem, list the processes running on the server and kill the AvCsMgr service using the process id (pid). To find the process id of AvCsMgr: tlist -s To kill the process: kill -f <process id of AvCsMgr>
CSCeg31816
3
conversations
A private secure reply to a non-private secure message will not have the text disclosure statement viewable via a SMTP e-mail program or MS Outlook. Conditions: Unity 4.0(5) with Private Secure messaging enabled for given subscribers.
There is no workaround for this defect.
However, the attached WAV file that contains the encrypted message will, if played outside of Unity, play a statement notifying that the message is private secure and can only be listened to via the TUI
CSCeg38936
3
conversations
Conv diag not showing filename of customer recorded greetings. Symptom: Conversation traces do not display the filename of the greeting files that were manually recorded. It only shows the names of the prompts. Conditions: Does not affect the functionality of Unity, just impacts serviceability.
There is no workaround.
CSCeg48243
4
conversations
This is a public key replication issue and there are a couple symptoms:
1.
2.
3.
Conditions: Cisco Unity 4.0(5) with Private Secure messaging enabled for some subscribers.
Workaround
Run the certificate creation utility AssignConfCert.exe on each Unity Server in Active Directory including the Exchange server for the Voice Connector.
CSCeg69839
3
conversations
Event log error needs more information. Description: The following event log is logged to the application event log, however it does not provide enough information for an administrator to investigate.
Event Type: Error Event Source: CiscoUnity_ConvSubscriber Event Category: Error Event ID: 119 Date: 2004/12/27 Time: 10:24:18 User: N/A Computer: USUNITY01 Description: An unexpected error has occurred while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMessage::Submit returned [0x8004010f] on line 171 of file H:\views\ESB1_view\un_Conv1\AvConvSubscriber\AvConvSubMsgPlaySvr\AvSSendCopiedMsg.cpp. For more information, click: http://www.CiscoUnitySupport.com/find.php Notes: USUNITY01 - All Cisco Unity Error Events
Conditions: AL: 0x8004010f Source: AL Hexcode: 0x8004010f Symbol: AL_E_NOT_FOUND Description: Something wasn't found, such as an item or property MAPI: 0x8004010f Source: MAPI Hexcode: 0x8004010f Symbol: MAPI_E_NOT_FOUND Description: Object, property, etc. is not found
Workaround
Enable Unity diagnostics.
CSCeg74006
3
sa
SA creates an invalid private list after viewing list's SA page.
Symptom: When running DBWalker to check the Cisco Unity database, the following Warnings are generated: Private List ID=<number> 1381:(warning) Private list has a NULL display name. This can be fixed by selecting a display name for this list on the Private Lists page of this subscriber in the SA 1384:(warning) private list contains no members
Condition: Cisco Unity 4.0(5) and earlier, when using DBWalker to check the Cisco Unity database. These warnings occur if a subscriber owns a private list with no members and/or no display name. This condition can occur if a private list is accessed via the TUI, Cisco Unity Administrator (SA) or Unity Assistant (UA) and no further action taken on it. Workaround
This is not a serious condition. Private list records are created when a list is accessed. To stop the warnings from occurring have the subscriber either update the list display name and/or add members, or have the subscriber delete the list using the Unity Assistant.
CSCeg83763
3
dommessaging
Under certain conditions, Cisco Unity subscribers do not receive a non-delivery receipt (NDR) when a message to a remote VPIM voice messaging system cannot be delivered. This problem has been observed on Cisco Unity with Domino, release 4.0(5), when the Domino server that handles outbound SMTP messages cannot deliver the VPIM message to the remote voice messaging system. Typically, the problem is caused by one or more of the following:
•
•
When the message delivery failure happens, Domino logs the message "Message <messageid#> contains no recipients." to the Domino console window (and Log.nsf) on the Domino server on which the Interop Gateway mail file is located.
Workaround
Determine the cause of the message delivery failure. For more information, refer to the following sections in the "VPIM Networking" chapter of the Networking in Cisco Unity Guide (with IBM Lotus Domino), Release 4.0(5):
•
•
•
•
The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/dom/index.htm.
CSCeg83830
3
dommessaging
The Cisco Unity CsDomInteropGty and AvCsMgr processes show a steady increase of Private Bytes during regular use. This occurs in Cisco Unity 4.0(5) with Domino when using the Interop Gateway to exchange messages with a remote voice messaging system using AMIS, Bridge, or VPIM Networking. The leak rate is linear to the number of messages that the Interop Gateway is processing, and occurs at approximately 250 bytes per message for the CsDomInteropGty service and at approximately 1KB per message for the AvCsMgr service.
Workaround
Restart the Cisco Unity server if the amount of Private Bytes being used by the CsDomInteropGty or AvCsMgr process begins to cause general system performance degradation.
CSCeg90618
3
dommessaging
Cisco Unity Administrators cannot access remote subscriber pages on a digitally networked Cisco Unity server. When they click on a subscriber name, another browser window opens up. The top frame says:
"Object with Alias"
The central frame says:
"Deleted Object: This object has been deleted."
This occurs in Cisco Unity 4.0(5) with Domino. This is seen if the Cisco Unity server has been configured to monitor an address book (or a local replica) that is being used as a Primary or Secondary address book for a Cisco Unity server that is in another Lotus Domino domain.
Workarounds
1.
2.
CSCeh01262
3
utilities
Delivery of incoming IP Fax messages fails when the receipient has an ambiguous alias. The fax message is not picked up from the incoming fax mailbox and the logs show a COM error. When this happens, the service tries to resend the message on the next cycle and fails with the same error in the log.
Condition: The problem is seen on systems using version 2.0.22 of the Unity IP Fax service, Microsoft Exchange as the message store, and any version of Cisco Unity.
There is no workaround.
CSCsa63219
3
conversations
UMR does not respect subscriber time zone settings.
Symptom: The UMR conversation does not respect time zone setting for an individual subscribers when announcing message time stamps. Instead, the time stamps on the messages are always in relation to the time zone of the server Unity is installed on.
Condition: This defect exists in all versions of Unity.
There is no workaround.
CSCsa63226
3
conversations
UMR conversation always plays time stamp before message.
Symptom: The UMR conversation always plays the time stamp for a message before the message. The default for the subscriber conversation is to play the time stamp after the message, but that configurable per subscriber. Expected behavior is for the UMR conversation to play the time stamp as configured for the subscriber.
Condition: This occurs in all versions of Unity.
There is no workaround.
CSCsa63960
3
utilities
The Cisco Unity IP Fax service hangs when trying to process Microsoft Word documents.
Condition: The problem is evident when using Microsoft Word documents with the Cisco Unity IP Fax service. When the document is opened with Wordpad on the Cisco Unity server, the error message "Unable to load graphics conversion filters. Continue with document conversion?" appears.
There is no workaround.
Microsoft Word or Wordviewer is not supported on the Cisco Unity server.
CSCsa65954
3
telephony
Greeting is intermittently played as no audio or hum - one way audio.
Symptom: Cisco Call Manager integration. Occasionally a greeting is heard as blank - one way audio. The lack of audio continues for the length of the greeting. For internal calls, this is heard as a fairly loud hum. For external calls, this is heard as no audio at all. A netmon capture on Unity shows it plays as a hum all the time. While the problem is often heard as no audio, there appears to actually be garbage audio coming out of Unity which may be heard as no audio or a hum depending on any intermediate equipment.
Conditions: Traces indicate Unity incorrectly determines the format capabilities of the output audio device and thus plays the file in the wrong format. The Unity Call Manager TSP is answering the phone so fast that the codec/format of the call is not yet known, and it may default to the wrong format.
Workaround
In the switch INI file for the particular Call Manager integration, include the following setting: [Configuration] DelayBeforeOpening=1 This setting is the number of seconds to pause after answering the call and before playing any audio files. Since the audio format will be setup between Call Manager and the Unity TSP well within one second of the beginning of a call, one second delay is sufficient. At the same time, this will not be noticed by callers. The switch file in use by an integration can be found in the registry in: HKLM\Software\Active Voice\MIU\1.0 \Initialization\Integrations\Integration<#>\Switch Configuration File This file can be found in X:\Commserver\Intlib. For Call Manager, it is usually cisco0002.ini.
CSCsa66528
3
sa
Importing users in saweb, returns the wrong domain results.
Symptom: Importing users and distribution lists from the Unity System Administration Web interface will return incorrect results. When you select one domain name and enter your search criteria, the results will sometimes display the results in the correct domain. Sometimes the results will be displayed in the incorrect domain.
Conditions: You need to have an environment where you are running Unity 4.0.4 SR1. In addition, you have 3 or more Domains from which Unity can search for.
Workaround
To change the value, open DohPropTest, and press the GC Monitor button. Find the ADIDCDomainEnumTimeOut setting, and change it as desired, using the Set button to invoke the change. The units used are milliseconds, so the default value of 1000 is a one second timeout. There are a couple things to note about this approach, though. First, it will have the side effect that SA import searches will take extra time. Second, there is no sure way for now, other than trial and error, to determine just what the optimal value is for the timeout, i.e. a setting that will return all domains reliably every time, while minimizing the delay in searching.
CSCsa66863
3
utilities
Message Store Manager: exception caught - Code: 0x80004005.
Symptom: The message store manager scripts fail with the following error: Could not move message - exception caught - Code: 0x80004005. Method: CScriptMoveMessages::MoveMessages(). [ScriptMoveMessages.cpp::315] MoveMessages() failed - Code: 0x80004005. Method: CScriptMoveMessages::Execute(). [ScriptMoveMessages.cpp::140]
Conditions: Message Store Manager version 1.4.0.32
Workaround
There is no workaround.
CSCsa72187
2
exmessaging
The Cisco Unity AvCsMgr process shows a steady increase of Private Bytes and a stepped increase of Virtual Bytes during regular use.
Condition
This occurs in Cisco Unity 4.0(5) when Exchange 2003 is the mailstore.
Workaround
Restart the Cisco Unity server if the AvCsMgr Private Bytes exceed 500 MB, if the AvCsMgr Virtual Bytes exceed 1.65 GB or if subscribers notice delays in the conversation.
CSCsa72233
4
csbmsgconnector
After a Disaster Recovery Restore (DiRT), there are errors in the event log stating that the Broadcast Messaging mailbox cannot be reached, even though Broadcast messaging functionality is working correctly. Conditions: After a Disaster Recovery Restore of an Unity 4.0(5) or later system.
There is no workaround. Verify that Broadcast Messaging functionality works as expected.
CSCsa74632
3
import
CUBI needs to pull in fax number from AD in a smarter way.
Symptom: CUBI presently accepts only numbers in the fax number field.
Conditions: Using CUBI to do bulk import.
Workaround
Modify the fax # field to all numbers or once imported manually change them to all numbers.
CSCsa74986
3
telephony
MWI requests from Cisco Unity to Cisco CallManager intermittently fail.
This problem occurs when voice messaging ports are registered to the Publisher and phones are registered to a different Subscriber. This problem has been known to occur when Cisco CallManager is under heavy call volume. The root cause of this problem is a defect in Cisco CallManager. Refer to CSCsa73821.
Workaround
If possible, upgrade to a Cisco CallManager version that has the fix for CSCsa73821.
Alternatively, place a comma at the end of the MWI On and MWI Off codes in the UTIM application in Cisco Unity. Note that this workaround will add one second per comma to each MWI request.
CSCsa76767
3
mediamaster
Messages recorded via the Media Master in ViewMail are recorded and stored in the G711 codec—even if this is not the record format is selected for the Cisco Unity server.
There is no workaround.
CSCsa76800
3
domdirconnector
DOM: SA reports an error when launched.
Symptom: When launching the SA it will fail to start and the following error will be displayed: Unrecognized error hr=0x80070057 (E_INVALIDARG) From: global.asa -- Initialize() Please see your system administrator for more details
Conditions: Cisco Unity 4.0(4) for Domino no longer relies on the ShortName field found in the Document Properties of a user's mailfile in the Domino Directory. Now it relies on the FullName. On upgrades or new installs Cisco Unity does not populate the FullName field in the Document properties of a user's mailfile in the Domino directory for the Example Administrator, Example Subscriber - applies to upgrades to 4.0(4) and Unity Messaging account. Should someone modify any of these accounts from in the Domino directory the Alias field in the Subscriber table in SQL will be cleared on the next Domino directory sync cycle
Workaround
Open up the mailfile document of the Example Administrator, Example Subscriber and Unity Messaging and check and see if the ShortName field blank or populated for these accounts. For those accounts that it is blank populate the ShortName field with the same value as the FullName field. In addition verify the following settings for the Unity Messaging account: ObjectType = 1 SubscriberType = 0 IsSubscriber=0 ListInDirectory=0 Undeletable = 1 UID same as Alias if it is not set.
CSCsa77180
3
utilities
The Cisco Unity IP Fax service fails to forward incoming or outgoing fax messages and the following failure appears in the diagnostic log for the fax service:
2005-03-07,16:28:29,Caught exception - Code: 0x800445ed. Method: CIpFaxCdoHelper::ForwardMessage. [IpFaxMessageHelper.cpp::2228] 2005-03-07,16:28:29,ForwardMessage() failed - Code: 0x800445ed. Method: CIpFaxCdoHelper::ForwardCurrentMessage. [IpFaxMessageHelper.cpp::1962] 2005-03-07,16:28:29,ForwardCurrentMessage() failed - Code: 0x800445ed. Method:
Conditions: The problem is seen when using Cisco Unity IPFax version 2.0.0.22, and when the Cisco Unity Fax Exchange mailbox has exceeded the size limit. When an incoming fax message is forwarded to a user, or an outbound fax message is forwarded to the gateway, the message is copied into the Sent Items folder. When the Cisco Unity Fax Exchange mailbox exceeds the size limit, the Cisco Unity Fax Exchange mailbox can not send or receive new messages.
Workarounds
•
•
•
CSCsa79169
2
telephony
Transfers from Cisco Unity 4.x will be dropped if the call is rejected due to lack of available bandwidth, and call waiting is enabled on the destination extension.
This problem occurs with Cisco Unity 4.x and Cisco CallManager 4.x when locations are in use, and call waiting is enabled on the transfer target.
Workaround
Disable the call waiting on the extensions that Cisco Unity needs to transfer calls to.
CSCsa81987
3
reports
After cancelling a Unity report from the Status Monitor, the Status Monitor does not list any reports at all. The Application Log fills up with the following error and reports may not work afterward:
Event Type:Error
Event Source: CiscoUnity_RepDir
Event Category: (62000)
Event ID: 10001
Date: 3/31/2005
Time: 9:44:05 AM
User:N/A
Computer:UNITYSERVER01
Description: REPDIR FATAL ERROR FILEe:\views\cs_ue4.0.3.159\un_Reports\ReportDirector\AvRepDirSvrSvc\AvRepDir.cp p LINE 1715 VALUE 0x80004005
Condition: This problem may occur in Unity 4.1(1) or earlier.
Workaround
If at all possible, don't cancel reports, just allow them to finish. If a report does not complete after an inordinate amount of time, and you must cancel it do the following:
1) Ignore any unexpected behavior when a report has been cancelled.
2) Restart the AvRepDirSvrSvc to clear up any resources that may still be dedicated to the cancelled report.
CSCsa84016
3
dommessaging
Inbound directory messages from the Cisco Unity Bridge server to Cisco Unity get stuck in the UOmni_<ServerName> mail file and the CsBridgeConnector service does not process the messages.
This problem has been observed on Cisco Unity 4.0(5) with Domino using Bridge Networking, when any nodes have been created on the Cisco Unity Bridge server before the corresponding delivery locations have been created on the Cisco Unity bridgehead server.
Workaround
Create the delivery locations on the Cisco Unity bridgehead server that correspond to all of the Octel Nodes that are configured on that Cisco Unity Bridge server where the directory messages are being sent from. For more information on creating delivery locations, refer to the Cisco Unity Bridge Networking Guide (with IBM Lotus Domino), Release 3.0(6), available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/big/dom/index.htm.
Note that after you have created the delivery locations, the CsBridgeConnector service will still not process those messages that were queued in the UOmni_<ServerName> mail file and will instead delete the messages. The directory messages that were deleted will be sent again when the Bridge server sends the next directory message to Cisco Unity. Optionally, you can manually resync the directories on the Cisco Unity Bridge server and the Cisco Unity bridgehead server.
To resync the Cisco Unity subscriber data on the Cisco Unity Bridge:
1.
2.
To resync Octel subscriber data on the Cisco Unity bridgehead:
1.
2.
3.
4.
Note that both of the resync options could take a significant amount of time to complete depending on the number of serial numbers and/or subscribers that need to be synchronized, so it is probably best to do the synchronization after hours so that the impact to the server during higher calling activity periods is kept to a minimum.
CSCsa85814
3
documentation
Unity Documentation for Fax Server Support is incorrect. Symptom: Unity documentation lists the following to be supported Fax Servers in Unity's 3rd Party Fax Configuration: Captaris RightFax, version 6 or later Esker FaxGate, version 7 FAXCOM for Exchange, version 6.19 or later Fenestrae FAXination, version 4 or later Interstar LightningFAX, version 5.5 or later Omtool Fax Sr., version 3 or later Optus FACSys, version 4.5 TopCall, all versions XMedius is NOT listed.
Conditions: Unity 4.0(x)
Workaround
XMedius is written in the latest version (1.0.11) of the 3rd Party Fax Configuration Utility, so it will work, however; this implementation is not TAC supported.
CSCsa86056
3
failover
When a Cisco Unity administrator deletes a subscriber object through the Cisco Unity Administrator on an active secondary server, the administrator receives a dialog stating "Substitute Objects have not yet been configured on this Unity Server. Deleting this subscriber, if it owns or is referenced by Call Handlers, Directory Handlers, or Restriction Tables, could cause database errors. You can either cancel the deletion and configure Substitute Objects or proceed with the deletion and run DBWalker to identify any database errors. Delete the subscriber?"
The administrator does not receive this error if a subscriber is deleted on an active primary server.
This problem occurs fresh installations and upgrades of Cisco Unity 4.0(5) when Cisco Unity is configured for failover. This problem is seen only on the secondary server.
Workarounds
For the first workaround, do the following.
1.
2.
3.
For the second workaround (only if secondary server is inactive), do the following.
1.
2.
3.
4.
5.
6.
7.
CSCsa86402
3
failover
Failover: MWI can get out of synch.
Symptom: Subscriber MWI does not extinguish after checking and saving or deleting new messages.
Conditions: Seen with Cisco Unity 4.0(5) with failover and Microsoft Exchange message store. This is a timing issue with MWI status replication and when failover occurs. When a subscriber receives a new voicemail with the active Primary server, their MWI will light and the System Administration > Subscriber > Messages page will reflect the MWI status as on. If a failover to the Secondary occurs, the MWI status may still be reflected as "Pending On." Thus, when the subscriber calls into Secondary server to check messages and saves/deletes the new message, the MWI status may get out of synch. This will not happen if the Secondary's SA > Subscriber > Messages page is given time to know the MWI status is "On."
Workaround
The MWI will get resynched when a fail back to the Primary occurs. Or, issue an MWI resynch via UTIM or the SA > Subscriber > Messages page.
CSCsa87792
3
core
When an MWI extension is deleted, and MWI Off request is sent to the deleted MWI extension, as well as to any MWI extensions that are still configured. This action can cause MWIs to be out of sync.
This problem occurs only in Cisco Unity 4.0(5).
Workaround
To get MWIs back in sync, from the SA page for the affected subscriber, choose to refresh MWIs.
CSCsa89618
3
core
TRaP will not work with Lotus Notes and Windows XP SP2. Symptom: Subscribers receive an unspecified error when trying to use their telephone to record or playback (TRaP) voicemail messages using the Lotus Notes client with Lotus DUC csClient 1.2.2 installed.
Conditions: This is seen with Cisco Unity 4.x with Lotus Domino integration. This is seen if the subscriber's workstation is installed with Windows XP SP2 and Lotus Notes client with Lotus DUC csClient. This is seen if the subscriber uses their telephone to record and playback voice messages (TRaP).
Workaround
Either uninstall Windows XP SP2 on the subscriber machine, or use the microphone and speakers to record and playback voice messages. TRaP will work if users install Windows XP SP1. Another work around: Modify the following local security option: "DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) Syntax" to allow remote access for ANONYMOUS_LOGON. See CSCef57086. Changing this setting restores the security setting to as it is for WIndows 2000. Further Problem Description: Windows XP SP2 locks down DCOM calls. DCOM is used for TRaP (telephone record and playback) calls made using the Lotus Notes client with DUC csClient installed.
CSCsa96664
3
setup
Third Party Faxes are not presented as faxes.
Symptom: Third Party Faxes are not presented as faxes in the conversation.
Conditions: Exchange is the message store. The Third Party Fax integration is changed after Cisco Unity subscribers have already been added and have used Unity. These subscribers will have their Exchange Cisco Search Folders setup to search for the prior (default) fax integration settings. Therefore, no faxes will be found in the conversation. Workaround
Presently, the only work-around is the manually delete the Cisco Search Folders in Exchange with a low-level tool such as mdbvu32. This is time-consuming, error-prone, and is not recommended. However, since search folders are rebuilt by default after 10 days, if you wait for 10 days the issue should resolve itself on its own.
CSCsa96815
3
import
CUBI: need to set contactrule.rule for TRANSFER_STRING.
Symptom: After using Cisco Unity Bulk Import (CUBI) to modify transfer extensions with the TRANSFER_STRING column of CSV file, the modified transfer extensions do not appear in the SA Subscriber > Call Transfer page for the subscribers as expected.
Condition: This can occur in Cisco Unity 4.0(5) and earlier, if the subscriber(s) being modified were previously configured for the Yes, ring subscriber's extension: option in the Transfer incoming calls to subscriber's phone? section of the Subscriber > Call Transfer page of the SA.
Workaround
First use BulkEdit to modify subscriber transfer extensions such that they are not set for transfer to their primary extension (in other words, so the Yes, ring subscriber at this number: option is selected in the Transfer incoming calls to subscriber's phone? section of the Subscriber > Call Transfer page of the SA.). Then use CUBI to modify the transfer extensions. 1. Run BulkEdit.exe from Cisco Unity Tools Depot. 2. Select the subscribers for which you want to update the transfer extension. 3. On the transfer tab, set Enable transfer to True, check the Append these digits to the left check box and enter 1 in the entry box on that line. 4. Run the process to update the subscribers. 5. Run CUBI, using the options to modify existing subscribers based on a CSV file. In the CSV file, specify the desired transfer extensions in the TRANSFER_STRING column.
CSCsb02180
3
setup
Unity setup allows root drive install.
Symptom: Unity is installed on the root of a drive such as c:\ or d:\ with no commserver directory.
Conditions: All Versions of Unity.
Workaround
Ensure that Unity is installed in a Commserver directory.
CSCsb02305
3
database
SQL database failover replication has no default publication expiration. A Cisco Unity system with failover has larger than expected unitydb and unitydb_log database files. An estimated size for 1000 subscribers would be a unitydb of 100MB.
Conditions: Cisco Unity 4.0(x) with failover.
Workaround
1.
2.
3.
4.
5.
Further Problem Description: MS SQL Server keeps records of conflicts that are resolved during replication in the conflict tables of the Cisco Unity database. If no expiration value is specified, the records of these conflicts may be unnecessarily retained indefinitely. This contributes to increased file sizes that may eventually exceed disk space.
CSCsb06612
3
reports
Subscriber Message Activity Report does not include DTMF / EXT of sender.
Symptom: The Subscriber Message Activity does not log the DTMF ID / extension for the sender.
Conditions: This occurs in all versions of Cisco Unity.
Workaround
There is no direct workaround for the report. However this query could be run again the ReportsDB. Change the SUBDISP value to get the desired user. ----------------------- USE ReportDb SELECT SUBDISP AS Subscriber, DATATIMECR AS Date & Time, EVSRC AS Source, EVTYP AS Action, SENDISP AS Sender Name, SENDTMF AS Sender Phone #, RCVTIME AS 'Receive dTime', NUMNEWMSGS AS 'Numbers of New Messages', DIALOUTRESULT AS 'Dial Out Result' FROM SUBMSG WHERE (SUBDISP = 'Test User') ----------------------- EVTYP Defs 1 = SAVE MESSAGE 2 = DELETE MESSAGE 3 = MARK NEW 4 = NEW MESSAGE 5 = MESSAGE DELETED 6 = MESSAGE READ 7 = VOICE MAIL BOX EMPTY 8 = MWI ON REQUESTED 9 = MWI OFF REQUESTED 10 = MWI ON COMPLETED 11 = MWI OFF COMPLETED 12 = LOGIN 13 = LOGOUT 14 = PAGER DIALOUT REQUEST 15 = PAGER DIALOUT COMPLETE 16 = PHONE DIALOUT REQUEST 17 = PHONE DIALOUT COMPLETE 18 = LIVE REPLY EVSRC Defs 1 = TELEPHONE 2 = OTHERS 3 = TELEPHONE2
CSCsb06626
3
reports
Subscriber Message Active report doesn't log event when MESSAGE READ.
Symptom: The Subscriber Message Active Report does not log an event when a message is read. (EVTYP 6 = MESSAGE READ). Expected behavior is for 6 = MESSAGE READ events to be logged just as 1 = SAVE MESSAGE, 2 = DELETE MESSAGE, 3 = MARK NEW, and 4 = NEW MESSAGE are.
Conditions: This occurs in all version of Cisco Unity.
There is no workaround.
CSCsb06631
3
reports
Subscriber Message Active Report NEW MESSAGE event only on ISM calls.
Symptom: The Subscriber Message Active Report does not log an event if a subscriber sends a message to another subscriber while logged in to their mailbox. A event will only be generate if a subscriber calls another subscriber and is forwarded to voicemail. Expected behavior is that same event will be logged regardless of how you send the message via the TUI. Example: SubscriberA logs in to their own mailbox and sends a message to SubscriberB. There is no event in the subscriber message activity report for SubscriberB. A event will only be generate if SubscriberA calls the phone of SubscriberB and then is forwarded to voicemail. In that case there will be an event showing that SubscriberA level a message if the report for SubscriberB.
Conditions: This occurs in all versions of Cisco Unity.
There is no workaround.
CSCsb07926
3
import
Bulk Import Exchange does not log errors, exchange hostname is missing.
Symptom: When we run the Bulk Import Exchange tool, the user is imported but when we find the user in SA Web, the Exchange server hostname is missing. There are no errors in the NT Application log or the Unity Traces. In addition, when logging into the subscriber account over the phone the caller hears failsafe, and the following error is logged to the event log: An unexpected error has occurred while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMailUser::Get(AVP_MAIL_SERVER) returned [0x8004010f] on line 3734 of file e:\Views\cs_CU4.0.4.221\un_Conv1\Scripted\ ConvSub\SubSignIn.cpp. Importing this user from SA Web works fine.
Conditions: The Exchange Server is set to not allow inheritance. Thus the UnitySirSvc account does not have required permissions to successfully complete the import.
Workaround
To prevent this problem from occurring in the future: Launch Exchange System Manager Browse to the server they have the users' mailbox on. Right click on the server | Properties | Security See that inherit permissions from parent is off (check box at bottom) Either allow inherited permissions, or manually add the UnityDirSvc account and give it full permissions and deny for the Receive As and the Send As permissions. To fix up any users that were impacted by this problem, simply delete the subscriber using the SA, and then reimport the subscriber.
CSCsb08596
3
documentation
Unity Failover Design Guide Bandwidth Requirements are misleading. Symptom: Design document for Unity is misleading when planning for bandwidth
Conditions: Designing network for Unity
Workaround
Contact your Cisco Systems Engineer or Account Team to assist with the design
CSCsb11449
2
failover
Unity gets into a failover/failback loop when Domino is disconnected. Symptom: Unity may not be able to restore Domino connection if Domino gets disconnected from the network for a long duration. When Domino is disconnected from network, Unity may get into a failover/failback loop. This continues after Domino is connected back to the network.
Conditions: This may happen with Unity 4.0(5) in failover configuration. Domino provides the message store.
Workaround
Make sure Domino network connection is up and stable. Restart the inactive/standby Unity server. Failover/failback after server restarts. Restart the other Unity server.
CSCsb13259
3
utilities
MSM does not show up in tools depot.
Symptom: Message Store Manager (MSM) does not show up in the Tools Depot.
Conditions: Seen on new installs and upgrades to Unity 4.0.5
Workaround
If comfortable with Regedit: Regedit HKLM \ Software \ Active Voice \ ToolsDepot\Administration Tools\Message Store Manager Change the value of backend from 3 (space 3) to just 3 (removing the leading space) Restart tools depot -or- Cut / paste the following into notepad and save off as MSMfix.reg. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\ToolsDepot\Administration Tools\Message Store Manager] "Path" = "%CommServer%\\utilities\\MessageStoreManager\\MSMConsole.exe " "HelpFile " = "%CommServer%\\utilities\\MessageStoreManager\\MSMConsoleHelp_ENU.htm " "Icon " = " " "MinUnityVersion " = " " "MaxUnityVersion " = " " "Backend " = "3 " " Double click the MSMFix.reg to install. Restart Tools Depot or go to www.ciscounitytools.com and download the latest version of MSM
CSCsb14876
3
utilities
When using the Cisco Unity IP Fax service to send outbound faxes, the cover sheet may indicate unrendered attachments that were in fact rendered and transmitted.
Workaround
Remove the Unrendered Attachments row from the cover sheet template. Open regedit to read the value of the key at: HKLM\Software\Active Voice\IPFaxRouter\1.0\Coverpage. This key contains the path to the cover page template.
In the template file, remove the row for Unrendered Attachments so that the unrendered attachment display does not appear on the transmitted cover sheets.
CSCsb15978
3
ce
Alternate greeting notices are not received by the message sender as expected when sending voice messages to a public distribution list. Alternate greeting notices are received by the sender if subscribers who have their alternate greetings enabled are addressed individually, but not if a public distribution list which they are a member of is addressed.
Conditions: This can occur in Cisco Unity 4.1(1) and later, with the Alternate Greeting Notices feature enabled. This can occur if the public distribution list was created via the Unity System Administrator or if it was created using Active Directory Users & Computers and the 'Send out-of-office messages to originator' option was not selected.
Workaround
Regardless of how the distribution list was originally created, Active Directory Users & Computers can be used to modify the distribution list so alternate greeting notices are generated. On the properties of the public distribution list, go to the Exchange Advanced tab, select the 'Send out-of-office messages to originator' option, and save the list. Now voice messages sent to public distribution lists will result in alternate greeting notices to the sender. This needs to be done on each public distribution list where this is the desired behavior.
CSCsb16432
3
utilities
EMS Service does not update configuration table.
Symptom: Unity Event Monitor Service (EMS) File / View current log file opens notepad and prompts to create a new file.
Conditions: Unity 4.0(4), EMS 1.2.9
Workaround
This happens when EMS is installed in multiple locations on the system. The admin interface is reading one location and the EMS service is writing to a different location. To correct the condition: 1. uninstall all versions of EMS currently installed and reboot 2. rename any remaining EMS install directories to make the names different 3. install EMS. After ems is installed, open a command prompt and cd to the directory where it is installed. run "csemssvc.exe -service" to install the CsEMSSvc from the current directory. 4. start the CsEMSSvc
CSCsb26256
3
exdirconnector
Scope DL's with over 1000 members fail to sync. Symptom: Users can not be found in a Directory Call Handler in which the Search Scope is set to a Distribution List with more than 1000 members.
Conditions: If a scoped DL contains over 1000 members, or a nested DL within the Scoped DL contains over 1000 members, only the first 1000 members are returned from Active Directory. So you can have a Scoped DL with nested DL's under it as long as there are not more than 1000 members under the member of tab on any distribution list within the Scoped DL all is fine. For example if you had a Scope DL called "Seattle Employees" with only two members which are DL's, say "QA Engineers" and "Development Engineers" and lets say QA Engineers had 1005 members and Development Engineers had 2010 members, only the first 1000 from the "QA Engineers" DL would get synched, and only the first 1000 members from the "Development Engineers" DL would get synched.
Workaround
Limit the members of the DL and the members of any nested DL to 1000 members.
CSCsb28661
3
ducs
DOM - Installing a DUC component may cause wizard to hang. Symptom: When attempting to install the csAdmin component of DUC it may hang when the window with the EULA is displayed. It is possible this can occur when install the csClient and csServer components.
Conditions: When this occurs the Cisco LOGO is not displayed.
Workaround
Start up the taskmgr and kill the setup process. Re-run the install. It maybe necessary to repeat several times before it succeeds.
CSCsb33436
3
telephony
With g.729 the packet preceding the CN packet is not always transmitted.
Symptom: With g.729, the packet immediately preceding the comfort noise packet is not always transmitted. After careful review of audio captures on calls missing some of these preceding packets it does not appear that this causes audio quality problems. However, network monitoring applications such as a sniffer will detect this packet loss and flag it as a problem. IP Phone will also report back to CallManager that packets were lost during the call.
Conditions: This only appears to happen only with g.729 and is known to occur with TSP 7.0(4b) and 8.0(1b). It is likely that all TSP versions have this issue.
Workaround
Disable Unity comfort noise generation. 1. 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 a Cisco Unity failover system, 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. 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. 3. Expand the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Avaudio\Parameters and choose to modify the value ComfortNoise. 4. In the Edit Dword Value window, click Decimal. 5. Set the value to 128. 6. Click OK. 7. Restart the Cisco Unity server. 8. If you are using failover, repeat this procedure to apply the registry setting to secondary server.
CSCsb40372
3
vpimconnector
Inbound VPIM messages to Unity not working.
Symptom: Problem description: Outbound messages (from Unity to Avaya Interchange) work. Inbound messages from Avaya Interchange to Unity, do not. Sniffer traces at the Interchange and at the Unity Exchange partner server shows that Interchange is sending the SMTP packets and Unity Exchange partner server is not responding correctly to the SMTP handshake. The problem is "No inbound SMTP mail flow to Exchange 2000 Server" The Sniffer traces would look like: Unsuccessful: Intuity to Unity 1 from Intuity to Unity: 3159 > SMTP (SYN) 2 from Unity to Intuity: SMTP > 3159 (SYN, ACK) 3 from Intuity to Unity: 3159 > SMTP (ACK) 4 from Unity to Intuity: SMTP > SMTP (FIN, ACK) 5 from Intuity to Unity: 3159 > SMTP (ACK) 6 from Intuity to Unity: Command Quit Successful (Unity to Intuity) 7 from Unity to Intuity: SMTP > 3159 (RST) 8 from Unity to Intuity: 36542 > SMTP (SYN) 9 from Intuity to Unity: SMTP > 36542 (SYN, ACK) 10 from Unity to Intuity: 36542 > SMTP (ACK) 11 from Intuity to Unity: SMTP Response: 220 domain SMTP service ready 12 from Unity to Intuity: Command: EHLO host name.domain 13 from Intuity to Unity: SMTP > 36542 (ACK) 14 from Intuity to Unity: SMTP > Response: 250- host.domain says hello.
Conditions: Unity version = 4.0(4.0) SR 1 Exchange version = Exchange 2000 build: 6249: SP 3 Unity Exchange Partner server IP address changed. VPIM integration with Avaya Interchange.
Workaround
The issue is resolved by configuring the Default SMTP Virtual Server to listen on the new IP Address on the server. You can do that by opening the Exchange System manager, then, browse to the Exchange server, click on protocols, then SMTP, and finally right click on SMTP virtual server and select properties You will notice that the IP for the SMTP virtual server was set to the OLD IP address that they have before they moved the box to the new network. This can setting be set to a fixed IP address or can be "All unassigned." If they had all unassigned, which means take the default IP address and get it from the TCPIP settings of your NIC card, then customer would have not had any issue when they moved the box, but because the IP was fixed to the old (wrong IP), then, SMTP was not working correctly. Once we changed this setting to the new IP address it started working.
CSCsb45457
3
dommessaging
Messages with 0 seconds of audio delivered to Unity MTA folder.
Symptom: Messages with 0 length audio are getting delivered to the UnityMTA folder and then are getting rejected by Domino and are moved to the Failed folder.
Conditions: Unity 4.0(4) SR1 ES58 and 76 DUCS 1.2.2 Build 49 Domino 6.5
Workaround
If the messages are really of 0 length, they are not valid voicemail and can be ignored. Further Problem Description: You will see the following in the UMR sync traces; Entering CNotesFuncts::BuildAttachmentsList(). 12:03:00:964,**,-1,5664,-1,,NotesCommon,1,Leaving CNotesFuncts::BuildAttachmentsList() (0) 12:03:00:965,**,-1,6836,-1,,NotesCommon,2,Begin proxy stub execution on thread ID=5664 12:03:00:964,**,-1,6836,-1,,NotesCommon,2,End proxy stub execution on thread ID=5664 12:03:00:965,AvDiagnostics_MC,1433,6836,-1,,AlCommon,10,TAvDohHasRecordingAttachment,GetNe xtIntroductionNumber,qi(IID_IAvIterator),e:\views\cs_ue4.0.3.159\un_Doh1\Doh\Src\TAvDohHas RecordingAttach.h,123,The operation completed successfully. ,00001AB4H,00DD63B8H 12:03:00:980,AvDiagnostics_MC,692,6836,-1,,UMR,0,HIGH,'CAvMtaMessage::RecordAudioIntoStrea m()',0x00001AB4 12:03:00:981,AvDiagnostics_MC,692,6836,-1,,UMR,1,LOW,'CAvMtaMessage::RecordFileIntoStream( )',0x00001AB4 12:03:00:980,AvDiagnostics_MC,692,6836,-1,,UMR,1,LOW,'CAvMtaStream::Initialize()',0x00001A B4 12:03:00:981,AvDiagnostics_MC,434,6836,-1,,UMR,1,LOW,'CAvMtaStream::Initialize()',0x000000 00,0x00001AB4 12:03:00:980,AvDiagnostics_MC,692,6836,-1,,UMR,1,LOW,'CAvMtaStream::CopyToStream()',0x0000 1AB4 12:03:00:981,AvDiagnostics_MC,434,6836,-1,,UMR,1,LOW,'CAvMtaStream::CopyToStream()',0x0000 0000,0x00001AB4 12:03:00:980,AvDiagnostics_MC,434,6836,-1,,UMR,1,LOW,'CAvMtaMessage::RecordFileIntoStream( )',0x00000000,0x00001AB4 12:03:00:981,AvDiagnostics_MC,434,6836,-1,,UMR,0,HIGH,'CAvMtaMessage::RecordAudioIntoStrea m()',0x00000000,0x00001AB4 12:03:00:980,AvDiagnostics_MC,434,6836,-1,,UMR,0,HIGH,'HRESULT InitMessage()',0x00000000,0x00001AB4 12:03:00:981,**,-1,5664,-1,,NotesCommon,1,Entering CNotesFuncts::CreateDUCSDocument(). 12:03:00:980,**,-1,5664,-1,,NotesCommon,1,Entering CNotesFuncts::InitUCAudioPart(). 12:03:00:981,**,-1,5664,-1,,NotesCommon,10,Attachment filename = C:\DOCUME~1\UnitySVC\LOCALS~1\Temp\AV_A6B7.wav 12:03:00:980,**,-1,5664,-1,,NotesCommon,10,Audio length of attachment is 0 This was indicating the recording was less than a second in length.
CSCsb51339
3
bridgeconnector
Directory updates between Unity and the Bridge fail. Diags need more information.
Symptom: Directory updates from Unity do not make it to the Bridge and visa versa. CSBridgeConnector diags and application event log indicate a failure logging on to and getting the UOmni_<ServerName> mailbox.
Conditions: This can occur if the CsBridgeConnector service can not log onto and get the Inbox for the UOmni_<Servername> mailbox. In this specific case the UOmni_<ServerName> mailbox in SQL was not synched with the AD object.
Workaround
Run \Commserver\Configuration Setup\setup.exe -sync to sync SQL with AD. Once the synch is complete, restart the CsBridgeConnector service. Further Problem Description:
CSCsb56521
3
exdirconnector
AvDSGlobalCatalgue report exception when list of enumerate items is zero. Symptom: Unable to import users via CUBI or the SA
Conditions: The AvDSGlobalCatalogue service should return S_FALSE with an empty variant array when a client calls CAvIDCAD::GetExistingDomains. Then the client can check how many items are in that array or key off of a return of S_FALSE and decide what to tell the user. In this case the client is the SA so it will be necessary to review the SA code to ensure that it can handle this condition. Here are the logs with the AvDSGlobalCatalogue service reporting an exception: 11:39:00:530, -1, -1, -1, -1, LogMgr, -1, diag Diag file opened 2005-08-04 11:39:00 11:39:00:530 (AvDiagnostics_MC,1152,-1,-1) [Thread 2924] LOGMGR OPENNEXTDIAGFILE C: \CommServer\Logs\diag_AvDSGl obalCatalog_20050803_220001.txt C: \CommServer\Logs\diag_AvDSGl obalCatalog_20050804_113900.txt 11:40:50:935 (AvDiagnostics_MC,1686,DSGlobalCatalog,0) [Thread 4484] COM Method CAvIDCAD::GetExistingDomains entered. 11:40:50:936 (AvDiagnostics_MC,1702,DSGlobalCatalog,10) [Thread 4484] spEnumVariant->Next(GC:) CAvIDCAD::GetExistingDomains() ulFetched=0. 11:40:50:935 (**,-1,-1,-1) [Thread 4484] Exception caught e: \Views\cs_CU4.0.4.221\un_Doh2\AvDirMonG lobalCatalog\AvDSGlobalCatalog\AvIDCAD.cpp 961 80004005H Workaround
This is typically indicative of networking issues. The one site that had this issue it turns out they had DNS issues - it is was not possible to contact the Microsoft Exchange server via fully qualified name using the ping command from the Cisco Unity server. Once customer resolved their DNS issues they were able to import users from both the SA and CUBI.
CSCsb56874
3
exdirconnector
Members are dropped from Scoped DL Members table on directory synch.
Symptom: Users may not be found from a Directory Handler which has the search scope set to a Public Distribution List, however the user may have previously been found.
Conditions: If a change was made to the Public Distribution List in AD, users may be dropped from the ScopeDListMembers table in SQL on the next synch cycle.
There is no workaround.
CSCsb57673
3
sa
low level CoS account can create admin level CoS account.
Symptom: A restricted level admin account, that is allowed to create subscriber accounts, can create a higher level account with full system permissions. The restricted account could even create a default admin class of service account.Conditions: This has been seen in a 4.05 system
There is no workaround.
CSCsb57843
3
sa
SA: AvSaDbConn traces do not show properties or Exchange objects.
Symptom: SA Import may return a blank page after some delay. The AvSaDbConn traces of this event may return the following: 11:09:50:219 (AvDiagnostics_MC,766,AvSaDbConn,1) [Thread 2976] HRESULT Success. SUCCESS: pExchangeObject->Get to get a specified property for importing user succeeded: 00000000 in H:\views\ESB1_view\un_SA1\SA\avsadbconn\AvSaDbSession.cpp at line 5427 and/or 11:09:50:218 (AvDiagnostics_MC,765,AvSaDbConn,10) [Thread 2980] HRESULT Failure. ERROR: pExchangeObject->Get to get a specified property for importing user failed: 8000ffff in H:\views\ESB1_view\un_SA1\SA\avsadbconn\AvSaDbSession.cpp at line 5427 There are no details provided on which property of which user succeed or fail.
Conditions: Cisco Unity 4.0(5) or earlier versions.
There is no workaround.
CSCsb62940
3
licensing
Avlic is not logging all micro-traces to the log file.
Symptom: AvLic fails to log all micro traces to the log file.
Conditions: Enable all micro-traces for AvLic
There is no workaround.
CSCsb64195
3
setup
RegOpenKeyEx should display Failure Code.
Symptom: Unity installation fails. The tempu.log file indicates Fail to open the event log application subkey
Conditions: Found in Unity 4.0(5), but it could occur in earlier versions.
There is no workaround.
CSCsb68768
3
setup
Unity install requires Windows Script Host version 5.6.
Symptom: Unity install reports the following error message: CfgCUApp.vbs: Object doesn't support this property or method: 'WScript.Arguments.Named' / Code: 800A01b6
Conditions: The problem is this script, run by the Unity install, requires Windows Script Host 5.6. The Unity install does not enforce a requirement for Windows Script Host 5.6, or give any indication (documentation) that it is required.
Workaround
Install Windows Script Host 5.6.
CSCsb73202
3
conversations
After Error Greeting, Unity disconnects the call instead of recording a message.
Symptom: Unity 4.0(5) with Error Greeting enabled via Tools Depot/Administrative Tools. The after greeting action is set to take a message. When a caller hears a subscriber's greeting and presses an invalid key, they are transferred to the subscriber's error greeting. The caller hears the error greeting and then the prompt "record your message at the tone. When you are finished, hang up or hold for more options." Unity then disconnects the call instead of playing the tone and recording the message.
Condition: This is known to occur in Unity 4.0(5), but may occur in other versions as well.
There is no workaround.
CSCsb73349
3
exmessaging
AST does not consider Failover possibility for the UnityMTA directory. Symptom: UMR messages left in the UnityMTA folder in a failover Unity group may NOT be available to the failover partner if the UnityMTA registry key is changed.
Conditions: If the UnityMTA registry key was changed via the Advanced Setting Tool (AST) or via regedit after the FailoverConfiigWizard was ran AND if the microsoft network share (UnityMTA) was not removed and added to the new folder location with the appropriate use rights may experience this situation.
Workaround
Move the share name and user level permissions to the new directory manually.
CSCsb74272
3
localization
Unity 4.0(5) - French - AvConvHotelFRA033.wav is incorrect. Symptom: when hitting the Hotel greeting AvConvHotelFRA033.wav, it plays: "Pour quitter, appuyez sur la touche dièse, pour joindre la réception, appuyez sur 0. " This translates to: "To Exit press #, to reach the operator press 0. " Actually entering # does not exit. The user has to use *.
Conditions: Unity 4.0(5) with French locale using the French hotel conversation prompt: AvConvHotelENU033.wav
Workaround
Use another prompt that correctly stated to use * to exit. Further Problem Description: The AvConvHotelFRA033.wav plays: "Pour quitter, appuyez sur la touche dièse, pour joindre la réception, appuyez sur 0. " This translates to: "To Exit press #, to reach the operator press 0. " The ENU counterpart: AvConvHotelENU033.wav plays: "To Exit press *, to reach the operator press 0. " This is not consistent and the French version should list * to exit and not #.
CSCsb74344
3
import
Unity 4.0(5) - CUBI import from AD does not allow "(" and ")."
Symptom: Unity 4.0(5) - when trying to import users from AD using CUBI, "(" and ")" are rejectes as invalid characters in the AD display name. When trying to import these users from the SA web, it works fine.
Conditions: users to be imported from AD have "(" and ")" characters in the AD display name.
Workaround
The importspec.xml can be modified to allow "(" and ")" as follows: ------------------------------------------------------------------------ ------------ <Validator validation= "textname64 " > <Validate validation= "string " maxlen= "64 " regex= "([[:alnum:]]|`|~|!|@|#|\$|%|\^|\x26|\-|_|\{|\}|'| |\.|,)* " /> </Validator> By <Validator validation= "textname64 " > <Validate validation= "string " maxlen= "64 " regex= "([[:alnum:]]|`|~|!|@|#|\$|%|\^|\x26|\-|_|\{|\}|\(|\)|'| |\.|,)* " /> </Validator> ------------------------------------------------------------------------ ------------ This line: <Validator validation= "alias64 " > <Validate validation= "string " maxlen= "64 " regex= "([a-z]|[A-Z]|[0-9]|`|~|!|@|#|\$|%|\^|\x26|\-|_|\{|\}|'|\.)* " /> </Validator> by <Validator validation= "alias64 " > <Validate validation= "string " maxlen= "64 " regex= "([a-z]|[A-Z]|[0-9]|`|~|!|@|#|\$|%|\^|\x26|\-|_|\{|\}|\(|\)|'|\.)* " /> </Validator> ------------------------------------------------------------------------ ------------ And: <Field fieldname= "CN " sqlparamtype= "STRING " sqlparam= "@None " > <Validate validation= "string " minlen= "1 " maxlen= "64 " regex= "([[:alnum:]]|\x26|_|'|\-|\.| |/)* " /> </Field> By: <Field fieldname= "CN " sqlparamtype= "STRING " sqlparam= "@None " > <Validate validation= "string " minlen= "1 " maxlen= "64 " regex= "([[:alnum:]]|\x26|_|'|\(|\)|\-|\.| |/)* " /> </Field> ------------------------------------------------------------------------ ------------
CSCsb76049
3
dommessaging
Change Notes Password does not work for Domino version 6.X or higher.
Conditions: Running Change Notes Password Tool does not allow if ran on Domino 6.X or higher.
Workaround
Manually create your own registry key HKLM\SOFTWARE\Lotus\Notes\5.0 and populate it with the same values as the 6.0 key.
CSCsb76575
3
telephony
Failback fails if Primary still has active call from before.
Symptom: When attempting to Failback a Unity failover pair, one or more ports on the primary server become unresponsive. A new call into Unity may CFNA to the secondary and trigger a new failover event.
Conditions: This has been seen when using TSP 8.0(1b). It occurs if Failback is attempted while the primary (inactive) server is still handling a call that was received before the last failover event occurred.
Workaround
Ensure that all ports on the primary (inactive) server are Idle before initiating Failback. If necessary, stop and restart Unity on the primary server before initiating Failback.
CSCsb77196
3
sa
Select Import Existing Exchange User long delay then page not found.
Symptom: While Importing user on SA web page. When you click on the Select Import existing Exchange user on the SA page, The Next screen Which is Exchange user locator screen, First there is long delay about 2 minutes then screen will partially populated with error "Page can not be displayed." and lower half of screen is greyed.
Conditions: Unity 4.0.3 SR1 ES76,ES95 Multiple Unity servers Env, Customer has already applied the fix as per bug CSCee05967 CSCee17914
Workaround
None at this time. Further Problem Description: Workaround has not worked for this issue as mentioned in bugs CSCee05967, CSCee17914 to apply 4.0.3 ES76 and registry key entry.
CSCsb77301
3
conversations
Unity unable to play subscriber sign in conversation.
Cisco Unity will not be able to open a scripted conversation file if the filename case is not as expected, i.e. the script file was named SUBSIGNSCRIPT.CDE when it was expecting SubSignInScript.cde. As Cisco Unity failed to load this conversation script, it played the prompt: 'A system error has occurred. Contact your administrator'. This can occur with other conversation script files as well.
Conditions: Customer had downloaded the Cisco Unity software from CCO and using a 3rd party software burned a CD and so it appears the media that the customer used made all files upper case and also appears that some files were truncated.
Workaround
After changing the name of the file to SubSignScript.cde Cisco Unity was able to load the script file and play the appropriate prompt. A quick check of the other files under the Commserver folder and subfolders revealed a number of other files were also in upper case.
CSCsb94975
3
domdirconnector
Cisco Unity 4.1 install, using Lotus Domino R7 as the partner mail server, fails to create any mailfiles for the corresponding Unity system accounts. Installation of the Interop Gateway for Domino or any of the Interop-related system accounts (AMIS, Bridge) also fails when using R7 as the partner Domino mail server. You may also see errors logged every 5 minutes from CiscoUnity_MALLn stating that it could not find the USBMS_<servername>.nsf mailfile in Domino.
For specific conditions and a detailed workaround, use Bug Toolkit. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. You need to have an account with Cisco.com to use it.
CSCsb95251
3
dommessaging
Cisco Unity subscribers homed on servers other than the Domino partner mail server get the failsafe when they try to send messages using the TUI. Subscribers can log on to their mailboxes, and Cisco Unity allows them to press to 2 to send a message. But after recording a message and pressing # to send it, Cisco Unity plays the failsafe and hangs up; the message is not delivered.
Condition: This problem has been seen in a Domino cluster environment, when the Domino partner mail server service has been shut down (by typing quit in the console), with the following versions:
-- Cisco Unity 4.1(1)
-- Notes 7.0 on the Cisco Unity server
-- Domino 7.0 on the Domino partner mail server
-- DUC for Cisco version 1.2.3
When Cisco Unity attempts to submit a message to mail.box on the Domino partner mail server, Notes returns an error code 0xA02. In this case, Cisco Unity does not attempt to submit the message to mail.box on a Domino cluster mate server, and fails to deliver the message, which in turn, causes the TUI to play the failsafe to the subscriber. The following error from CiscoUnity_MALLn is logged to Event Viewer:
Event ID 14
"The Unity for Domino messaging component was unable to open the mailfile [mail.box] on server [CN=ServerName/O=OrgName]. The Notes subsystem returned the following error: (0xA02) Remote system no longer responding."
Other Symptoms: Subscribers homed on the Domino partner mail server get the failsafe when they attempt to logon to their mailboxes via the TUI. Messages left by callers remain in the UMR (the UnityMTA folder on the Cisco Unity server).
There is no workaround.
Resolved Caveats—Release 4.1(1)
Troubleshooting
Cisco Unity troubleshooting information can be found in the Cisco Unity Troubleshooting Guide, Release 4.0(5). The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/tsg/tsg405/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/tsg/tsg405/ex/index.htm.
Installing a Cisco Unity Demonstration System
A demonstration system is a fully functioning version of Cisco Unity that has the limits noted in the "Limits on a Cisco Unity Demonstration System" section. A demonstration system uses one of two different license files:
•
•
Note
The software for a demonstration system can be ordered on line. The orderable demonstration system is the easiest way to get an entire set of the discs, including third-party software (except Windows 2000 Server). It is available at http://www.cisco.com/order/apollo/configureHome.html. The part number is UNITY4-DEMO-10USR.
We strongly recommend that you install a demonstration system by using the software you receive when you purchase either the full version of Cisco Unity or the orderable demonstration system. Both include the versions of third-party products that Cisco Unity requires to function properly. Installations of demonstration systems frequently fail because the installer is using an unsupported version of third-party software.
To enable the demonstration system, see the applicable section, depending on which license file you are using:
•
•
See also the "Converting a Cisco Unity Demonstration System to a Standard System" section, if applicable.
Limits on a Cisco Unity Demonstration System
Depending on the type of license file you use—Default License File or Time-Limited License File—the Cisco Unity demonstration system will have the limits listed below.
Default License File
•
•
•
–
–
•
•
•
•
Time-Limited License File
The time-limited license enables either Unified Messaging (UM) or Voice Messaging (VM) with the following limitations:
•
–
–
–
–
–
•
–
–
–
–
–
The time-limited license includes the following additional limitations:
•
–
–
•
•
•
•
Enabling a Cisco Unity Demonstration System with the Default License File
The default license file (CiscoUnity40.lic) is automatically copied to the Cisco Unity server during installation.
To Enable a Demonstration System with the Default License File
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Enabling a Cisco Unity Demonstration System with the Time-Limited License File
Do the following three procedures to obtain a time-limited license file and enable a Cisco Unity demonstration system.
To Get the MAC Address of the Cisco Unity Computer
Step 1
Step 2
Step 3
If the server contains more than one NIC, one value will appear for each NIC. Use the value for the primary NIC.
Step 4
To Register and Obtain the License Files
Step 1
Step 2
Step 3
Step 4
To Install License Files
Step 1
Step 2
Step 3
Step 4
Step 5
(When Cisco Unity was registered on Cisco.com, Cisco replied with an e-mail containing an attached file with licenses for Cisco Unity features. The instructions in the e-mail directed that the attached file be saved.)
Step 6
Step 7
If prompted, click Yes to copy the license file to the local system.
Step 8
Step 9
Step 10
Step 11
Step 12
Converting a Cisco Unity Demonstration System to a Standard System
Do the following procedure after you have ordered and received the license file for a standard Cisco Unity system.
Note
To Convert a Demonstration System to a Standard System
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
(When Cisco Unity was registered on Cisco.com, Cisco replied with an e-mail containing an attached file with licenses for Cisco Unity features. The instructions in the e-mail directed that the attached file be saved.)
Step 9
Step 10
If prompted, click Yes to copy the license file to the local system.
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Otherwise, provide additional ports for the Cisco Unity system. The way you provide additional ports depends on the type of phone system integration you have:
Step 18
a.
b.
c.
d.
e.
f.
g.
h.
Step 19
If you are adding languages or the RealSpeak text-to-speech engine, install the feature files and enable the feature(s):
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
Note that if you are using text to speech (TTS) and are using Australian English or New Zealand English as the phone language, also install U.S. English or UK English for the TTS language.
l.
m.
n.
The Cisco Unity Installation and Configuration Assistant displays check marks next to "Install Cisco Unity" and "Install the Cisco Unity License Files," and the Configure the Cisco Unity Services screen appears in the main window.
o.
p.
q.
r.
The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Services," and the Configure the Cisco Unity Message Store screen appears in the main window.
s.
t.
u.
v.
w.
The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Message Store."
x.
y.
z.
Refer to the "Languages" chapter of the Cisco Unity System Administration Guide, Release 4.0(5). (The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/ex/index.htm.)
Put subscribers in a class of service (COS) that includes TTS. Refer to the "Class of Service Settings" chapter of the Cisco Unity System Administration Guide, Release 4.0(5). (The Domino version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/dom/index.htm. The Exchange version of the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/ex/index.htm.)
Cisco Unity Documentation
For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to the Cisco Unity Documentation Guide. The document is shipped with Cisco Unity and is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/about/aboutdoc.htm.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006 Cisco Systems, Inc. All rights reserved.
