The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.
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. |
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.
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. |
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.
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.
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.
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.
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.
Workaround
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.
This information applies to CSCun49156.
For IP Phones that use SSL VPN, third-party firewalls are not supported.
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.
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.
This update is for CSCvg70867.
The System Error Messages for Cisco Unified Communications Manager file is missing the following ENUM definitions for the 78XX and 88xx phones.
Value |
Device Type |
---|---|
508 |
Cisco IP Phone 7821 |
509 |
Cisco IP Phone 7841 |
510 |
Cisco IP Phone 7861 |
544 |
Cisco IP Phone 8831 |
568 |
Cisco IP Phone 8841 |
569 |
Cisco IP Phone 8851 |
570 |
Cisco IP Phone 8861 |
36665 |
Cisco IP Phone 7811 |
36669 |
Cisco IP Phone 8821 |
36670 |
Cisco IP Phone 8811 |
36677 |
Cisco IP Phone 8845 |
36678 |
Cisco IP Phone 8865 |
36686 |
Cisco IP Phone 8851NR |
36701 |
Cisco IP Phone 8865NR |
This update is for CSCvd71818.
The System Error Messages for Cisco Unified Communications file is missing some ENUM values for the LastOutOfServiceInformation set of alarms. Following is a complete list:
Reason Code |
Description |
---|---|
10 |
TCPtimedOut - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error |
12 |
TCPucmResetConnection - The Cisco Unified Communication Manager reset the TCP connection |
13 |
TCPucmAbortedConnection - The Cisco Unified Communication Manager aborted the TCP |
14 |
TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection |
15 |
SCCPKeepAliveFailure - The device closed the connection due to a SCCP KeepAlive failure |
16 |
TCPdeviceLostIPAddress - The connection closed due to the IP address being lost. This may be due to the DHCP Lease expiring or the detection of IP address duplication. Check that the DHCP Server is online and that no duplication has been reported by the DHCP Server |
17 |
TCPdeviceLostIPAddress - The connection closed due to the IP address being lost. This may be due to the DHCP Lease expiring or the detection of IP address duplication. Check that the DHCP Server is online and that no duplication has been reported by the DHCP Server |
18 |
TCPclosedConnectHighPriorityUcm - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM |
20 |
TCPclosedUserInitiatedReset - The device closed the TCP connection due to a user initiated reset |
22 |
TCPclosedUcmInitiatedReset - The device closed the TCP connection due to a reset command from the Cisco Unified CM |
23 |
TCPclosedUcmInitiatedRestart - The device closed the TCP connection due to a restart command from the Cisco Unified CM |
24 |
TCPClosedRegistrationReject - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM |
25 |
RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM |
26 |
TCPclosedVlanChange - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN |
27 |
Power Save Plus |
30 |
Phone Wipe (wipe from CUCM) |
31 |
Phone Lock (lock from CUCM) |
32 |
TCPclosedPowerSavePlus - The device closed the TCP connection in order to enter Power Save Plus mode |
100 |
ConfigVersionMismatch - The device detected a version stamp mismatch during registration Cisco Unified CM |
101 |
Config Version Stamp Mismatch |
102 |
Softkeyfile Version Stamp Mismatch |
103 |
Dial Plan Mismatch |
104 |
TCPclosedApplyConfig - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes |
105 |
TCPclosedDeviceRestart - The device closed the TCP connection due to a restart triggered internally by the device because device failed to download the configuration or dial plan file |
106 |
TCPsecureConnectionFailed - The device failed to setup a secure TCP connection with Cisco Unified CM |
107 |
TCPclosedDeviceReset - The device closed the TCP connection to set the inactive partition as active partition, then reset, and come up from the new active partition |
108 |
VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost 109 IP Address Changed |
109 |
IP Address Changed |
110 |
Application Requested Stop (service control notify to stop registering) |
111 |
Application Requested Destroy |
114 |
Last Time Crash |
200 |
ClientApplicationClosed - The device was unregistered because the client application was closed |
201 |
OsInStandbyMode - The device was unregistered because the OS was put in standby mode |
202 |
OsInHibernateMode - The device was unregistered because the OS was put in hibernate mode |
203 |
OsInShutdownMode - The device was unregistered because the OS was shut down |
204 |
ClientApplicationAbort - The device was unregistered because the client application crashed |
205 |
DeviceUnregNoCleanupTime - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup |
206 |
DeviceUnregOnSwitchingToDeskphone - The device was unregistered because the client requested to switch from softphone to deskphone control |
207 |
DeviceUnregOnSwitchingToSoftphone - The device is being registered because the client requested to switch from deskphone control to softphone |
208 |
DeviceUnregOnNetworkChanged - The device is being unregistered because the client detected a change of network |
209 |
DeviceUnregExceededRegCount - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations |
210 |
DeviceUnregExceededLoginCount - The device is being unregistered because the client has exceeded the maximum number of concurrent logons |
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.
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.
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".
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.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.
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.
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.
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.
This information applies to CSCus63274.
All devices reset when you regenerate TVS, CCM, and CAPF client application certificates.
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.
This information applies to CSCuu74346.
Perfect Forward Secrecy (PFS) security service is not supported in IPsec configuration between Cisco Unified Communications Manager and Voice Gateway.
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.
This information applies to CSCut80673.
HTTP/1.0 version is not supported on Cisco Unified IP Phone 7936 from Cisco Unified Communications Manager 10.x and later.
If you are using the utils system upgrade CLI command to upgrade IM and Presence Service nodes, you must use the default OS admin account, as opposed to a user with administrator privileges. Otherwise, the upgrade will not have the required privilege level to install essential services, thereby causing the upgrade to fail. You can confirm the account’s privilege level by running the show myself CLI command. The account must have privilege level 4.
Please note that this limitation exists for CLI-initiated upgrades of IM and Presence Service only and does not apply to Cisco Unified Communications Manager. Also note that this limitation may be fixed for newer ISO files. Refer to your ISO Readme file for details on your specific ISO file. For up to date information on this limitation, see CSCvb14399 at https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb14399.
IM and Presence server updates the presence status of the user as Unavailable if it does not receive a keep-alive from the client after two 1-minute pings.
The timings for these pings are hard-coded on the server side and are not configurable.
When configuring your call routing, make sure that you don't assign a single route filter to too many route patterns. A system core could result if you were to edit a route filter that has hundreds of associated route patterns, due to the extra system processing that is required to update call routing for all of the route patterns that use the route filter. Create duplicate route filters to ensure that this does not occur. For more information see CSCup04938.