To support TLS encryption between IM and Presence Service and Microsoft Lync/OCS/LCS, you must modify the Peer Authentication TLS Context configuration on IM and Presence Service using the Cisco Unified CM IM and Presence Administration GUI. Ensure that you disable empty TLS fragments when you modify the Peer Authentication TLS Context on IM and Presence Service before integrating with Microsoft Lync/OCS/LCS for Partitioned Intradomain Federation.
CSCub12922 Adding a new subscriber causes device reset
After you install a new node in an existing cluster, all phones that are registered to the cluster are reset.
CSCue04792 EMCC logout limitation
In the visiting cluster, the current Phone Configuration window has a Log Out button for intracluster Extension Mobility (EM). This button is also used by the visiting cluster administrator to log out an Extension Mobility Cross Cluster (EMCC) phone. Because the EMCC phone is not currently registered with the visiting Cisco Unified Communications Manager, this operation is equivalent to a database cleanup in the visiting cluster. The EMCC phone will remain registered with the home Cisco Unified Communications Manager until it comes back to the visiting cluster due to a reset or a logout from the home cluster by other means.
CSCum63324 Jabber 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.
CSCue08776 Call Queuing interaction with Hunt Groups and Hunt Pilots
The logoff notification functionality for hunt groups changes when Call Queuing is enabled for a hunt pilot. The Hunt Group Logoff Notification does not play when a user logs out of a hunt group, or is logged off because they missed their turn in the queue, if Call Queuing is enabled for a hunt pilot.
CSCue58676 Bandwidth management sections of Video Telephony in the 9.x System Guide
In the Differentiated Services Code Point (DSCP) packet marking, the following characteristic is added:
Video streams and associated audio streams in immersive video calls default to CS4 is added.
The following service parameter settings affect DSCP packet marking for media RTP streams are added:
DSCP for Audio Portion of Video Calls
DSCP for TelePresence Calls
· DSCP for Audio Portion of TelePresence Calls
DSCP for ICCP Protocol Links is removed.
CSCtw47643 Cannot Install Signed Microsoft CA Server-Client Authentication Certificate on Microsoft OCS 2008
You cannot install a server-client authentication certificate that is signed by a Microsoft certificate authority (CA) into the local computer store of a Microsoft Office Communications Server (OCS) running Windows 2008. Attempting to copy the certificate from the current user store to the local computer store fails with the error message that the private key is missing.
To resolve this issue, perform the following procedure:
Log on to the OCS as a local user.
Create the certificate.
Approve the certificate from the CA server.
While logged on to the OCS, export the certificate to a file and ensure that the private key is exported.
Log off the OCS (Local Computer).
Log on to the OCS again, but this time log on to the OCS domain as a domain user.
Use the Certificate Wizard to import the certificate file. The certificate is installed in the local computer store. You can now select the certificate in the OCS certificate tab.
CSCts65285 Presence data loss after upgrade from Cisco Business Edition 5000 to Cisco Unified Communications Manager
There is no upgrade path in VMware to upgrade from Cisco Business Edition 5000 to Cisco Unified Communications Manager. A fresh installation is needed. After you perform the fresh installation, IM and Presence Service resynchronizes data with the new Cisco Unified Communications Manager. The Syncagent uses the primary key (pkid) as a comparison field for the synchronization. When the Cisco Unified Communications Manager is reinstalled, all the pkids on Cisco Unified Communications Manager are changed. As such, any existing data on IM and Presence Service is cleaned up and the Syncagent deletes the old data.
Be sure to back up your data before performing this procedure.
CSCto77824 Presence user experiences issues obtaining availability
After an IM and Presence Service server upgrade, when all activated feature services and network services are started, a user experiences inconsistent presence availability. The user can log in to IM and Presence Service but will experience issues obtaining availability information, mainly from SIP-based clients.
This issue is caused when users are provisioned while IM and Presence Service is being upgraded. You must unassign and then reassign the user.
CSCud59343 Access control group permissions interactions
Users can belong to multiple access control groups. When adding a new access control group to existing users, an unexpected reduction in the current level of privileges for some preexisting access control groups may be experienced if the new access control group has the "Effective Access Privileges for Overlapping User Groups and Roles" Enterprise parameter set to Minimum.
Access privilege reduction can occur inadvertently, for example, during an upgrade of Cisco Unified Communications Manager Administration. If the upgrade version supports the Standard RealTimeAndTrace Collection user group, which has the "Effective Access Privileges for Overlapping User Groups and Roles" Enterprise parameter set to Minimum, all users are automatically added to that user group during the upgrade. To resolve the permissions issue in this example, you can remove users from the Standard RealTimeAndTrace Collection user group.
CSCtu18692 CallProcessingNodeCpuPegging alerts for VMware installations
Cisco Unified Communications Manager VMware installations can experience high CPU usage spikes while performing tasks such as DRF backups and Bulk Administration Tool exports. The processes that are commonly responsible for CPU usage spikes are gzip and DRFLocal.
If your system is generating CallProcessingNodeCpuPegging alarms, add an additional vCPU for the support of 7500 Cisco Unified Communications Manager users following the Open Virtualization Archives (OVA) template specifications for your system.
The CallProcessingNodeCpuPegging alert is generated during CPU usage spikes. Other alarms that may also be issued during these CPU usage spikes include CoreDumpFound, CriticalServiceDown, SDLLinkOutOfService, and NumberOfRegisteredPhonesDropped alarms.
When a phone requests a common file from a central or proxy TFTP server and that file has a common name such as ringlist.xml.sgn or is a locale file, the TFTP server sends its own local copy of the file instead of the file from the home cluster of the phone. The phone rejects the file due to a signature verification failure because the file has the signature of the TFTP server's local cluster, which does not match the Initial Trust List (ITL) of the phone. To resolve this issue, you can either disable Security By Default (SBD) for the phone or perform the bulk certificate export procedure to make the Trust Verification System (TVS) return a success when the phone verifies a signature from a different cluster. See the procedure in the "Default Security Setup" section of the Cisco Unified Communications Manager Security Guide for performing a bulk certificate export when migrating IP phones between clusters. To disable Security by Default, see the procedure to update the ITL file for IP Phones in the Cisco Unified Communications Manager Security Guide.
CSCud03278 Empty Far-End When Recording Call Park for some phones
In the current Call Park implementation, the far-end or X-Refci may be empty when recording Call Park for phone models such as 997X, 995X and 896X.
CSCub65671 Route Class Configuration SIP Information
If the route pattern points to a SIP trunk supporting G.Clear, then specify Data or Hotline as the Route Class.
You can use non-default route class settings to translate an inbound T1 CAS route class digit into a Cisco Unified Communications Manager route class value (and strip off the digit). You should not need to assign a non-default route class setting to any other inbound calls that use pattern configuration.
CSCuc63315 Queue Status PLK Supported Phone Models
Queue status PLK is only supported with the following LCD display phones for both SCCP and SIP protocols:
CSCuc55921 Find and List Phones in DNA Using Directory URI
Dialed Number Analyzer (DNA) provides a Phones window where you can find and list phones by device name, description, directory number, Directory URI, calling search space device pool, device type, and call pickup group. You can find a phone and choose it as a calling device for the analysis that you want to perform. You can further choose a configured phone line (directory number) and use it as a calling party number.
CSCuc39511 Expansion module field missing from certain device profiles
The expansion module field is not listed on the Device Profile Configuration window for Cisco Unified IP Phone models 8961, 9951, and 9971. No manual selection is required. The lines from the Phone Button Template are applied to the physical device no matter which expansion modules these phones use.
Skip step 9 in the procedure to "Create the device profile for a user" as documented for Cisco Extension Mobility configuration in the Cisco Unified Communications Manager Features and Services Guide.
If the phone type supports Cisco Unified IP Phone Expansion Modules, Cisco Unified Communications Manager displays expansion module field. At the Module 1 drop-down list box and at the Module 2 drop-down list box, choose the appropriate expansion module.
CSCtb31860 Transcoding G.711 to All Codecs Supported
The transcoder supports transcoding between G.711 and all codecs, including G.711, when functioning as a transcoder and when providing MTP/TRP functionality.
CSCuc30279 Cannot Disassociate Devices from End Users Using BAT
The Bulk Administration Tool (BAT) cannot be used to disassociate devices that are already associated to an end user.
If you manually delete a controlled device from an exported end-user record and then insert the modified user record back in to the Cisco Unified Communications Manager database as a custom CSV data file, the insertion appears successful when you check the job results using Bulk Administration > Job Scheduler. However, the controlled device is still listed on the End User Configuration window in Cisco Unified Communications Manager Administration.
CSCts83374 Remote destination single number reach and enterprise number call reroute
In Cisco Unified Communications Manager Administration, use the Device > Remote Destination menu path to configure remote destinations.
Single Number Reach
You can configure all of the Remote Destination Configuration Settings for Single Number Reach.
Reroute Remote Destination Calls to Enterprise Number
For the Reroute Remote Destination Calls to Enterprise Number, you can configure:
Answer Too Soon Timer
Answer Too Late Timer
For the Reroute Remote Destination Calls to Enterprise Number, you can not configure:
Delay Before Ringing Timer
Enable Mobile Connect
CSCtr78911 Answer Too Late Timer
In Cisco Unified Communications Manager Administration, use the Device > Remote Destination menu path to configure remote destinations.
Answer Too Late Timer
Enter the maximum time in milliseconds that Cisco Unified Communications Manager allows for the mobile phone to answer. If this value is reached, Cisco Unified Communications Manager stops ringing the mobile phone and pulls the call back to the enterprise.
Range: 0 and 10,000 - 300,000 milliseconds
Default: 19,000 milliseconds
If the value is set to zero, the timer is not started.
CSCtr49649 Cisco Unified CM installation on MCS 7825 H3 and 7828 H3 server models
Note the following revision to step 5 of the Install software procedure in Installing Cisco Unified Communications Manager, Release 9.0(1).
The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:
First, the installation process checks for the correct drivers, and you may see the following warning:
No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?
To continue the installation, choose Yes.
The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.
The installation process next verifies RAID configuration and BIOS settings.
For MCS 7825 H3 and MCS 7828 H3 Server models, the installation process detects and disables the SATA RAID, if enabled. The System Rebooting Intermediately window appears with the message
System is going to reboot for SATA RAID to be disabled in BIOS
Press any key to continue
This disables the SATA RAID and reboots the system. On reboot, the installation will continue and will activate the Linux SW RAID.
If this step repeats, choose Yes again.
If the installation program must install a BIOS update, a notification appears telling you that the system must reboot. Press any key to continue with the installation.
After the hardware checks complete, the Product Deployment Selection window displays.
CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated
When upgrading the publisher node, there will be a temporary server outage until all subscriber nodes get upgraded to the new software version.
CSCtk68384 disable ICH10 onboard SATA controller on EX/ESXi servers during Unified CM installation
If the server is running VMware EX/ESXi and the motherboard has an ICH10 onboard SATA controller, you must disable the SATA controller in the BIOS. The ICH10 onboard SATA controller is not supported by EX/ESXi. Perform the following steps to disable the SATA controller in the BIOS as a pre-installation task when installing the Cisco Unified Communications Manager.
Boot the server and press F2 when prompted during boot up.
Select Advanced tab.
Select Mass Storage Controllers Configuration.
Set the Onboard SATA Controller to Disabled.
CSCua63006 and CSCth80282 Regenerate certificate
You can regenerate certificates from the Cisco Unified Communications Operating System as an operating system security function. For more information about regenerating certificates, see the Cisco Unified Communications Manager Security Guide.
Regenerating a certificate can affect your system operations. Regenerating a certificate overwrites the existing certificate including a third party signed certificate if one was uploaded.
Certificate regeneration or upload of a third party signed certificate should be performed during maintenance.
The following table describes the system security certificates you can regenerate from the Cisco Unified Communications Operating System and the related services that must be restarted. For information about regenerating the TFTP certificate, see the Cisco Unified Communications Manager Security Guide.
Table 1 Certificate Names and Descriptions
This self-signed root certificate is generated during installation for the HTTPS server.
This self-signed root certificate is generated during installation for IPsec connections with MGCP and H.323 gateways.
Cisco Disaster Recovery System (DRS) Local and Cisco DRF Master
This self-signed root certificate is installed automatically when you install Cisco Unified Communications Manager. This certificate provides server identification, including the server name and the Global Unique Identifier (GUID).
CallManager and CAPF
The system copies this root certificate to your server or to all servers in the cluster after you complete the Cisco client configuration.
CallManager and CAPF
This is a self-signed root certificate.
If you regenerated the certificate for Cisco Certificate Authority Proxy Function (CAPF) or Cisco Unified Communications Manager and a CTL client is configured, rerun the CTL client.
After you regenerate certificates in the Cisco Unified Communications Operating System, you must perform a system backup so that the latest backup contains the regenerated certificates. If your backup does not contain the regenerated certificates and you perform a system restoration task, you must manually unlock each phone in your system so that the phone can register with Cisco Unified Communications Manager. For information about performing a backup, see the Disaster Recovery System Administration Guide.
Navigate to Security > Certificate Management.
The Certificate List window displays.
Click Generate New.
The Generate Certificate dialog box opens.
Choose a certificate name from the Certificate Name list. For details about certificate names, see the Certificate Names and Descriptions table.
Click Generate New.
If intracluster communication is enabled using EMCC complete the following steps during certificate regeneration.
Navigate to Advanced Features > EMCC> Intercluster Service Profile and deactivate EMCC Service.
Logout all remotely logged in devices from Device > Related Link > Remotely Logged In Device.
Perform the Bulk Certification operation.
Activate the EMCC Service.
What to Do Next
Restart all services that are affected by the regenerated certificate as listed in the Certificate Names and Descriptions table.
Rerun the CTL client (if configured) after you regenerate the CAPF or CallManager certificates.
Perform a system backup to capture the newly regenerated certificates. For information about performing a backup, see the Disaster Recovery System Administration Guide.
CSCtz29138 Enable Mobile Connect for IP Multimedia Subsystem
For IP Multimedia Subsystem, ensure that the Mobile Connect feature is enabled in the Remote Destination Configuration window, or by using one of the other methods prescribed for enabling Mobile Connect, before implementing Intelligent Session Control call processing.
CSCub10861 Call waiting behavior with MLPP Preemption correction
When a Routine precedence call is offered to a destination station that already has active calls that are configured with call waiting, normal call waiting is activated if the existing call count is less than the busy trigger.
When a non-routine precedence call is offered to a destination station that already has an active call that is configured with call waiting, precedence call waiting is activated if the existing call count is less than the busy trigger and any of the following conditions exist:
The device supports visual call appearances and has an open appearance.
The device supports two non-visual call appearances and has an open appearance, and the precedence of the new call is equal to or lower than the existing call.
The device has an open appearance (visual or non-visual) and the device is non-preemptable.
When a non-routine precedence call is offered to a destination station that already has an active call that is configured with call waiting, an existing lower-precedence call is preempted if the existing call count is equal to or greater than the busy trigger.
CSCtt41576 Trace option for show media streams CLI command
The trace option for the show media streams cli command activates extra trace from the media driver to the system log.
Ignore any kernel messages that display on the console screen when show media streams trace is entered.
Since the primary language spoken in Belgium is Dutch, you can download the Dutch (Netherlands) locale file, for example, cm-locale-nl_NL- 184.108.40.2060-1.cop.sgn (Cisco Unified Communications Locale Installer 220.127.116.1100-1 Dutch (Netherlands)). Secondary languages commonly spoken in Belgium are French and German.
Cisco IP Phones and Cisco Unity Connection support for IPv6 - CSCtz88812
For information about IPv6 support for your IP phone or Unity Connection, see the Cisco Unified IP Phone Administration Guide that supports your phone model or the Cisco Unity Connection documentation.
IPv4-only support for video streams
Cisco Unified Communications Manager Release 9.0 supports IPv4 only for video streams. Calls between video endpoints and an application must use IPv4 only for both voice and video media streams.
Prior to Cisco Unified Communications Manager Release 9.0, there was one exception. Cisco Unified Video Advantage, which uses IPv4 exclusively, could be associated with a dual-stack Skinny Client Control Protocol (SCCP) IP phone, forming a composite endpoint which could, in certain circumstances, use IPv6 for voice and, at the same time, IPv4 for video media streams.
In Cisco Unified Communications Manager Release 9.0 and later, this exception is no longer supported, and video will be disabled whenever a dual-stack IP phone configured in dual-stack or IPv6-only mode is associated with Cisco Unified Video Advantage. IP phones associated with Cisco Unified Video Advantage must be reconfigured to use IPv4 only for voice, if they are to continue to support video.
Localization not supported for some Unified CM components
Localization is not supported for the following Cisco Unified Communications Manager, Release 9.0(1) components:
Cisco Unified Serviceability
Cisco Unified Reporting Tool
Cisco Disaster Recovery System
Cisco Dialed Number Analyzer
Cisco Unified CM Administration is localized for Japanese, Chinese, and Korean; Cisco Unified CM Administration > Help only supports Japanese.
When initially configuring your system for Cisco clients, use Cisco Unified CM IM and Presence Administration > Application > Legacy Clients to configure the settings below:
LDAP Client Attribute Mapping
In future releases of Jabber clients, some of these settings may no longer need to be configured.
Unified CM assigns nonsecure conference bridge when conference initiated by nonsecure phone
If a nonsecure phone that is assigned to a media resource group list initiates a conference and a nonsecure conference bridge is available in the media resource group list, Cisco Unified Communications Manager allocates the nonsecure conference bridge even if a secure conference bridge with a higher priority ranking is also available in the media resource group list.
Install language prompts for TAPS
If you need to install language prompts other than English, you must install the Locale Installer on all nodes in your Unified CM cluster. After you install the Locale Installer, you must pull the locale specific AAR file that the Locale Installer saves to the Unified CM TFTP directory and install that file in Cisco Unified Contact Center Express.
Download the Locale Installer that contains your language from cisco.com.
Install the Locale Installer on each Unified CM cluster node.
For detailed installations on installing locales in Unified CM, see "Software Upgrades" in the Cisco Unified Communication Operating System Administration Guide.
Restart each cluster node.
Login to Cisco Unified Operating System Administration and choose Software Upgrades > TFTP File Management.
Search for the AAR file that the Locale Installer installed in Unified CM’s TFTP directory.
Login to Cisco Unified Operating System CLI.
Use the file get tftp <AAR file name> CLI command to get the file from Unified CM’s TFTP directory.
See the Cisco Unified Contact Center Express product documentation for instructions on how to install and configure the AAR file in Cisco Unified Contact Center Express.
CSCtj43528 FindAndList Gateway Template does not display the templates
FindAndList Gateway Template does not display templates with less than five characters. To display the list of templates, create a template with more than five characters.
RD numbers cannot be provisioned on two different clusters
The same RD cannot be provisioned on two different clusters. If a call is made across two clusters, the dtmf signal, and some other signals, will stop forwarding after hitting the first provisioned RD cluster. The second cluster will not receive it.
CSCtw79487 Default device pool may not be chosen after upgrades to 5.x or later
If you upgrade an existing system to 5.x or later and your system includes new device types, the Default Device Pool may not be selected for the new device types. After the upgrade, you must check to ensure that the Device Pool that you want is assigned.
CSCua87279 DoCoMo phones not certified
The Remote Destination Configuration Settings section that appears in the “Cisco Unified Mobility” chapter of the Cisco Unified Communications Manager Features and Services Guide states that the Mobile Phone check box does not apply to dual-mode phones that are running SIP, such as DoCoMo N902iL and DoCoMo N906i. This information is correct. However, the DoCoMo phones should not be explicitly mentioned since neither phone has been certified with Cisco Unified Communications Manager.
CSCua75983 Support for midcall mobility features with Cisco Unified Border Element
Cisco Unified Mobility supports the Mobile Connect feature without mid-call features over SIP trunks with Cisco Unified Border Element (CUBE). To enable mid-call features, you must also configure an Enterprise Feature Access directory number and check the Send send-receive SDP in mid-call INVITE check box that appears in the SIP Profile Configuration window of the SIP profile that is assigned to the SIP trunk.
In Cisco Unified Communications Manager Administration, you can use the Device > Phone page to configure the following MLPP parameters:
If you do not set the MLPP parameters on the phone configuration page, the system uses the settings configured in the common device configuration. If the MLPP paramaters are not configured in the common device configuration, then the settings from the enterprise parameters are used. MLPP parameters are not inherited from settings in the device pool.
LBM Hub Node TCP Port 9004 must only be accessible by trusted nodes
Unified CM 9.0(1) introduces a new architecture for propagating Locations Bandwidth information end-to-end in a multi cluster environment. In the initial release, this feature is not secured so it is critical that only trusted hosts are able to access TCP Port 9004 on any node configured as a Locations Bandwidth Manager (LBM) Hub Node. Future versions of Unified CM will implement a solution to verify the authenticity of this signaling. This requirement does not apply for isolated clusters with no LBM Hub Node Groups configured.
When you install the Cisco Unified Communications Manager on a server, the locale English_United_States installs automatically; however you can add new locales to the server if required. If you add new locales, add them only after you have installed Cisco Unified Communications Manager on all servers in the cluster, and have set up the database.
Install COP enabler files for any custom device types that you want to use that do not ship with Cisco Unified Communications Manager. Perform this task only after you have completed the installation for the entire cluster, and set up the database.
Following an upgrade, the Configure Automatic Database Purge > MAX DATABASE AGE parameter will be changed to one of the following:
If the MAX DATABASE AGE in the old version is between 1 and 60, it will be configured to 60 in the new version.
If the MAX DATABASE AGE in the old version is between 60 and 180, it will be configured to the same age in the new version.
If the MAX DATABASE AGE in the old version is more than 180, it will be configured to 180 in the new version.
Secure shell password maximum length
The maximum length of a secure shell password is 50 characters. It can include any alphanumeric or special characters.
CSCtw78204 RTMT cannot collect OPC logs under default settings
If you are using Cisco Real-Time Monitoring Tool (RTMT) to monitor Cisco Unified Contact Center Enterprise, RTMT cannot collect OPC logs under the default settings. This issue arises because the default timeout for RTMT log collection is 60 seconds, but the OPC log collection process takes longer.
To resolve the issue, open the <RTMT_INSTALLATION_FOLDER_PATH>/conf/rtmt.xml file from the RTMT installation folder and change the value for ReadTimeout to 360. After you make the change, RTMT will be able to collect OPC logs.
CSCub51519 no audio after pressing mobility button
In Unified CM 9.0(1), the Cisco Unified Mobile Communicator must be enabled for a mobile phone on the Mobility Identity Configuration page.
CSCub12688 FinalCalledPartyNumber field description is incorrect
The Cisco Unified Communications Manager Call Detail Records Administration Guide states that the FinalCalledPartyNumber record represents a numeric string of up to 48 characters that can be either digits or a SIP URL. This information is incorrect. The field does not have a 48 character limit and can be an alphanumeric string that can be either digits or a SIP URL.
CSCub59376 Missing step in Unified CM hostname update
There is a missing step in each of the procedures that describe how to change a server hostname in the Changing the IP Address and Hostname for Cisco Unified Communications Manager document. Immediately after you change the hostname of a Unified CM server and save your changes, the server reboots automatically. Immediately after the server reboots, you must bring up the Admin CLI for the server on which the hostname was changed and run the utils dbreplication dropadmin db command. This step applies to any procedure that involves a hostname change for Cisco Unified Communications Manager.
CSCub17607 SIP Redirect by Application requires a SIP route pattern
If the Redirect by Application check box in the SIP Profile Configuration window is checked, Cisco Unified Communications Manager passes the Contact header of the redirection request through its routing engine and applies routing logic to forward the redirection request to the address in the Contact header. If the host portion of the Contact header is not a local Unified CM, a SIP route pattern may be required to map the host portion of the Contact header to an outgoing trunk or Unified CM will not be able to route the call.
For detailed information on how Unified CM routes SIP requests, see "Routing of SIP Requests in Unified CM" in the Dial Plan chapter of the Cisco Unified Communications System SRND.
CSCub77698 Cause tag required for convertHIToDiversion() API
If you are implementing the convertHIToDiversion() function with SIP Transparency and Normalization, a Diversion header will only be produced if the Histoy-Info header contains a “cause=” tag.
CSCuc23992 Call Preservation support for SIP trunks
The Call Preservation feature in Cisco Unified Communications Manager supports SIP trunks. Active calls that cross a SIP trunk do not get interrupted when a Cisco Unified Communications Manager node fails, or when communication between a device and its cluster node fails
CSCuc77135 Port Information for UDS
The TCP and UDP Port Usage for Cisco Unified Communications Manager document does not mention port usage information for Cisco User Data Services. Endpoints can make a TCP connection to Cisco Unified Communications Manager port 8443 for Cisco User Data Services requests.
CSCto78373: SCCP device handles one call in a pending state
You can use the Computer Telephony Integration application, known as the CTI application, to control Cisco Unified IP Phones.
For phones that are running SCCP, outbound dialing supports enbloc (the phone collects all digits before passing them to Cisco Unified Communications Manager for routing) or digit-by-digit collection. If dialing is done digit-by-digit, a CTI dialing call state notification gets sent to the phone when it goes off hook and the first digit is pressed for an outgoing call. For enbloc outbound dialing, the dialing call state notification gets delayed until the phone collects all the digits and sends them to Cisco Unified Communications Manager for routing.
When an outbound call is pending on an SCCP device and is not yet connected, Cisco Unified Communications Manager does not process call setup requests for that device until the first call is connected. If you are using a CTI application for outbound dialing, Cisco recommends that you configure an interval between outbound calls to ensure that pending calls are connected before new call requests are initiated.
CSCuf57901 Video resolution support for SIP phones
Cisco Unified Communications Manager supports the imageattr line in the Session Description Protocol (SDP) portion of the SIP header for higher resolution video calls. Cisco SIP phones that support w360p (640 x 360), such as the 9951, 9971, and 8961, automatically select the best resolution for video calls depending on the following criteria:
If the session level bandwidth is greater than 800 Kbps and the imageattr[640 x 480] line in the SDP exists, then VGA is used.
If the session level bandwidth is greater than 800 Kbps and the imageattr[640 x 480] line in the SDP does not exist, then w360p is used.
If the session level bandwidth is less than 800 Kbps but greater than 480 bits per second and the imageattr[640 x 480] line exists, then VGA 15 frames per second is used.
If you currently have a Cisco Unified IP Phone model 9951, 9971, or 8961 that supports w360p (640 x 360) video resolution and are upgrading to Cisco Unified Communications Manager Release 8.5(1) or later, you may notice changes in the resolution of video calls.
The following video call flow is between two 9951 phones (Phone A and Phone B) without imageattr line support (for example, using
Cisco Unified Communications Manager Releases 8.0(1) and earlier):
Phone A sends a SIP message with an imageattr line in the SDP.
Cisco Unified Communications Manager deletes the imageattr line in the SDP and then sends the modified SIP message to Phone B.
Phone B attempts to send video with the w360p resolution because there is no imageattr line in the SDP portion of the SIP header.
The following video call flow is between two 9951 phones (Phone A and Phone B) with imageattr line support (for example, using
Cisco Unified Communications Manager Releases 8.5(1) and later):
Phone A sends a SIP message with the imageattr line in the SDP.
Cisco Unified Communications Manager does not delete the imageattr line and sends the SIP message to Phone B unchanged.
Phone B attempts to send video with the VGA resolution.
Call Queuing not supported with mobile device types
Cisco Unified Communications Manager does not support Call Queuing with mobile device types.
CSCuh70981: Presentation sharing supported with BFCP
The Cisco Unified Communications Manager System Guide incorrectly states that Binary Floor Control Protocol (BFCP) is not supported when used between Cisco Unified Communications Manager and a Cisco TelePresence MCU conference bridge.
Cisco Unified Communications Manager supports presentation sharing with BFCP between Unified Communications Manager and a Cisco TelePresence MCU.
CSCug84842 Installation fails with unrecoverable internal error
Application user name and password
When you install Cisco Unified Communications Manager, you must enter an Application User name and password. You use the Application User name and password to access applications that are installed on the system, including the following areas:
Cisco Unified CM Administration
Cisco Unified Serviceability
Real Time Monitoring Tool
Cisco Unified Reporting
To specify the Application User name and password, follow these guidelines:
Application User name - The Application User name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores.
Application User password - The Application User password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
Do not use the system application name as the Application User name. Using a system application name causes the installation to fail with an unrecoverable error during the installation of the database
System application names are:
You can change the Application User name and password by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.
CSCul10528 License Mac references
In Unified Communications Manager 9.x and later, the license mac is no longer used for licensing purposes; Enterprise License Manager handles licensing. Please ignore references to the license mac in the documentation.