Cisco Unified IP
Phones 7940 and 7960 Do Not Support Java Midlets
This information applies to CSCtn79567.
Cisco Unified IP
Phones 7940 and 7960 do not support Cisco-signed Java Midlets, but they can
parse the service information from the phone configuration file.
Cisco Unified Mobility Disclaimer
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.
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
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.
information about the deployment of
Unified Communications Manager in a virtualized
Do not perform any
configuration tasks during the upgrade process.
If you are
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
Cisco Unified Communications
Manager. If such failures occur, you must restart the entire upgrade
process for both
Cisco Unified Communcations
IM and Presence Service
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
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 fresh install and 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. There is a workaround for this issue which requires you to contact Cisco TAC for assistance.
This workaround only applies if you have a backup of the IM and Presence Service database publisher node.
Insert the IM and Presence Service domain into the CUCM secureconfig table. You must conatct Cisco TAC for assistance with this step.
Reinstall the IM and Presence Service database publisher node.
Restore the IM and Presence Service database publisher node using the backup.
Resintall the IM and Presence Service subscriber nodes.
Restore the IM and Presence Service subscriber nodes.
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.
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.
With the merging
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
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
Simplified Messaging Desk Interface (SMDI) and Music-On-Hold Live-Audio
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.
Care Breaks User Call Fwd Settings
This information applies to CSCul90262.
calls to: option in the Self Care Portal overwrites any configured
Call Forward No
Busy settings. You must reconfigure
rules if you enable
calls to: outside of the Self Care Portal, such as on a phone app.
option found in the System Enterprise parameters impact this issue
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.
avoid end-users triggering this problem by hiding the
settings from the Self Care Portal by setting the "Show Call Forwarding"
Enterprise Parameter to "Hide All Settings".
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.
Server Performance for Large Firmware Deployments
This information applies to CSCul30613.
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.
Treatment When No Path Is Available Default Parameter Change
This information applies to CSCui70893.
10.0(1), the Location Bandwidth Manager service parameter
"CallTreatmentWhenNoPathIsAvailable" default value of "reject
call" has been changed to
This change has been implemented to allow calls to proceed when a local hub is
Failover Interoperability with Cisco Jabber Clients
If you have configured redundancy with backup servers, the following interoperability limitations apply to Cisco Jabber clients when the primary Cisco Unified Communications Manager server goes down:
Softphone mode—If the Jabber client is in softphone mode, automatic failover is supported so long as the client has already downloaded the device information from the TFTP server (this occurs upon client startup). When the primary server goes down, the Call Preservation feature is invoked. All active Jabber calls are preserved, but users cannot invoke call-processing features. Once all preserved calls have ended, the Jabber client automatically switches over to the backup server. When the primary Cisco Unified Communications Manager server becomes available again, control reverts to the primary server.
Deskphone mode—If the Jabber client is controlling a deskphone, automatic failover is not supported. However, you can switch over to the backup Cisco Unified Communications Manager server by signing out and signing in again on the Jabber client, or by switching to softphone mode, and then back to deskphone mode again.
Reset with Certificate Regeneration
This information applies to CSCus63274.
All devices reset when you regenerate TVS,
CCM, and CAPF client application certificates.
MGCP IOS Gateway
From PSTN Does Not Support Connected Address in ISDN Notify
This information applies to CSCut08346.
The calling-line ID (CLID) information is not displayed through Media
Gateway Control Protocol (MGCP) IOS gateway after the call is transferred since
it does not support Connected Address in ISDN NOTIFY.
Secrecy is not Supported in IPsec Configuration
This information applies to CSCuu74346.
Perfect Forward Secrecy (PFS) security service is not supported in
IPsec configuration between Cisco Unified Communications Manager and Voice
Change Perfmon Counter File Size Parameters in RTMT
If you have started logging perfmon counter data in RTMT and you want to change the file size and maximum number of files, you must first stop counter logging. After you stop the perfmon counters, you can make your changes and then restart perform counters.