![]() |
Table Of Contents
Release Notes for Cisco Unity Connection Releases 7.1(2), 7.1(2a), and 7.1(2b)
For Cisco Unity Connection in Cisco Unified CMBE
Determining the Software Version
Cisco Personal Communications Assistant
For Cisco Unified Communications Manager Business Edition
New and Changed Requirements and Support—Release 7.1(2)
Additional Languages for Cisco Unity Connection Components
Calendar Integration with Exchange 2007 Server Is No Longer Supported
Cisco Unity Connection Release 7.1(2b)
Cisco Unity Connection Release 7.1(2a)
COBRAS Support for Migrating from Cisco Unity for Domino
Fax Support for VPIM Networking with Cisco Unity Express and Cisco Unified Messaging Gateway
For Cisco Unity Connection in Cisco Unified CMBE
Selected Servers Require Replacement Hard Disks or Additional Memory for Some Configurations
Software Qualified for Use with Cisco Unity Connection on User Workstations
Single Number to Receive Both Voice Calls and Faxes
Support for Up to 200 Partitions and 200 Search Spaces
Support for 24 Voice Messaging Ports (Connection in Cisco Unified CMBE)
Utility Updates on the Cisco Unity Tools Website
You Cannot Upgrade from Connection 2.1(4) to 7.1(2) or 7.1(2a) or 7.1(2b)
New Functionality—Release 7.1(2)
Deactivating Message Notifications
Port and Phone System Conditions in Routing Rules for Forwarded Calls
Relaying Copies of Messages to an External Account
Repeat Notification Option for Pager Devices
Wizard Available for Creating Wallet Cards of Custom Conversations
Changed Functionality—Release 7.1(2)
Cisco Unity Connection Conversation Changes
Speed and Volume Changes are Saved
Voice-Recognition Conversation Uses Same Keypad Mappings as Specified Touchtone Conversation
Installation and Upgrade Information
Information for Cisco Unified Communications Manager Business Edition Customers
Installing Cisco Unity Connection for the First Time
Supported Cisco Unity Connection Upgrades
Upgrading from Cisco Unity Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version
Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1
Installation and Upgrade Notes
Installing Additional Cisco Unity Connection Languages
License Tag Required to Use the U.S. English Conversation and Personal Call Transfer Rules
Connection IMAP Server Service Should Not Be Stopped or Disabled For An Extended Period of Time
Connection Cannot Be Installed or Operated in IPv6 or Dual-Stack (IPv4 and IPv6) Networks
In Connection Cluster, Changed License Data on One Server Does Not Replicate to Other Server
Media Master Cannot Open WAV Files Saved on a Workstation in G.729a Format
ViewMail Limitations Regarding Secure Messages
Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Traps and Informs
Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Services
Obtaining Documentation and Submitting a Service Request
Cisco Product Security Overview
Release Notes for Cisco Unity Connection Releases 7.1(2), 7.1(2a), and 7.1(2b)
Revised June 17, 2013 (Originally published May 29, 2009)These release notes contain information on downloading software, new and changed support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Unity Connection Releases 7.1(2), 7.1(2a), and 7.1(2b), and for Connection in Cisco Unified Communications Manager Business Edition (CMBE) Releases 7.1(2a) and 7.1(2b).
********************************************************************************************************************************************************
Cisco Unity Connection 7.1(2b) contains fixes and changes to the operating system and/or Cisco Unified Communications Manager 7.1(2) application components, including components shared by Connection and Cisco Unified CM.
Cisco Unity Connection 7.1(2a) contained one resolved caveat (CSCta09513) that affected upgrades from Connection versions 7.0 and 2.1(2) and later to version 7.1(2). Nothing else was different.
Note the following information:
•
Throughout this document, references to 7.1(2) also apply to 7.1(2a) and 7.1(2b).
•
Anything documented as compatible with Connection 7.1(2)—for example, versions and tools, and other Cisco products—are equally compatible with 7.1(2a) and 7.1(2b).
•
Follow the Connection documentation regarding any 7.1(2) engineering specials (ESes). You use the same ESes with 7.1(2a) and 7.1(2b).
•
For information on determining whether 7.1(2) or 7.1(2a) or 7.1(2b) is installed, see the "Determining the Software Version" section.
•
For more information, see the "Cisco Unity Connection Release 7.1(2b)" section.
•
For more information, see the "Cisco Unity Connection Release 7.1(2a)" section.
********************************************************************************************************************************************************
Note
Cisco Unity Connection is a Linux-based solution. It is available in two configurations—Cisco Unity Connection, and Cisco Unified Communications Manager Business Edition, in which Connection is preloaded on the same platform with Cisco Unified Communications Manager. These release notes contain information for both configurations.
Note
Items in release notes may be added, or revised to correct or clarify information after the initial publication date (the date the software was released). When an item has been changed, the phrase "Added <date>" or "Revised <date>" is included in the text of an item.
Contents
•
New and Changed Requirements and Support—Release 7.1(2)
•
New Functionality—Release 7.1(2)
•
Changed Functionality—Release 7.1(2)
•
Installation and Upgrade Information
•
Obtaining Documentation and Submitting a Service Request
•
Cisco Product Security Overview
System Requirements
For Cisco Unity Connection
System Requirements for Cisco Unity Connection Release 7.x contains the most current Connection requirements. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.
For Cisco Unity Connection in Cisco Unified CMBE
System Requirements for Cisco Unity Connection in Cisco Unified CMBE Release 7.x contains the most current Connection requirements. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucmbesysreqs.html.
Compatibility Information
The following documents list the most current version combinations qualified for use with Cisco Unity Connection, and with Connection in Cisco Unified CMBE (where applicable):
•
Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations
•
SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express
•
SIP Trunk Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express
The documents are available on Cisco.com at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.
Determining the Software Version
This section contains procedures for determining the version in use for the following software:
•
Cisco Personal Communications Assistant
Cisco Unity Connection
Revised September 9, 2009
To Determine the Cisco Unity Connection Version by Using Cisco Unity Connection Administration
Step 1
In Cisco Unity Connection Administration, in the upper-right corner below the Navigation list, click About.
The Connection version is displayed below "Cisco Unity Connection Administration." If the version number is:
•
7.1.2.10000-16, Connection 7.1(2) is installed.
•
7.1.2.20000-2, Connection 7.1(2a) is installed.
•
7.1.2.30000-3, Connection 7.1(2b) is installed.
To Determine the Cisco Unity Connection Version by Using the Command-Line Interface
Step 1
Start a command-line interface (CLI) session. For more information, see the Cisco Unified Communications Operating System Administration Help.
Step 2
Run the show cuc version command.
If the version number is:
•
7.1.2.10000-16, Connection 7.1(2) is installed.
•
7.1.2.20000-2, Connection 7.1(2a) is installed.
•
7.1.2.30000-3, Connection 7.1(2b) is installed.
Cisco Personal Communications Assistant
To Determine the Cisco Personal Communications Assistant (PCA) Version
Step 1
Log on to the Cisco PCA.
Step 2
On the Cisco PCA Home page, click About in the upper right corner. (The link is available on every web tool page.)
Step 3
The Cisco Unity Connection version is displayed. The Cisco PCA version is the same as the Connection version.
Related Documentation
For Cisco Unity Connection
For descriptions and URLs of Cisco Unity Connection documentation on Cisco.com, refer to the Documentation Guide for Cisco Unity Connection Release 7.x. The document is shipped with Connection and is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/roadmap/7xcucdg.html.
For Cisco Unified Communications Manager Business Edition
For descriptions and URLs of Cisco Unified Communications Manager Business Edition documentation on Cisco.com, refer to the Cisco Unified Communications Manager Business Edition Documentation Guide. The document is shipped with Cisco Unified CMBE and is available at http://www.cisco.com/en/US/products/ps7273/products_documentation_roadmaps_list.html.
Note
The documentation links on Cisco.com for some Cisco Unity Connection in Cisco Unified CMBE 7.x versions go to documents that are labeled for Cisco Unity Connection Release 7.x. Despite the version label, all content in the following guides applies to both Connection configurations: Administration Guide for Cisco Unity Connection Serviceability, Interface Reference Guide, System Administration Guide, Troubleshooting Guide, User Moves, Adds, and Changes Guide, and the User Workstation Setup Guide.
New and Changed Requirements and Support—Release 7.1(2)
This section contains information about new and changed requirements and support in the 7.1(2) release 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 Connection.
Release notes for all versions of Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.
Additional Languages for Cisco Unity Connection Components
This section lists new languages in which Cisco Unity Connection components are available.
For a complete list of languages, refer to the "Available Languages for Cisco Unity Connection Components" section of the applicable System Requirements:
•
System Requirements for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.
•
System Requirements for Cisco Unity Connection in Cisco Unified CMBE Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucmbesysreqs.html.
(For a list of numeric and alphabetic language codes, refer to the "Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection" section of the 7.x System Requirements.)
Cisco Personal Communications Assistant (PCA)
Czech, Hungarian, Polish, Portuguese-Europe, Turkish
Cisco Personal Communications Assistant (PCA) Help
Czech, Hungarian, Polish, Turkish
Cisco Unity Connection ViewMail for IBM Lotus Notes
Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish
Cisco Unity Connection ViewMail for IBM Lotus Notes Help
Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish
Cisco Unity Connection ViewMail for Microsoft Outlook
Arabic-Saudi Arabia, Czech, Hungarian, Polish, Portuguese-Europe, Turkish
Cisco Unity Connection ViewMail for Microsoft Outlook Help
Arabic-Saudi Arabia, Czech, Hungarian, Polish, Turkish
System prompts
Czech, Hungarian, Polish, Portuguese-Europe, Turkish
Text-to-speech engine
Polish, Portuguese-Europe
Calendar Integration with Exchange 2007 Server Is No Longer Supported
Added July 9, 2010A calendar integration with Exchange 2007 Server is no longer supported in Cisco Unity Connection 7.1(2), 7.1(2a), and 7.1(2b).
The "Creating a Calendar Integration with Exchange 2007" section in the "Creating Calendar Integrations" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x (at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html) incorrectly indicates that calendar integrations with Exchange 2007 Server are supported.
Note however that contact and text to speech integrations are still supported with Exchange 2007 Server.
Cisco Unity Connection Release 7.1(2b)
Added September 9, 2009
Release 7.1(2b) contains fixes and changes to the operating system and/or Cisco Unified Communications Manager 7.1(2) application components, including components shared by Connection and Cisco Unified CM.
Cisco Unity Connection Release 7.1(2a)
Revised September 9, 2009
Release 7.1(2a) contained an update to fix CSCta09513.
Cisco Unity Connection 7.1(2) DVD 1 was never released; the DVD 1 that Cisco shipped at the time contained release 7.1(2a).
Note
The shipping DVD and the DVD 1 image available on the Cisco Unity Connection 7.1 Software Download page on Cisco.com have been updated with release 7.1(2b).
The defect affected upgrades from Connection versions 7.0 and 2.1(2) and later to version 7.1(2).
COBRAS Support for Migrating from Cisco Unity for Domino
COBRAS, the tool used to migrate from Cisco Unity to Cisco Unity Connection, supports exporting data from Cisco Unity when Domino is the message store.
For more information, see the COBRAS page at http://ciscounitytools.com/App_COBRAS.htm.
Digital Networking
Up to ten Cisco Unity Connection servers can be joined to form a digital network. (In version 7.0, the limit was five servers.)
Note
In a Cisco Unity Connection cluster, only the publisher server is joined to the network, so a cluster counts as a single server toward the limit of ten.
Additional requirements and limits for Digital Networking are available in System Requirements for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.
Note
The Digital Networking feature is not supported for use with Cisco Unified Communications Manager Business Edition.
Fax Support for VPIM Networking with Cisco Unity Express and Cisco Unified Messaging Gateway
Cisco Unity Connection and Connection in Cisco Unified CMBE support using VPIM Networking to send and receive fax messages to Cisco Unity Express and Cisco Unified Messaging Gateway.
LDAP Directories
Revised June 17, 2013You can synchronize Cisco Unity Connection user data with the following additional LDAP directories:
•
Microsoft Active Directory 2008
•
Netscape Directory Server
•
Sun iPlanet Directory Server
•
Oracle Directory Server Enterprise Edition 11g (formerly Sun ONE Directory Server)
Note the following considerations:
•
For Netscape, Sun iPlanet, and Oracle Directory Server Enterprise Edition 11g, you cannot update the LDAP field that maps to the Connection Alias field, or the corresponding Connection users will become inactive.
•
For Netscape and Oracle Directory Server Enterprise Edition 11g, changes to LDAP directory data are replicated to the Connection database immediately, so a scheduled or manual synchronization is not required.
For Active Directory and a Sun iPlanet directory server, changes to LDAP directory data are replicated to the Connection database only if you perform a manual synchronization or if Connection automatically performs a scheduled synchronization.
•
For Netscape and Oracle Directory Server Enterprise Edition 11g, deleting an LDAP user causes the user to be immediately flagged in Connection. The Cisco Unity Connection Administration page for that user says, "User has been deleted from LDAP directory." A scheduled or manual synchronization is not required.
For Active Directory and a Sun iPlanet directory server, the information that an LDAP user was deleted is replicated to the Connection database only if you perform a manual synchronization or if Connection automatically performs a scheduled synchronization.
•
Only Microsoft Active Directory supports specifying additional LDAP directory servers to act as backup in case the LDAP directory servers that Connection accesses for synchronization and for authentication become unavailable.
Note
For Cisco Unified Communications Manager Business Edition, see the Cisco Unified Communications Manager Administration Guide for Cisco Unified Communications Manager Business Edition for information on integrating Connection and Cisco Unified Communications Manager with an LDAP directory.
Phone System Integrations
For Cisco Unity Connection
Cisco Unified Communications Manager version 7.1 has been qualified for use with this release of Cisco Unity Connection.
For supported versions of Cisco Unified CM and Cisco Unified CM Express, refer to the applicable document, depending on the integration type:
•
SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html.
•
SIP Trunk Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucsiptrunkmtx.html.
For information on other supported phone system integrations, refer to the applicable Cisco Unity Connection integration guides at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.
For Cisco Unity Connection in Cisco Unified CMBE
Cisco Unified Communications Manager 7.1 has been qualified for use with Cisco Unified CMBE. It is installed on the same platform with Cisco Unity Connection.
Selected Servers Require Replacement Hard Disks or Additional Memory for Some Configurations
If you are upgrading from Cisco Unity Connection 2.x or 1.x to Connection 7.1 and you want to reuse the current server, for some servers and some configurations you must replace hard disks or add memory. For example:
•
Some servers require replacement hard disks if you are configuring a Connection cluster.
•
Some servers require additional memory if voice recognition and Digital Networking are configured when the sum of contacts, users, distribution lists, locations, personal contacts, and personal distribution lists exceeds 2,000. (These are the first six items on the Tools > Grammar Statistics page in Cisco Unity Connection Administration.)
If you are upgrading an existing Connection server to version 7.1, see the Cisco Unity Connection Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html to determine whether your server requires replacement hard disks or additional memory.
For information on replacing the hard disks or adding the memory, refer to the applicable chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Servers in a Cisco Unity Connection Cluster Can Be Installed in Separate Buildings or Sites That Are Separated by a Firewall
The requirements for a Connection cluster are available in System Requirements for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.
Note
Cisco Unity Connection clusters are not supported for use with Cisco Unified Communications Manager Business Edition.
Software Qualified for Use with Cisco Unity Connection on User Workstations
The following software has been qualified for use on user workstations with Cisco Unity Connection 7.1:
•
Cisco Unity Connection ViewMail for IBM Lotus Notes version 7.1(2)
•
Cisco Unity Connection ViewMail for Microsoft Outlook version 7.1(2)
•
Internet Explorer version 8.0 on all supported Windows operating systems
For the most current version combinations of software qualified for use on user workstations, see Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html.
Single Number to Receive Both Voice Calls and Faxes
Cisco Unity Connection and Connection in Cisco Unified CMBE support using a single number that receives both voice calls and fax calls. In this configuration, incoming calls are directed to a Cisco gateway that can detect a CNG (fax) tone. When a CNG tone is detected, the gateway forwards the fax call to the Cisco Fax Server. When no CNG tone is detected, the gateway forwards the voice call to Connection.
For configuration information, see the "Creating a Cisco Fax Server Integration" chapter of the System Administration Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.
Support for Up to 200 Partitions and 200 Search Spaces
Up to 200 partitions and 200 search spaces are supported. These limits apply either to the directory of a single Connection server or cluster pair, or to the global directory of up to ten servers or clusters in a digital network.
(In earlier versions, the limits were 50 partitions and 50 search spaces.)
Support for 24 Voice Messaging Ports (Connection in Cisco Unified CMBE)
Cisco Unity Connection in Cisco Unified CMBE supports 24 voice messaging ports.
Utility Updates on the Cisco Unity Tools Website
Updates to utilities on the Cisco Unity Tools website are frequently posted between Cisco Unity Connection releases. The updates commonly do not apply to a specific release, so we do not list the tools that have been updated since the last version of Connection. However, you can sign up to be notified when the utilities posted on the Cisco Unity Tools website are updated. Go to http://www.ciscounitytools.com, and click Sign Up Here.
ViewMail for IBM Lotus Notes
Cisco Unity Connection ViewMail for IBM Lotus Notes will be available mid-June. Version 7.1(2) is supported for use on user workstations with Connection version 7.1.
The U.S. English (ENU) version will be released about June 12; other languages will be released at the end of June 2009.
Information on installing and setting up ViewMail for Notes will be available in Release Notes for Cisco Unity Connection ViewMail for IBM Lotus Notes Release 7.1(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/vmn/release/notes/712cucvmnrn.html.
Information on using ViewMail for Notes will be available in ViewMail for Notes Help and in the User Guide for Accessing Cisco Unity Connection Voice Messages in an E-Mail Application at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/user/guide/email/7xcucugemailx.html. (User Guide content is available only in the ENU version of the guide; ViewMail for Notes Help is available in all localized versions.)
You Cannot Upgrade from Connection 2.1(4) to 7.1(2) or 7.1(2a) or 7.1(2b)
Revised September 9, 2009A change that was made to Cisco Unity Connection in version 2.1(4) prevents upgrades from version 2.1(4) to Connection 7.1(2) or 7.1(2a) or 7.1(2b). To upgrade from Connection 2.1(4), you will need to wait for Connection 7.1(3) to be released, in the fourth quarter of 2009. (For information on supported Connection upgrades, see the "Supported Cisco Unity Connection Upgrades" section.)
New Functionality—Release 7.1(2)
This section contains information about new functionality in the 7.1(2) release time frame only. Refer to the release notes of the applicable version for information on new functionality in earlier versions of Cisco Unity Connection.
Release notes for all versions of Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.
Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity Connection 7.1(2). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com for information.
Deactivating Message Notifications
By default, on a notification dialout, the person answering the phone is given the option to deactivate message notifications to the phone number that Cisco Unity Connection called. This is helpful in cases where the wrong phone number was entered for the notification device.
In version 7.1, you can disable this behavior by unchecking the Play Option To Turn Off Message Notification setting on the System Settings > Advanced > Conversation Configuration page in Cisco Unity Connection Administration.
Filtering LDAP Users
If you are synchronizing Cisco Unity Connection user data with user data in an LDAP directory, you may want additional control over which LDAP users you import into Connection for a variety of reasons. For example:
•
The LDAP directory has a flat structure that you cannot control sufficiently by specifying user search bases.
•
You want only a subset of LDAP user accounts to become Connection users.
•
The LDAP directory structure does not match the way you want to import users into Connection. For example, if organizational units are set up according to an organizational hierarchy but users are mapped to Connection by geographical location, there might be little overlap between the two.
In these cases, you may want to use the "set cuc ldapfilter" CLI command to filter the users in the LDAP directory whose accounts can be accessed by Connection.
For considerations and related tasks, see the "Filtering LDAP Users" section in the "Integrating Cisco Unity Connection with an LDAP Directory" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.
Note
For Cisco Unified Communications Manager Business Edition, see the Cisco Unified Communications Manager Administration Guide for Cisco Unified Communications Manager Business Edition for information on integrating Connection and Cisco Unified Communications Manager with an LDAP directory.
Port and Phone System Conditions in Routing Rules for Forwarded Calls
When creating routing rules to handle calls that are forwarded to Cisco Unity Connection (for example, unanswered calls to user extensions), you can use the port or phone system conditions to match rules to calls that arrive on a specific voice messaging port or are sent from a specific phone system.
In earlier Connection versions, port and phone system conditions were available only for direct routing rules.
Relaying Copies of Messages to an External Account
Revised September 1, 2009With the Accept and Relay the Message message action, you can configure user accounts to relay copies of messages that the user receives in Cisco Unity Connection to an external mail account while also saving the messages to the Connection message store.
This configuration may be useful for users who regularly use an alternate device and want easy access to voice messages both on the alternate device and through the Connection user interfaces. It is also useful for users who want to access voice messages in their Microsoft Exchange message store by using the Microsoft Outlook Web Access client.
Note that any actions the user takes on the relayed copy are not reflected on the message in the Connection message store. If the user does not regularly manage new messages in the Connection message store, the user mailbox may quickly exceed the mailbox quota because new messages are not subject to message-aging policies.
For more information, see the "Message Actions" section in the "Setting Up Features and Functionality That Are Controlled by User Account Settings" chapter of the User, Moves, Adds, and Changes Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/user_mac/guide/7xcucmacx.html.
Repeat Notification Option for Pager Devices
Added June 3, 2009Cisco Unity Connection can send multiple message notifications to a pager device for each new message that a user receives. Use the option if users need additional reminders of new messages or if users sometimes do not receive notifications, even though the first call to the pager was successful.
Two settings in Cisco Unity Connection Administration allow you to enable and configure the option:
•
To enable repeat notifications, specify a value greater than zero in the Retries After Successful Attempt field on the New Notification Device page or the Edit Notification Device page for a pager notification device.
•
After the first successful call to the pager, Connection makes calls periodically at the interval you specify in the Retry Interval After Successful Attempt field until the user checks the message or the retry limit is reached.
For example, if Retries After Successful Attempt is set to 2 and Retry Interval After Successful Attempt is set to 15, and the user receives a new message at noon, Connection calls the pager device at noon. If that call is answered but the user does not check the message before 12:15 p.m., Connection calls the pager device again at 12:15 p.m. If the user does not check the message before 12:30 p.m., Connection calls the pager device a second time at 12:30 p.m. At this point, the configured number of retries has been reached, and no further notification calls are made for this message.
Note that the settings generate a series of notifications that is separate from the series that is generated when you enable the Repeat Notification If There Are Still New Messages setting on the Edit Notification Device page for the pager. To avoid confusing the user with multiple repeating notifications, we recommend that you use either the Retries After Successful Attempt setting or the Repeat Notification If There Are Still New Messages setting, but not both. (Users can enable or disable the Repeat Notification If There Are Still New Messages setting for themselves by using corresponding fields in the Cisco Unity Assistant, but they cannot set or change the values for Retries After Successful Attempt or Retry Interval After Successful Attempt.)
For more information on the fields, see the "New Notification Device" or "Edit Notification Device" section in the "Users" chapter or "Templates" chapter of the Interface Reference Guide for Cisco Unity Connection Administration at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/gui_reference/guide/7xcucgrgx.html.
Wizard Available for Creating Wallet Cards of Custom Conversations
The Cisco Unity Connection Wallet Card wizard produces a PDF of a wallet card that can be printed and given to users.
The templates in the wizard list frequently used menu options and shortcuts for managing messages and user preferences by phone; the wizard fills in the applicable keys based on the conversation that you specify. The wizard allows you to specify the key mappings and shortcuts to include on the card for the Main, During Message, After Message, and Send menus. In addition, the generated wallet card includes the Entering Recipients and Selecting Recipients menus. The wizard also allows you to customize technical support information and instructions for logging on to Cisco Unity Connection.
Note
Procedures in the User Guide for the Cisco Unity Connection Phone Interface do not contain the keys that users press for Connection menu options. Instead, the procedures use the prompts that users hear to specify the menu options to choose. To provide users with key information, use the Wallet Card wizard.
The Connection Wallet Card wizard is a Windows-based remote database administration tool. Download the tool and view Help at http://www.ciscounitytools.com/App_CUC_WalletCardWizard.htm.
Changed Functionality—Release 7.1(2)
This section contains information about changed functionality in this release time frame only. Refer to the release notes of the applicable version for information on changed functionality in earlier versions of Cisco Unity Connection.
Release notes for all versions of Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.
Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity Connection 7.1(2). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com for information.
Cisco Unity Connection Conversation Changes
Some default settings and functionality have changed in the Cisco Unity Connection conversation with this release. The changes are described in the following sections:
•
Speed and Volume Changes are Saved
•
Voice-Recognition Conversation Uses Same Keypad Mappings as Specified Touchtone Conversation
Speed and Volume Changes are Saved
Speed and volume changes that users make while listening to messages or to the Cisco Unity Connection conversation will be saved as new default settings for the user. (Note that the voice-recognition conversation is the only conversation that allows users to change the Connection conversation speed or volume by phone.)
If you do not want speed and volume changes to be saved as new default settings for the user, you can disable this functionality by unchecking the Save Speed and Volume Changes Made by User setting on the System Settings > Advanced > Conversation Configuration page in Cisco Unity Connection Administration.
In previous versions, any speed and volume changes that users made while listening to messages were in effect only for that individual message. Any speed and volume changes that users made while listening to the Connection conversation were in effect only for the duration of that phone session. The speed and volume settings were reset to the defaults.
Voice-Recognition Conversation Uses Same Keypad Mappings as Specified Touchtone Conversation
The voice-recognition conversation has been updated to use the same set of keypad mappings as the conversation set in the Touchtone Conversation field on the Phone Menu page of the user profile. The change affects key mappings in the Main menu, during message playback, and in the After Message menu.
In earlier versions, voice-recognition users could press keys as an alternative to saying select commands in cases where using the keypad was more convenient or effective than saying the command. However, the keys defined for this purpose were specific to the voice-recognition conversation, and did not necessarily match the keys that users would use if they switched to using their specified touchtone conversation.
Installation and Upgrade Information
•
Information for Cisco Unified Communications Manager Business Edition Customers
•
Installing Cisco Unity Connection for the First Time
•
Supported Cisco Unity Connection Upgrades
•
Upgrading from Cisco Unity Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version
•
Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1
•
Installation and Upgrade Notes
Information for Cisco Unified Communications Manager Business Edition Customers
Added June 3, 2009•
For instructions on installing a new Cisco Unified CMBE system, see Overview of Mandatory Tasks for Setting Up a Cisco Unified Communications Manager Business Edition 7.x System at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/cucmbe_task_list/7xcucmbetask.html and the Installing Cisco Unified Communications Manager Business Edition Release 7.1(2) guide at http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/install/7_1_2/cmins712.html.
•
For instructions on upgrading a Cisco Unified CMBE system, see the "Software Upgrades" chapter of the applicable version of the Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/ps7273/prod_maintenance_guides_list.html.
CautionIf you are upgrading from Cisco Unified CMBE version 6.x or 7.0 and any languages other than U.S. English (ENU) are currently installed and in use on the 6.x or 7.0 system, you must install the Connection 7.1 versions of the same languages after the Cisco Unified CMBE upgrade. Otherwise, the Connection conversation will not function properly for users who are configured to use non-ENU languages. For information on downloading and installing languages, see the "Downloading Connection 7.x Language Files" and "Installing Language Files on the Connection 7.x Server" sections in the "Adding Languages to the Cisco Unity Connection 7.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
•
There is no supported migration path from Connection 1.x to Cisco Unified Communications Manager Business Edition (CMBE). If you want to migrate from Connection 1.x to Cisco Unified CMBE, you must reinstall all software, and recreate all system and user data.
Installing Cisco Unity Connection for the First Time
Revised September 9, 2009You must use the Cisco Unity Connection DVD to install a new server.
For instructions on installing a new Connection server, see the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.
Supported Cisco Unity Connection Upgrades
Revised September 9, 2009
CautionDo not try to upgrade from Connection 7.x, or 2.1(2) or later to version 7.1(2). Upgrade to Connection 7.1(2b) instead. Otherwise, you will have to revert to the version from which you are upgrading and reupgrade to 7.1(2b).
You can upgrade from the following versions of Cisco Unity Connection directly to version 7.1(2b):
•
7.1(2a)
•
7.1(2)
•
7.0(2)
•
7.0(1) SU1a
•
7.0(1) SU1
•
7.0(1)
•
2.1(3b) SU1
•
2.1(3b)
•
2.1(3a)
•
2.1(3)
•
2.1(2) SU1a
•
2.1(2) SU1
•
2.1(2)
Upgrading from Connection 2.1(4) to version 7.1(2), 7.1(2a), or 7.1(2b) is not supported. For more information, see the "You Cannot Upgrade from Connection 2.1(4) to 7.1(2) or 7.1(2a) or 7.1(2b)" section.
To upgrade a Connection 2.0(1) or 2.1(1) system to Connection 7.1(2b), upgrade first to Connection 2.1(2), then upgrade to Connection 7.1(2b). For more information, see the "Installation and Upgrade Information" section of the Release Notes for Cisco Unity Connection Release 2.1(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/2x/release/notes/212cucrn.html.
Upgrading from Cisco Unity Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version
Revised September 16, 2009For instructions on downloading software that can be used to upgrade a Connection 7.x or 2.1(2) or later system to version 7.1, see "Downloading Software for an Upgrade from Cisco Unity Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version" section.
Note
If you are upgrading to a Service Update (SU) version, download instructions are provided in the readme file posted with the software on the Cisco Unity Connection software download page. (Start at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240, and browse to the applicable Connection version under Unified Communications Applications > Voice Mail and Unified Messaging.)
For instructions on upgrading:
•
A Connection 7.x system to version 7.1, see the "Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
•
A Connection 2.1(2) or later system to version 7.1, see the "Upgrading Cisco Unity Connection 2.1(2) or Later to the Shipping 7.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Downloading Software for an Upgrade from Cisco Unity Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version
Revised April 2, 2012The upgrade application posted on Cisco.com can be used only to upgrade from Cisco Unity Connection 7.x or 2.1(2) or later to the shipping 7.1 version. It cannot be used to install a new Connection 7.1 server, or to migrate from Connection 1.x to 7.1.
Because of the size of the upgrade application, the file has been divided into two parts. Do the following procedure to download the two parts and to recombine them into a single file.
To Download Software for an Upgrade from Connection 7.x or 2.1(2) or Later to the Shipping 7.1(2x) Version
Step 1
Log on to a computer with a high-speed Internet connection, and go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.
Note
To access the software download page, you must be logged on to Cisco.com as a registered user.
Step 2
In the tree control on the Downloads page, expand Products>Voice and Unified Communications>IP Telephony>Unified Messaging>Cisco Unity Connection, and click Cisco Unity Connection Version 7.1.
Step 3
On the Select a Software Type page, click Cisco Unity Connection Software.
Step 4
On the Select a Release page, click 7.1(2), and the download links appear on the right side of the page.
Step 5
Confirm that the computer you are using has sufficient hard disk space for the downloaded files. (The download file sizes appear below the download links.)
Step 6
Click UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part1of2, and follow the on-screen prompts to complete the download. Make note of the MD5 value.
Step 7
Click UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part2of2, and follow the on-screen prompts to complete the download. Make note of the MD5 value.
Step 8
For each downloaded file, use a checksum generator to confirm that the MD5 checksum matches the checksum that is listed on Cisco.com. If the values do not match, the downloaded file is damaged.
CautionDo not attempt to use a damaged file to install software or the results will be unpredictable. If the MD5 values do not match, download the file again until the value for the downloaded file matches the value listed on Cisco.com.
Free checksum tools are available on the Internet, for example, the Microsoft File Checksum Integrity Verifier utility. The utility is described in Microsoft Knowledge Base article 841290, Availability and Description of the File Checksum Integrity Verifier Utility. The KB article also includes a link for downloading the utility.
Step 9
Execute one of the following commands, depending on the operating system, to reunite the two parts of the file:
•
On a Unix/Linux system, copy and paste the following command from this document into the CLI to combine the two files:
cat UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part1of2 UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part2of2 > UCSInstall_UCOS_7.1.2.30000-3.sgn.iso•
On a Windows system, copy and paste the following command from this document into the command prompt (cmd.exe) to combine the two files:
COPY /B UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part1of2+UCS_Install_UCOS_7.1.2.30000-3.sgn.iso_part2of2 UCSInstall_UCOS_7.1.2.30000-3.sgn.isoStep 10
Use a checksum generator to confirm that the MD5 checksum of the reunited file matches the following checksum:
6d5e5a07c4c26857c29ead458d54da67
If the values do not match, the reunited file is damaged.
CautionDo not attempt to use a damaged file to install software, or the results will be unpredictable. If the MD5 value of the reunited file does not match the value listed above, download the file again until the value for the downloaded file matches the value listed on Cisco.com.
Step 11
If you are installing from a DVD, burn the DVD, noting the following considerations:
•
Choose the option to burn a disc image, not the option to copy files. Burning a disc image will extract the thousands of files from the .iso file that you created in Step 9 and write them to a DVD, which is necessary for the files to be accessible for the installation.
•
Use the Joliet file system, which accommodates filenames up to 64 characters long.
•
If the disc-burning application that you are using includes an option to verify the contents of the burned disc, choose that option. This causes the application to compare the contents of the burned disc with the source files.
Step 12
Confirm that the DVD contains a large number of directories and files, not just the .iso file that you created in Step 9.
Step 13
Delete unnecessary files from the hard disk to free disk space, including the two .iso files that you downloaded and the combined .iso file that you created in Step 9.
Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1
For information on migrating from Cisco Unity 4.0(5) or later to Connection 7.1 or from Connection 1.x to Connection 7.1, see the applicable "Migrating from ..." chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Note
There is no supported migration path from Connection 1.x to Cisco Unified Communications Manager Business Edition (CMBE). If you want to migrate from Connection 1.x to Cisco Unified CMBE, you must reinstall all software, and recreate all system and user data.
Installation and Upgrade Notes
•
Installing Additional Cisco Unity Connection Languages
•
License Tag Required to Use the U.S. English Conversation and Personal Call Transfer Rules
Installing Additional Cisco Unity Connection Languages
Revised September 1, 2009For instructions on installing additional Connection languages on the following system types, see the referenced documentation:
•
A new Connection system, see the "Installing Additional Languages on the Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.
•
An existing Connection system, see the "Adding Languages to the Cisco Unity Connection 7.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
•
An existing Cisco Unified CMBE system, see the "Downloading Connection 7.x Language Files" and "Installing Language Files on the Connection 7.x Server" sections in the "Adding Languages to the Cisco Unity Connection 7.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
If you are installing Japanese because you want Cisco Unity Connection Administration to be localized, you must also install the Cisco Unified Communications Manager Japanese locale. See the "Locale Installation" section in the "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide.
If you are installing other languages because you want the Cisco Personal Communications Assistant to be localized, you must also install the corresponding Cisco Unified Communications Manager locales. See the "Locale Installation" section in the "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide.
License Tag Required to Use the U.S. English Conversation and Personal Call Transfer Rules
If you want to use English-United States for the Cisco Unity Connection conversation or you want users to be able to create personal call transfer rules, the Connection license must include the license tag LicRegionIsUnrestricted. If your Connection licenses do not include the LicRegionIsUnrestricted tag and you want to use these features, install a license that includes the tag. After you install the license, you must restart Connection. (Licenses without this tag are intended only for use outside the United States.)
If you choose not to install a license that includes the LicRegionIsUnrestricted tag, you must install one or more Connection languages.
Connection demonstration licenses include the LicRegionIsUnrestricted tag, so you can use English-United States on demonstration systems.
To Determine Whether the LicRegionIsUnrestricted License Tag Is Present
Step 1
In Cisco Unity Connection Administration, under System Settings, click Licenses.
Step 2
On the Licenses page, click the name of the first license file.
Step 3
On the View License page, in the File Content box, search for the text "LicRegionIsUnrestricted."
Step 4
If you do not find the text in the first file, search all of the other license files listed on the Licenses page.
Step 5
If "LicRegionIsUnrestricted" does not appear in any of the license files, get a license that contains the tag before you install Connection.
Important Notes
Connection IMAP Server Service Should Not Be Stopped or Disabled For An Extended Period of Time
Added October 19, 2010The Connection IMAP Server service processes events that are placed in the IMAP queue table in the Connection database when voice messages are created, updated, or deleted, even if you do not have active IMAP users. If the service is disabled or stopped, the table continues to grow, and can eventually fill available disk space and cause database instability. Do not stop the service for more than a day at a time or disable the service indefinitely. If you have previously stopped or disabled the service, try restarting the service. If the service does not start, contact Cisco TAC to apply the workaround for caveat CSCti68395.
Limitations and Restrictions
Connection Cannot Be Installed or Operated in IPv6 or Dual-Stack (IPv4 and IPv6) Networks
Revised November 9, 2010Connection 7.1 does not support IPv6, and cannot be installed or operated in a pure IPv6 network. To install or operate in a dual-stack (IPv4 and IPv6) network, a workaround for CSCtj93659 is required. See the caveat information for CSCtj93659 for more details.
In Connection Cluster, Changed License Data on One Server Does Not Replicate to Other Server
When a new or changed license file is installed on one server of a Cisco Unity Connection cluster, the changed license data is not automatically replicated to the other server.
To replicate the changed license data, you must restart both Connection servers by using the following CLI command:
utils system restartMedia Master Cannot Open WAV Files Saved on a Workstation in G.729a Format
The Media Master cannot open WAV files prerecorded in the G.729a audio format and saved to a workstation.
This limitation has the following workarounds:
•
Convert the WAV file to another audio format (for example, convert it to the G.711 audio format).
•
Use a WAV file that is recorded in a supported audio format other than G.729a.
•
Make the recording by using a phone or a computer microphone.
Note that when Cisco Unity Connection is configured to record in the G.729a audio format, the Media Master functions correctly for recording and playing by using a phone or a computer microphone.
Replacing Disks in a RAID
Connection 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.
CautionDo not replace a disk in a RAID with a disk that contains data, even if the replacement disk was originally a disk in the same RAID in the same server.
ViewMail Limitations Regarding Secure Messages
Added February 22, 2010•
Secure messages cannot be forwarded by using Cisco Unity Connection ViewMail for Microsoft Outlook or ViewMail for IBM Lotus Notes.
•
ViewMail for Outlook and ViewMail for Notes support only playing secure messages.
•
Messages that are composed or replied to by using ViewMail for Outlook or ViewMail for Notes are not sent as secure, even when users are assigned to a class of service for which the Require Secure Messaging field is set to Always or to Ask.
Caveats
The tables in this section list the Severity 1, 2, and 3 open and resolved caveats when Cisco Unity Connection 7.1(2) and 7.1(2a)were released.
You can find the latest caveat information for Cisco Unity Connection versions 7.1(2) and 7.1(2a), and for Connection in Cisco Unified Communications Manager Business Edition version 7.1(2a)—in addition to caveats of any severity for any release—by using Bug Toolkit, an online tool available for customers to query defects according to their own needs. Bug Toolkit is available at http://www.cisco.com/go/bugs.
Note
To access Bug Toolkit, you must be logged on to Cisco.com as a registered user.
This section contains caveat information for Cisco Unity Connection 7.1(2) and 7.1(2a), and Connection in Cisco Unified CMBE 7.1(2a) only:
See the release notes of the applicable version for caveat information for earlier versions of Cisco Unity Connection.
Release notes for all versions of Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.
Open Caveats—Connection Releases 7.1(2) and 7.1(2a), and Connection in Cisco Unified CMBE Release 7.1(2a)
Click a link in the Caveat Number column to view the latest information on the caveat in Bug Toolkit. (Caveats are listed in order by severity, then by component, then by caveat number.)
Resolved Caveats—Connection Releases 7.1(2) and 7.1(2a), and Connection in Cisco Unified CMBE Release 7.1(2a)
Revised June 15, 2009Click a link in the Caveat Number column to view the latest information on the caveat in Bug Toolkit. (Caveats are listed in order by severity, then by component, then by caveat number.)
Related Caveats—Cisco Unified Communications Manager 7.1(2) Components That Are Used by Connection 7.1(2)
Added September 9, 2009Table 3 describes the Cisco Unified Communications Manager components that are used by Cisco Unity Connection.
Caveat information for the Cisco Unified CM components is available in the following documents:
•
ReadMe for Cisco Unified Communications Manager Release 7.1(2b)su1 on the download page for 7.1(2b)SU1 (start at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240).
•
Release Notes for Cisco Unified Communications Manager Release 7.1(2b) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_1_2/cucm-rel_notes-712b.html.
•
Release Notes for Cisco Unified Communications Manager Release 7.1(2a) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_1_2/cucm-rel_notes-712a.html.
Documentation Updates
Errors
This section lists errors in the current documentation for Cisco Unity Connection and for Connection in Cisco Unified CMBE documentation and gives corrected information. The correct information will be incorporated in a future documentation release, or as otherwise noted.
Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Traps and Informs
Added July 13, 2009In the "SNMP Traps and Informs" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the first note (after the first paragraph) should read as follows:
Note
Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, and Cisco Unity Connection support SNMP traps.
System Administration Guide for Cisco Unity Connection: Creating a Calendar Integration with Exchange 2007
Added July 9, 2010The "Creating a Calendar Integration with Exchange 2007" section in the "Creating Calendar Integrations" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x (at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html) incorrectly indicates that you can do a calendar integration with Exchange 2007 Server. Calendar integrations with Exchange 2007 Server are no longer supported in Cisco Unity Connection 7.1(2), 7.1(2a), and 7.1(2b).
Note however that contact and text to speech integrations are still supported with Exchange 2007 Server.
Omissions
This section lists new and additional information that is not included in the current documentation for Cisco Unity Connection and for Connection in Cisco Unified Communications Manager Business Edition. The new and additional information will be incorporated in a future documentation release, or as otherwise noted.
Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Services
Added July 13, 2009In the "SNMP Services" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following row was omitted from Table 15-2, "SNMP Services."
Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Management Information Base (MIB)
Added July 13, 2009In the "SNMP Management Information Base (MIB)" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following section was omitted.
CISCO-UNITY-MIB
The CISCO-UNITY-MIB uses the Connection SNMP Agent to get information about Cisco Unity Connection.
To view the CISCO-UNITY-MIB definitions, go to the following link and click SNMP V2 MIBs:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Note
Cisco Unity Connection supports this MIB. Cisco Unified Communications Manager does not support this MIB.
The Connection SNMP Agent supports the following objects.
Cisco Unified Serviceability Administration Guide Release 7.1(2): Configuring CISCO-UNITY-MIB Trap Parameters
Added July 13, 2009In the "Configuring SNMP Trap/Inform Parameters" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following text should be included as the "Configuring CISCO-UNITY-MIB Trap Parameters" section.
Connection only: The Connection SNMP Agent does not enable trap notifications, though traps can be triggered by Cisco Unity Connection alarms. You can view Cisco Unity Connection alarm definitions in Cisco Unity Connection Serviceability, on the Alarm > Definitions screen.
You can configure trap parameters by using the CISCO-SYSLOG-MIB. See the "Configuring CISCO-SYSLOG-MIB Trap Parameters" section.
Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Replacing Disks in a RAID Array
Added July 9, 2009The Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x does not include any documentation on replacing disks in a RAID array. However, because Connection and Cisco Unified Communications Manager mostly use the same servers, you can use the procedures in the "Performing Failed RAID Disk Replacement" section of the "Cisco Unified Communications Manager System Issues" chapter of the Troubleshooting Guide for Cisco Unified Communications Manager, Release 7.1(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/trouble/7_1_2/tbsystem.html.
Troubleshooting Information
Cisco Unity Connection troubleshooting information can be found in the Troubleshooting Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/troubleshooting/guide/7xcuctsgx.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately
Further information regarding U.S. export regulations may be found at http://www.access.gpo.gov/bis/ear/ear_data.html.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
©2012 Cisco Systems, Inc. All rights reserved.