 Feedback
|
Table Of Contents
Release Notes for Cisco Unity Bridge Release 3.0(2)
System Requirements, and Supported Hardware and Software
Determining the Software Version
Cisco Unity Voice Connector for Microsoft Exchange
Important Information from Earlier Cisco Unity Bridge 3.0(x) Release Notes
Changes to Bridge Networking Option
Downloading the Cisco Unity Bridge Software and Required Service Packs
Upgrading to Cisco Unity Bridge 3.0(2) from 3.0(1)
Upgrading to Cisco Unity Bridge 3.0(2) from 2.x
New and Changed Requirements and Support—Release 3.0(2)
Cisco Security Agent for Cisco Unity Bridge, Version 1.1(1)
Monitoring Software Qualified for Use with the Cisco Unity Bridge
Required Versions of Cisco Unity and the Voice Connector
New and Changed Functionality—Release 3.0(2)
Resolved Caveats—Release 3.0(2)
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco Unity Bridge Release 3.0(2)
Published January 27, 2004
These release notes describe download and upgrade instructions, new and changed requirements and support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Unity Bridge Release 3.0(2).
Access the latest Bridge software upgrades on the Cisco Unity Bridge Software Download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-bridge.
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 Bridge requirements and are available on Cisco.com:
•
•
•
Determining the Software Version
This section contains procedures for determining the version in use for the following software:
•
Cisco Unity Bridge
To Determine the Cisco Unity Bridge Version in Use
Step 1
Step 2
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 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
Important Information from Earlier Cisco Unity Bridge 3.0(x) Release Notes
Changes to Bridge Networking Option
The Bridge Networking option changed significantly in Cisco Unity version 4.0(3) with Bridge 3.0(1) and provides many new features. Refer to the following documentation for details:
•
•
Downloading the Cisco Unity Bridge Software and Required Service Packs
The Bridge software, Microsoft Windows 2000 Server Service Pack 3, Microsoft Internet Explorer 6 Service Pack 1, and MSXML with Service Pack 1—all of which are required on a new Bridge server and for upgrading to Bridge version 3.0(2)—are available for download from the Cisco Software Center website. Use a computer with a high-speed Internet connection.
To Download the Bridge Software and Required Service Packs
Step 1
13 MB for the download file and 20 MB for the extracted files.
1 GB for the download file and for the extracted files.
Note that if you are upgrading from Bridge 3.0(1) to version 3.0(2), you do not need to install any additional service packs or updates, so you do not need to download Cisco Unity Service Packs CD 1.
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
If you are installing the Bridge software for the first time, refer to the Cisco Unity Bridge Installation Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/big/big30/index.htm.
Upgrading to Cisco Unity Bridge 3.0(2) from 3.0(1)
To Upgrade to Cisco Unity Bridge 3.0(2) from Version 3.0(1)
Step 1
Step 2
•
•
The Bridge services will complete the shutdown process when the last in-process message transmission or reception, rather than call, is complete. No additional message transmissions will begin on the in-process calls—either outbound or inbound—once shutdown has been initiated.
Step 3
If you are using the Cisco Unity Bridge CD, insert the disc in the CD-ROM drive, and browse to the Install directory.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Upgrading to Cisco Unity Bridge 3.0(2) from 2.x
Upgrading from Bridge 2.x requires that Cisco Unity be upgraded to version 4.0(3) or later and that the Cisco Unity Voice Connector for Microsoft Exchange 2000 be upgraded to version 11.0(1) or later.
For instructions on upgrading to Bridge version 3.0(2) from Bridge 2.x, refer to the "Upgrading Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm.
New and Changed Requirements and Support—Release 3.0(2)
This section contains information on new and changed support in the Cisco Unity Bridge Release 3.0(2) time frame only. Refer to the release notes of the applicable version for information about new and changed support with earlier versions of the Bridge. Release notes for all versions of the Bridge are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Cisco Security Agent for Cisco Unity Bridge, Version 1.1(1)
Cisco Security Agent for Cisco Unity Bridge version 1.1(1) is qualified for use with Cisco Unity Bridge 3.0(x). The application combines host intrusion detection and prevention, malicious mobile code protection, and operating system integrity assurance.
For requirements and other information on using Cisco Security Agent for Cisco Unity Bridge, refer to Release Notes for Cisco Security Agent for Cisco Unity Bridge, Release 1.1(1) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bsecagnt/bsa111rn.htm.
For information on the full Cisco Security Agent product, refer to the product website at http://www.cisco.com/en/US/products/sw/secursw/ps5057/index.html.
Monitoring Software Qualified for Use with the Cisco Unity Bridge
The following monitoring software has been qualified for optional use with Cisco Unity Bridge 3.0(x):
•
•
For the most current list of all supported monitoring software—including software qualified since the release of Cisco Unity Bridge version 3.0(2)—refer to the "Supported Monitoring Software" section of Cisco Unity Bridge 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/sysreq/30bsysrq.htm.
Required Versions of Cisco Unity and the Voice Connector
Bridge version 3.0(2) is supported only with Cisco Unity 4.0(3) and later and Cisco Unity Voice Connector for Microsoft Exchange 11.0(1) and later. In installations with multiple Cisco Unity servers, all the servers must be upgraded to Cisco Unity 4.0(3) or later.
Caution
New and Changed Functionality—Release 3.0(2)
There is no new or changed functionality in Cisco Unity Bridge 3.0(2). See the "Resolved Caveats—Release 3.0(2)" section for information on the software fixes in the release.
Installation Notes
For detailed information on installing the Cisco Unity Bridge, refer to the Cisco Unity Bridge Installation Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/big/big30/index.htm.
For detailed information on configuring Bridge Networking, refer to the Cisco Unity Bridge Networking Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm.
Limitations and Restrictions
Refer to the "Notable Behavior" section in the "About Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm.
Caveats
If you have an account with Cisco.com, you can use Bug Toolkit to find more information on the caveat in this section, in addition to caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
Note that this section contains caveat information for Cisco Unity Bridge Release 3.0(2) only. Refer to the release notes of the applicable version for caveat information for earlier versions of the Bridge. Release notes for all versions of the Bridge are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Open Caveats—Release 3.0(2)
Resolved Caveats—Release 3.0(2)
Documentation Updates
Omissions
This section lists new and additional information that is not included in the current Cisco Unity Bridge documentation. The new and additional information will be incorporated in a future documentation release, or as otherwise noted.
Adding the Serial Number and Mailbox ID to Existing Cisco Unity Subscriber Accounts: Cisco Unity Bridge Networking Guide, Release 3.0
The following note should appear in the "Adding the Serial Number and Mailbox ID to Existing Cisco Unity Subscriber Accounts" of the "Setting Up Cisco Unity and the Bridge for Networking" chapter and the "Adding the Serial Number and Mailbox ID to Cisco Unity Subscriber Accounts" section of the "Upgrading Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide, Release 3.0:
Note
Except for the omitted note, the sections in the Cisco Unity Bridge Networking Guide that contain steps for running Subscriber Information Dump and the Cisco Unity Bulk Import wizard to add the serial number and mailbox ID to existing subscriber accounts are correct and complete.
Bug Toolkit is available at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If the defect remains open in later versions of Cisco Unity, the note will be added to the applicable version of the Cisco Unity Bridge Networking Guide.
Pushing Octel Node Directory Information from the Bridge to Cisco Unity: Cisco Unity Bridge Networking Guide, Release 3.0
The following information should appear in the "About Bridge Networking"chapter of the Cisco Unity Bridge Networking Guide, Release 3.0:
When an Octel node directory entry is created on the Bridge server, the Bridge sends a vCard containing the name, recorded voice name, and mailbox number of the directory entry to the Cisco Unity bridgehead server so that a corresponding Bridge subscriber can be created. In this way, the Octel node directories on the Bridge server and the Cisco Unity directory are automatically kept in sync. If needed, you can force the Bridge to resend the existing Octel node directory information to the Cisco Unity bridgehead server if some error has occurred that caused the directories to become out of sync.
Note that the following procedure applies only to Cisco Unity 4.0(3) and later.
To Push Octel Node Directory Information from the Bridge to the Cisco Unity 4.0(3) Bridgehead Server
Step 1
Step 2
Step 3
Step 4
Note that the preceding procedure is used to send existing Octel node directory entries from the Bridge to Cisco Unity. If instead you want the Bridge to retrieve new Octel subscriber information from remote Octel servers that does not yet exist on the Bridge, or if you want to have the Bridge re-retrieve directory information from the Octel servers for existing entries, use the MBUpload.exe utility on the Bridge server.
For information on using MBUpload.exe, refer to the "Using the Cisco Unity Bridge Mailbox Import Tool to Create Permanent Directory Entries" in the "Setting Up Cisco Unity and the Bridge for Networking"chapter in the Cisco Unity Bridge Networking Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm.
The Network > Bridge Options > Synchronization Options page in the Cisco Unity Administrator of the Cisco Unity bridgehead server provides a mechanism to force a full synchronization of Cisco Unity subscriber data with the subscriber directory on the selected Bridge server(s).
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.
