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
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
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
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
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.
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.
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.
Certificate on AnyConnect VPN Phone
When you upload an updated certificate with the same Common Name (CN) to Phone-VPN-trust, you overwrite the old certificate. Upload the new certificate to the subscriber instead of the publisher. Phone-VPN-trust does not replicate to other servers but this process will still add the new certificate to the database for the Phone VPN Gateway configuration. Therefore, the old certificate will not be overwritten.
new ASA certificate on the ASA, but do not activate it.
Add the new
ASA certificate to the trust store (Phone-VPN-trust).
Add the new
ASA certificate to VPN Gateway Configuration. Select and add the new ASA
certificates in this location."
information about which VPN phones are registering and which VPN phones are not
Apply the new
configuration file to the phones from
Phone Profile Configuration window that is used for VPN phones or from the Device
Pool Configuration window that used for VPN phones.
Reset the VPN
the phone received the updated configuration file or verify that the phone has the new ASA certificate hash information in its configuration file.
the previously registered VPN phones are registering back to Unified
4, 5, 6, and 8.
Remove the old
ASA certificate from the VPN Gateway Configuration.
Extension Mobility Now Supports Device Owners
This documentation update resolves CSCun04965.
You can now configure the Owner User ID in the Phone Settings
interface if you are using Extension Mobility. Extension Mobility now supports
device owners. A note indicating otherwise is listed in error in the
Cisco Unified Communications Manager Administration Guide.
Care Breaks User Call Fwd Settings
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".
Certificate Warnings with IM and Presence Service
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.
Communications Manager Online Help
Help Manual Text Need Update for IPv6 Address (for Dual IPv4/IPv6)
In the Cisco
Unified Communications Manager voice/video server configuration settings table,
under the field IPv6 Address (for dual IPv4/IPv6) :
Configure the IP
Address only .
Do not configure
Time Is Not Manually Configurable Due to NTP Requirement
The following note
appears In the Cisco Unified OS Administration online help in the
Settings > Timemenu and the
OS Administration Guide:
Before you can
manually configure the server time, you must delete any NTP servers that you
Because it is
mandatory to have at least one NTP server, this note is inaccurate. The
following is the correct note:
configure time manually from the
Time window, because you cannot delete all NTP
servers and one NTP server is required.
Treatment When No Path Is Available Default Parameter Change
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
Increase in Number of LDAP Sync Agreements
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. Cisco recommends that the sync agreements for 160,000 users is 10 or
less. 20 sync agreements is recommended only for the system with the number of
sync user 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 times
may increase and potentially double.
Server Performance for Large Firmware Deployments
increased firmware sizes for the DX650 and the EX/MX/SX 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. Cisco recommends that administrators monitor download progress
through Unified RTMT to ensure that all devices sucessfully upgrade. Devices
that experience a download timeout require that the administrator restart the
download process on the affected endpoints by issuing a Apply Config or
Reset/Restart command through Cisco Unified CM Administration.
Care Portal Does Not Recognize Default Voicemail Profile / Pilot
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.
User Template Accepts Only Hexadecimal Characters
The table in
"End user digest
credential settings" sub section of
authentication for SIP phones setup" section states that Digest Credentials
accepts alphanumeric characters, which is wrong. The Digest Credentials accepts
only hexadecimal characters for BAT User Template.
Guide Should Mention That MGCP FXS Ports Do Not Require License
MGCP FXS ports
do not require any license because they are not considered as analog phones.
Bulk Administration Character Length
This documentation update resolves CSCum94975.
The character length for the User Template Name
field is incorrect in the Cisco Unified Communications Manager Bulk Administration Guide. The following table shows the correct description.
User Template Name
Enter a unique name, up to 132 alphanumeric characters, for
the user template.
Unified Communications Manager Alarms
The Cisco Unified Communications Manager Managed Service Guide contains a list of system error alarm messages that may not be up to date.
For a complete list of system error messages, see the System Error Messages document for your release at the following URL:
CSCun49156 IP Phone SSL VPN not Supported on Third Party Firewalls
For IP Phones that use SSL VPN, third-party firewalls are not supported.
CSCun73445 Additional Prerequisite for IP and Hostname Change on IM and Presence Service
Item Added to Pre-Change Task List
For each cluster where the publisher/subscriber node being changed is an intercluster peer, remove the publisher’s/subscriber’s cluster from the list of intercluster peers.
For example, ClusterA, ClusterB and ClusterC are all intercluster peers. You want to change the hostname on the publisher node of ClusterA. You must first remove the ClusterA publisher node from the list of intercluster peers on both ClusterB and ClusterC.
Hostnames in IPv4 and IPv6 Environments
This documentation update resolves CSCun74975.
The following information is omitted from the IPv6 Address
(for dual IPv4/IPv6)
field description under "Server Settings" in the Cisco Unified Communications Manager Administration Guide:
You cannot use an IPv4 address as a hostname in a network environment with both IPv4 and IPv6 addresses.
Music On Hold and Native Call Queuing Behavior
The Announcements with Music On Hold document discusses Native Call Queuing and the added capabilities that are related to customized audio announcements and Music On Hold. Access this document at the following URL:
CSCuo02154 DRS Restore of Failed IM and Presence Service Database Publisher Node Requires DRS Restore of Cisco Unified Communications Manager Publisher Node
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.
CSCuo13148 ATA 187 Not Compatible until Cisco Unified Communications Manager 8.0.3
The Cisco ATA 187 Analog Telephone Adaptor is compatible with Cisco
Unified Communications Manager 8.0.3 and later. For Cisco Unified
Communications Manager 8.0.3, you must install the device pack
cmterm-devicepack22.214.171.12438-1.cop.sgn for Cisco
ATA 187 to be supported.
CSCun07952 USB Music on Hold Fixed Audio Adapter is not Supported
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.
or Disable FIPS for IM and Presence Service
FIPS 140-2 mode for
IM and Presence Service is pending certification at
this time and is not supported until certification is complete.
following information before you enable or disable FIPS 140-2 mode for
IM and Presence Service: After you enable or disable
FIPS 140-2 mode for
IM and Presence Service, the Tomcat certificate is
regenerated and the node reboots. The Intercluster Sync Agent syncs the new
Tomcat certificate across the cluster; this can take up to 30 minutes. Until
the new Tomcat certificate is synced across the cluster, an
IM and Presence Service subscriber node cannot access
information from the
IM and Presence Service database publisher node. For
example, a user who is logged in to the Cisco Unified Serviceability GUI on a
subscriber node cannot view services on the
IM and Presence Service database publisher node. Users
see the following error message until the synching is complete:
Connection to server cannot be established (certificate
Calling Party Normalization Restriction
This documentation update resolves CSCuo56960.
The following restriction is omitted from the Features and Services Guide for Cisco Unified Communications Manager:
When calling or called party transformations are applied at the gateway or route list level, the calling number in the facility information element (IE) for QSIG calls is the post-transformation number. However, the called party in the facility IE is the pre-transformation called party number.
The calling party that is sent after transformation through the gateway is typically localized and does not cause an issue with the display and routing. The called party is typically the dialed digits and is displayed on the calling phone, so the transformation is not relayed for called party transformations. Called party transformation is designed to send the information based on the gateway that the call is going through, regardless of how the number is dialed. Called party transformation is kept at the gateway level and not updated, whereas the calling party is updated.
Directory Number Line Behavior in Cisco Unified Communications Manager
This documentation update resolves CSCuo74599.
The following information is omitted in the "Set Up Cisco Unified IP Phone" procedure in the Cisco Unified Communications Manager Administration Guide:
After you add a directory number to a phone and click Save, the following message appears:
Directory Number Configuration has refreshed due to a directory number change. Please click Save button to save the configuration.
Maximum Hunt Timer Restriction
This documentation update resolves CSCuo90637.
The following note is omitted from the Cisco Unified Communications Manager Administration Guide and online help for Hunt Group configuration:
Do not specify the same value for the Maximum Hunt Timer and the RNA Reversion Timeout on the associated line group.
Unified CM 10.0 Upgrade Process Correction
This documentation update resolves CSCup31306.
In the Change Virtual Machine Configuration Specifications procedure, Step 6 ("Shut down the virtual machine") should be performed before Step 3 ("Change the configuration of the virtual machine").
Remote Destination and Auto Answer
This documentation update resolves CSCtd43582.
The following restriction is omitted from the "Cisco Mobility" chapter in the Features and Services Guide for Cisco Unified Communicatins Manager:
A remote destination call does not work when Auto Answer is enabled.
Cisco Certificate Change Notification Service
This documentation update resolves CSCup84785.
The following content is omitted from the Platform Services section of the "Services" chapter in the Cisco Unified Serviceability Administration Guide:
Cisco Certificate Change Notification Service
This service keeps certificates of components like Tomcat, CallManager, and XMPP automatically synchronized across all nodes in the cluster. When the service is stopped and you regenerate certificates, you have manually upload them to Certificate Trust on the other nodes.
Secure and Nonsecure Indication Tone
This documentation update resolves CSCuq04604.
In the Cisco Unified Communications Manager Security Guide, the section about secure and nonsecure indication tones states that "Protected devices can call nonprotected devices that are either encrypted or nonencrypted. In such cases, the call specifies nonprotected and the nonsecure indication tone plays." This statement applies only if a protected phone calls a nonencrypted, nonprotected phone. If the call is encrypted for both parties, the indication tone plays the secure tone.
Protected devices that call nonprotected devices that are encrypted play the secure tone, while protected devices that call nonprotected and nonencrypted devices play the nonsecure tone.
Transmit UTF8 for Calling Party Name Field Correction
This documentation update resolves CSCup45037.
The Cisco Unified Communications Manager Administrator Guide specifies that the SIP trunk field Transmit UTF-8 for Calling Party Name uses the user locale setting of the device pool to determine what to send in the Calling Party Name field. However, the device pool does not have a user locale field. It has a network locale field, and both the Common Device Configuration record, and the Phone record itself have user locale fields.
The following is the process that the SIP trunk uses to obtain the user locale:
If the Transmit UTF-8 for Calling Party Name is checked to obtain the locale, the SIP trunk attempts to obtain the locale from the device. If that attempt fails, the SIP trunk attempts to obtain the user locale from the Common Device Configuration, and if that attempt fails, the SIP trunk obtains the user locale that is used for the Enterprise Parameters.
Missing Information for Allow Multiple Codecs in Answer SDP
This documentation update resolves CSCup79162.
The following information is omitted from the "SIP Profile Settings" topic in the Cisco Unified Communications Manager Administration Guide and online help:
Configure Allow multiple codecs in answer SDP for the following:
Third-party SIP endpoints that support this capability
SIP trunks to third-party call controls servers that uniformly support this capability for all endpoints
Do not configure this capability for SIP intercluster trunks to Cisco SME or other Cisco Unified Communications Manager systems.
CSCuq44567- SAML SSO Authentication - LDAP Attribute for User ID setting
The following note is missing from the "SAML Single Sign-On"
chapter in Feature and Services Guide for Cisco Unified Communications Manager.
Cisco Unified Communications Manager currently supports only sAMAccountName option as the LDAP attribute for user ID settings.
Incorrect Default Value for LogPartitionLowWaterMarkExceeded Alert
This documentation update resolves CSCuq39087.
The default threshold value for LogPartitionLowWaterMarkExceeded alert is incorrectly described in the Cisco Unified Real-Time Monitoring Tool Administration Guide. The following table contains the correct value.
Table 1 Default Configuration for the LogPartitionLowWaterMarkExceeded RTMT Alert
Trigger alert when following condition met:
Log Partition Used Disk Space Exceeds Low Water Mark (90%)