Release Notes for Cisco Unified Communications Manager, Release 10.0(1)
Important Notes
Downloads: This chapterpdf (PDF - 1.19MB) The complete bookPDF (PDF - 2.28MB) | The complete bookePub (ePub - 215.0KB) | The complete bookMobi (Mobi - 375.0KB) | Feedback

Important Notes

Contents

Important Notes

Cisco Unified Mobility Disclaimer


Caution


The Cisco Mobility solution is verified with only Cisco equipment. This solution may also work with other third-party PSTN gateways and Session Border Controllers (SBCs), but each Cisco Mobility feature is not guaranteed to work as expected.

If you are using this solution with third-party PSTN gateways or SBCs, Cisco technical support may not be able to resolve problems that you encounter.


Deployment

In Release 10.0(1) and later, Cisco only supports virtualized deployments of Cisco Unified Communications Manager (Unified Communications Manager) on Cisco Unified Computing System servers, or on a Cisco-approved third-party server configuration. In Release 10.0(1) and later, Cisco does not support deployments of Unified Communications Manager on Cisco Media Convergence Server servers.

Tape device is not supported in virtualized deployments. Upgrade to 10.0(1) and later removes the devices/schedules configured with tape device. Ensure to add the network device(if it does not exists) and re-configure the schedule for backup/restore post upgrade.

For more information about the deployment of Unified Communications Manager in a virtualized environment, see:

http:/​/​docwiki.cisco.com/​wiki/​Unified_​Communications_​in_​a_​Virtualized_​Environment.

No Configuration During Upgrades

Do not perform any configuration tasks during the upgrade process.

Caution


If you are upgrading both Cisco Unified Communications Manager and IM and Presence Service, do not modify any of the IM and Presence Service server entries on the Application Server or Server configuration pages of the Cisco Unified CM Administration interface. The IM and Presence Service upgrade process automatically updates these entries on the Cisco Unified Communications Manager cluster during the final stages (switch version) of the upgrade process.

For upgrades from Release 8.x or 9.x to Release 10.x or later, any manual modification of these entries during the upgrade process will result in data migration failures between IM and Presence Service and Cisco Unified Communications Manager. If such failures occur, you must restart the entire upgrade process for both Cisco Unified Communcations Manager and IM and Presence Service clusters.


Upgrade Considerations for Virtual Machines

You must change the network adaptor type when upgrading a virtual machine. Follow the procedure in Section 5 in the Readme associated with the CUCM 10.0(1) OVA file download.

Not following the procedure can cause performance degradation, and result in a unsupported configuration.

Upgrades from IM and Presence Service 10.0(1) Export Unrestricted

If you are upgrading from IM and Presence Service 10.0(1) Export Unrestricted to any higher release of IM and Presence Service Export Unrestricted (including Service Updates), you must install the unrestricted upgrade COP file before you begin the upgrade: ciscocm.cup.unrst_upgrade_10_0_1_vx.x.cop.sgn. You can download this file from Cisco.com.

Upgrade Fails if AXL Password Contains Special Characters

This document update resolves CSCur00547.

If you have special characters in your Cisco Unified Communications Manager default administrative password, when you upgrade from releases 8.x or 9.x, the connection between IM and Presence Service and Cisco Unified Communications Manager fails. Before you upgrade from an 8.x or 9.x release, you must change your password so that all special characters are removed.

Directory Search in Self Care

The Directory Search option under User Options in releases before 10.0(1) has been removed from the 10.0(1) release onward. However, in the Self Care Portal, the same search capability is available under Contacts and Speed Dials, both of which a user can manually create.

DRS Restore of Failed IM and Presence Service Database Publisher Node Requires DRS Restore of Cisco Unified Communications Manager Publisher Node

This information applies to CSCuo02154.

If you need to perform a Disaster Recovery System (DRS) restore of a failed IM and Presence Service database publisher node, you must also perform a DRS restore of the Cisco Unified Communications Manager publisher node.

IP Phone SSL VPN not Supported on Third Party Firewalls

This information applies to CSCun49156.

For IP Phones that use SSL VPN, third-party firewalls are not supported.

Increase in Number of LDAP Sync Agreements

This information applies to CSCul20279.

The maximum number of users that can be synced into a cluster is 160,000. This is the user limit for LDAP synchronization. The maximum number of LDAP sync agreements is 20. However, using 20 LDAP sync agreements with 160,000 users simultaneously is not supported. We recommend that the sync agreements for 160,000 users is 10 or less. 20 sync agreements is recommended only for a system for which the number of sync users is less than 80,000.

