 Feedback
|
Table Of Contents
Release Notes for Cisco Unity 4.0(3) Service Release 1
System Requirements, and Supported Hardware and Software
Determining the Cisco Unity Software Version
Installing Service Release 1 on a Cisco Unity 4.0(3) Server
Removing Service Release 1 and Restoring Registry Settings
New and Changed Support—Service Release 1
New and Changed Functionality—Service Release 1
Cisco Unity with Domino: UMR Conversation Is Disabled by Default
Cisco Unity with Exchange: Excluding All Receipts When Subscribers Check Messages by Phone
Cisco Unity with Exchange: Excluding Return Receipts from the Cisco Unity Inbox
Customizing the Subscriber Conversation: Excluding the Summary During Message Replay
Resolved Caveats—Service Release 1
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco Unity 4.0(3) Service Release 1
Published March 11, 2004
These release notes contain installation instructions, new and changed support, new and changed functionality, and resolved caveats for Cisco Unity 4.0(3) Service Release 1.
Cisco Unity 4.0(3) Service Release 1 is a cumulative update for Cisco Unity 4.0(3) systems that includes the engineering specials ES1 through ES58. A Cisco Unity system must be running version 4.0(3) to install this service release.
Cisco Unity software is available on the Cisco Unity Software Download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-40.
Contents
These release notes contain the following sections:
•
System Requirements, and Supported Hardware and Software
•
•
•
•
•
•
•
•
•
System Requirements, and Supported Hardware and Software
The following documents list the most current Cisco Unity requirements and supported hardware and software, and are available on Cisco.com:
•
•
•
Compatibility Matrixes
The following matrixes list the most current software version combinations qualified for use with Cisco Unity and are available on Cisco.com:
•
•
•
Determining the Cisco Unity Software Version
This section contains procedures for determining the Cisco Unity software version in use.
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, including any installed service release, is displayed in the Cisco Unity Build Number field.
To Determine the Cisco Unity Version in Use by Using the AvCsMgr File
Step 1
Step 2
Step 3
Step 4
Downloading Service Release 1
The service release is on the Cisco Unity 4.0(3) SR1 Post-Install CD. The release is also available on the Cisco Unity 4.0 CD Images Software Download page.
To Download Service Release 1
Step 1
Step 2
Step 3
Step 4
Installing Service Release 1 on a Cisco Unity 4.0(3) Server
This section contains a procedure for installing Service Release 1 on a Cisco Unity server that is already running version 4.0(3). The service release may be installed on a multilingual system; however, the installation program is not localized.
If you are installing a new Cisco Unity 4.0(3) server or are upgrading to Cisco Unity 4.0(3), refer to the Cisco Unity Installation Guide, Release 4.0(3). The installation and upgrade instructions alert you when to install Service Release 1. (The Domino version of the guide is at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/inst/inst403/dom/index.htm. The Exchange version of the guide is at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/inst/inst403/ex/index.htm.)
To Install Service Release 1 on a Cisco Unity 4.0(3) Server
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If you downloaded Service Release 1, browse to the directory where you extracted the files.
Step 7
Step 8
Step 9
The Cisco Unity server will restart twice at the end of the installation process. This is expected behavior.
Step 10
Step 11
Note
Removing Service Release 1 and Restoring Registry Settings
This section contains a procedure for removing Service Release 1 from a Cisco Unity server that is running version 4.0(3) and for restoring the pre-service-release registry settings.
Complete the procedure before you try to install Service Release 1 a second time on the same Cisco Unity server.
Caution
To Remove Service Release 1 and Restore Registry Settings on a Cisco Unity 4.0(3) Server
Step 1
Step 2
(If the Cisco Unity icon is not in the taskbar, browse to the CommServer directory, and double-click AvCsTrayStatus.exe.)
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
CommServer\ServiceReleaseBackup\CiscoUnity4.0(3)SR1Step 11
RegisterAndReboot.vbs C:\SRRestore.txtStep 12
Restarting the Cisco Unity server will register the restored DLL files and write to the SRRestore log file in the root directory where Cisco Unity is installed.
Step 13
Caution
Step 14
Step 15
HKEY_LOCAL_MACHINE\Software\Active Voice.Step 16
Step 17
Note that the files and subdirectories in the directory will be properly recreated when a subscriber accesses the Cisco Personal Communications Assistant and Inbox.
Step 18
Step 19
New and Changed Support—Service Release 1
This section contains information on new and changed support in the Cisco Unity 4.0(3) Service Release 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.
For the URLs of Cisco Unity documentation that contains current support information, see the "System Requirements, and Supported Hardware and Software" section.
Cisco Unity Tools Depot
Table 1 lists tools that have been updated or are new in the Tools Depot and that are required or recommended for implementation of feature enhancements included in Service Release 1.
Download the latest version of the tools from the Cisco Unity Tools website at http://www.answermonkey.net/App_pdl_builder_40.htm.
New and Changed Functionality—Service Release 1
This section contains information on new and changed functionality for Cisco Unity 4.0(3) Service Release 1 only. Refer to the release notes of the applicable version for information on new and 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.
Cisco Unity with Domino: UMR Conversation Is Disabled by Default
The Unity Message Repository (UMR) is a feature that helps insulate Cisco Unity from volatility in the external network. The UMR as a feature consists of the following main parts:
•
•
Configuring Domino servers in a cluster is another way in which volatility in the network can be managed. The purpose of Domino clustering is the same as the UMR conversation: to increase the availability of messages. Because subscribers rarely lose access to their mail files in a Domino clustered environment, the UMR conversation is not needed.
In previous versions, Cisco Unity called a Notes API, NSPingServer(), to determine if the Domino message delivery server and the mail servers of message recipients were on line. The NSPingServer() function has proven to be unreliable in a Domino cluster, as described in CSCec15693 and CSCed40506. The pinging of Domino mail servers happens in two places:
•
•
Because the NSPingServer() function is an unreliable way to determine if a mail file is available in a Domino cluster, the following problems have been observed:
•
•
Because Domino clusters provide high availability to messages, rather than finding another way for Cisco Unity to determine if a mail file is available, a registry setting was added that controls whether or not Cisco Unity calls NSPingServer() to ping the mail servers in the above cases. The default is to not ping. This change means that subscribers will never be presented with the UMR conversation. After a subscriber logs on, if Cisco Unity is unable to access the mail file of the subscriber, the failsafe prompt is played and Cisco Unity hangs up. ("This system is temporarily unable to complete your call. Call again later. Goodbye.")
Note that messages from outside callers are still stored in the UnityMTA directory of the Cisco Unity server, and if the attempt to handoff a message to Domino fails, Cisco Unity holds the message in the UnityMTA directory and periodically re-attempts the handoff.
If you are running Domino without clustering, you can enable the UMR conversation. The method in which Cisco Unity checks to see if Domino mail servers are on line works fine when the Domino servers are not clustered. You use the Advanced Settings Tool in Tools Depot to enable the UMR conversation. For details, refer to the Advanced Settings Tool Help. The setting is called Conversation—(Unity Domino only) Enable UMR Conversation.
Cisco Unity with Exchange: Delaying Message Waiting Indication for Messages to Large Distribution Lists
Messages to large distribution lists, such as the All Subscribers list, can cause all ports to be busy when a large number of subscribers call in and listen to a message at the same time. Two new settings in the Public Distribution List Builder tool add a configurable systemwide delay (throttling) for subscriber message waiting indicators when a message is sent to specified distribution lists.
Each throttled message waiting indication (MWI) request is delayed by the specified number of seconds. The total notification time for the message will be approximately equal to the number of queued throttled requests multiplied by the delay time interval.
To Set Up MWI Delay for Messages to Large Distribution Lists
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco Unity with Exchange: Excluding All Receipts When Subscribers Check Messages by Phone
You can use the Advanced Settings Tool to change the Cisco Unity conversation so that when subscribers check messages by phone, Cisco Unity excludes non-delivery receipts (NDRs) and return receipts from the list of messages that it plays for subscribers. You may want to consider the change because when subscribers have receipts with large attachments (100 MB or larger) in their mailboxes (often typical in Unified Messaging configurations), one or both of the following problems may occur:
•
•
The registry change applies systemwide to all subscribers associated with the Cisco Unity server, regardless of whether they use the standard conversation or Optional Conversation 1.
For details on setting up this functionality, refer to the Advanced Settings Tool Help. The setting is called Conversation—Exclude All Receipts From Voice Mail Stack.
Cisco Unity with Exchange: Excluding Return Receipts from the Cisco Unity Inbox
You can use the Advanced Settings Tool to change the registry so that Cisco Unity excludes return receipts from the Cisco Unity Inbox. The change is applied systemwide to all subscribers associated with the Cisco Unity server.
For details on setting up this functionality, refer to the Advanced Settings Tool Help. The setting is called Unity Inbox—Exclude Return Receipts from the Inbox.
Customizing the Subscriber Conversation: Excluding the Summary During Message Replay
You can use the Advanced Settings Tool to change the Cisco Unity conversation so that it replays only the message body when a subscriber replays a voice message. (By default, Cisco Unity replays both the summary and the body of the message.)
The customization affects only how Cisco Unity replays voice messages. The change is applied systemwide to all subscribers associated with the Cisco Unity server, and it affects both the standard conversation and Optional Conversation 1.
For details on setting up this functionality, refer to the Advanced Settings Tool Help. The setting is called Conversations—Do Not Replay Message Summary.
Resolved Caveats—Service Release 1
Table 2 lists resolved caveats in Cisco Unity 4.0(3) Service Release 1 only.
If you have an account with Cisco.com, you can use Bug Toolkit to find more information on the caveats in Table 2, in addition to caveats of any severity for any release. Bug Toolkit is available at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
Refer to the applicable release notes 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.
Cisco Unity Documentation
For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to About Cisco Unity Documentation. 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 on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments 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.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case 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 listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your 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.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation 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.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—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://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