The initial LDAP synchronization times increase substantially (multiple hours) as the number of users and the number of sync agreements increase. Subsequent LDAP syncs will not take as long. If custom LDAP attributes are used, the synchronization time may increase and potentially double.

Jabber Certificate Warnings with IM and Presence Service

This information applies to CSCum63324.

When using the Cisco Jabber client, certificate warning messages can be encountered if the IP address is configured as the IM and Presence Service node name. To prevent Cisco Jabber from generating certificate warning messages, the FQDN should be used as the node name.

Parameter Settings

With the merging of Cisco Unified Communications Manager and IM and Presence Service, enterprise and service parameters are now shared between nodes in a cluster. As such, both types of nodes use the same settings for enterprise and cluster-wide parameters. You need to be aware that not all parameter settings are retained during an upgrade to Release 10.0(1). All enterprise parameters and cluster-wide service parameters that are common to both Cisco Unified Communications Manager and IM and Presence Service retain the value specified on Cisco Unified Communications Manager only, with one exception. The User Assignment Mode parameter is the only enterprise parameter that is retained during upgrade. Service parameters that apply to IM and Presence only are retained after an upgrade.

Cisco recommends that before you begin an upgrade, you make a note of parameter settings and evaluate the best settings for the combined cluster. This will allow you to easily configure those settings after the upgrade is complete.

Removal of Simplified Messaging Desk Interface (SMDI) and Music-On-Hold Live-Audio Source

The Simplified Messaging Desk Interface (SMDI) and Music-on-Hold Live-audio source as used by CMI and SME depend on bare metal USB support. Because this release is virtual-only, SMDI and Music-on-Hold Live-audio source are no longer supported.

Self Care Breaks User Call Fwd Settings

This information applies to CSCul90262.

Selecting the Forward all calls to: option in the Self Care Portal overwrites any configured Advanced calling rules. Advanced calling rules affect Call Forward No Answer and Call Forward Busy settings. You must reconfigure Advanced calling rules if you enable Forward all calls to: outside of the Self Care Portal, such as on a phone app.

The Show Call Forwarding option found in the System Enterprise parameters impact this issue as follows:

  • If the parameter is set to "Show Only Forward All," the user cannot correct the defect by using the Advanced Calling Rules section, as it is not available.

  • Customers can avoid end-users triggering this problem by hiding the Call Forward settings from the Self Care Portal by setting the "Show Call Forwarding" Enterprise Parameter to "Hide All Settings".

Self Care Portal Does Not Recognize the Default Voicemail Profile or Pilot

This information applies to CSCul51014.

If the voicemail profile is configured for directory numbers to inherit the system default, a message appears in the user Self Care portal stating that voicemail pilot has not been configured, even when voicemail is available. To avoid this message, and to provide your users the functionality to launch a call to the Voicemail Pilot using WebDialer, explicitly configure a voicemail profile on each DN.

TFTP Server Performance for Large Firmware Deployments

This information applies to CSCul30613.

Because of increased firmware sizes for some devices, firmware downloads have the potential to timeout and not download successfully from the TFTP server when many devices are simultaneously attempting to download firmware. We recommend that you monitor the download progress through Unified RTMT to ensure that all devices sucessfully upgrade. Devices that experience a download timeout require that you restart the download process on the affected endpoints by issuing an Apply Config or Reset/Restart command through Cisco Unified CM Administration.

USB Music on Hold Fixed Audio Adapter is not Supported

This information applies to CSCun07952.

Cisco Unified Communications Manager Release 10.x does not support the USB Music On Hold fixed audio adapter. You can configure this adapter for use with the SRST router-based multicast Music On Hold. However, the USB adapter is not supported on Release 10.x for MOH audio input from an external sound device, such as an SAT receiver or a CD/DVD. This loss of support may affect you if you use the USB Music On Hold fixed audio adapter and are upgrading from Unified Communications Manager Releases 7.x, 8.x, or 9.x.

Call Treatment When No Path Is Available Default Parameter Change

This information applies to CSCui70893.

In Release 10.0(1), the Location Bandwidth Manager service parameter "CallTreatmentWhenNoPathIsAvailable" default value of "reject call" has been changed to "allow call." This change has been implemented to allow calls to proceed when a local hub is not functioning.