 Feedback
|
Table Of Contents
Release Notes for Cisco Unified Presence Release 6.0(x)
Installation and Upgrade Notes
Supported Upgrade Paths to Cisco Unified Presence Release 6.0(x)
The Latest Software Upgrades for Cisco Unified Presence on Cisco.com
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(1) to 6.0(2)
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(3)
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(4)
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(5)
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(6)
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(7)
Additional Installation and Upgrade Considerations
Backing Up Data on an Unsupported Cisco Unified Presence1.0(3) server upgraded to 6.0(5)
Migrating Data To a Cisco Unified Presence 6.0(5) Server Installed on New Hardware
Verifying System Configuration
Cisco Unified Presence Release 6.0(2) Engineering Special
Problem Description and Resolution
Special Installation Instructions
Cisco Unified Presence Release 6.0(1)
About Cisco Unified Communications Manager Alignment
Cisco Unified Presence Features
About Application Programming Interfaces
Cisco Unified Presence Release 6.0(2)
Support Status for Transport Layer Security (TLS) in SIP Trunk
How to Configure Cisco Unified Presence for Integration with Microsoft Exchange 2007
Creating an Exchange Account with a Mailbox
Delegating Roles and Receive-As Permissions to the Exchange Account
Verifying Permissions on the Exchange Account
Cisco Unified Presence Release 6.0(3)
Recommended Best Practice for Microsoft Exchange 2007 Integration
Exchange Calendaring Using Forms-based Authentication (FBA)
New Data Field to Authenticate Microsoft Office Communicator Users At Login
Cisco Unified Presence Release 6.0(5)
Licence Change for the Cisco Phone Control and Presence with IBM Lotus Sametime Application
About Cisco Unified Presence Release 6.0(1)
IP Address Change Unsupported After Installation
No Status Displays For a Buddy
Microsoft Office Communicator Logins Fail
Cisco Unified Presence Server Upgrades
Intercluster Code Cannot Determine the Correct Routing
Microsoft Office Communicator Call Forward Fails
Server and Phone Support Information
Cisco Unified Presence Administration GUI Drop-Down Menus Display Cryptic Values
IPPM Automatic Meeting Reminder Feature
About Cisco Unified Presence Release 6.0(2)
CTI Gateway Authentication against Cisco Unified Communications Manager is Case-Sensitive
IBM SameTime Click-to-Call Support Information
Cisco Unified Presence Administration GUI Drop-Down Menus are Inaccessible
Intercluster Code Can Determine the Correct Routing
Call Forwarding Status Not Updating in Microsoft Office Communicator
Presence Update Delay on Cisco Unified Personal Communicator if the Reverse Lookup Scope is Missing
About Cisco Unified Presence Release 6.0(3)
Sync Agent Test in System Configuration Troubleshooter
Reverse Look-up of International Dial Plans in E. 164 Format
Duplicate Users in Cisco Unified Presence Limited to 250 Records
About Cisco Unified Presence Release 6.0(4)
Call Transfer Fails Via SIP Proxy
Release 6.0(3) to 6.0(4) Upgrade of Cisco Unified Presence Does Not Preserve CA Certificate
About Cisco Unified Presence Release 6.0(5)
Image Extensions Can Cause Install Problems with Patch File Download
AXL executeSQLQuery Request Hangs or Fails on Large Request
Cisco Unified Presence Engine Database Service is not Correct in SYSAPPL-MIB
Sync Agent Fails to Synchronize Data from Cisco Unified Communications Manager
Config Agent Static routes Do Not Update Correctly
IPPM : XML Parse Error when showing Message History
MOC Call Transfers to External Destinations Fail
Disabling DNS and Reverse DNS Lookup on Cisco Unified Presence for CVP integration
About Cisco Unified Presence Release 6.0(6)
About Cisco Unified Presence Release 6.0(7)
Cisco Unified Presence Release 6.0(2)
Cisco Unified Presence Release 6.0(3)
Cisco Unified Presence Release 6.0(4)
Cisco Unified Presence Release 6.0(5)
Cisco Unified Presence Release 6.0(6)
Cisco Unified Presence Release 6.0(7)
Cisco Unified Presence Release 6.0(1)
Cisco Unified Presence Release 6.0(2)
Proxy Static Routes Precedence
Required User permissions for Intercluster Peer Configuration
Configuration Troubleshooter: Interclustering Test
Intercluster Peer Duplicates Navigation Link
Uploading Microsoft Exchange Certificates
Uploading CA-Signed Certificates
How to Configure the LCS Certificate Chain
Uploading Supported x509 Certificates
Enabling and Disabling Empty TLS Fragments
Managing Live Communications Server (LCS) Security Certificates
Office Communications Server 2007 Support
Message Reply in IP Phone Messenger
Root Certificate Upload Procedure
Cisco Unified PresenceTrust Certificate Filename
Cisco Unified Presence Upgrade Considerations
Cisco Unified Presence Release 6.0(3)
Cisco Unified Communications Manager CtiGw Application User Name is Case Sensitive
Restarting the SIP Proxy to Complete Installation of Second Node
Cisco Unified MeetingPlace Express Unsupported in Cisco Unified Presence
Configuration of SSL Security Certificate for Meeting Notifications
Installing CA on the Exchange Server
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Release Notes for Cisco Unified Presence Release 6.0(x)
Revised: May 20, 2010
These release notes describe requirements, restrictions, and caveats for Cisco Unified Presence Release 6.0(1) up to and including Cisco Unified Presence Release 6.0(7).
Note
To view the release notes for previous versions of Cisco Unified Presence, choose the Cisco Unified Presence version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Before you install Cisco Unified Presence, Cisco recommends that you review the "Quick Reference for URLs" section for important documentation about Cisco Unified Presence.
Contents
•
•
•
Introduction
Cisco Unified Presence, a critical component for delivering the full value of a Cisco Unified Communications environment, collects information about user availability, such as whether users are using communications devices (for example, a phone) at a particular time. It can also collect information about individual user communications capabilities, such as whether web collaboration or video conferencing is enabled. Using this information, applications such as Cisco Unified Personal Communicator and Cisco Unified Communications Manager can improve productivity by helping employees connect with colleagues more efficiently through determining the most effective way for collaborative communication.
Quick Reference for URLs
Table 1 lists URLs for additional documentation related to Cisco Unified Presence.
Table 1 Quick Reference URLs
Cisco Unified Presence Compatibility Information
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
Cisco Unified Presence Documentation
http://www.cisco.com/en/US/products/ps6837/tsd_products_support_series_home.html
System Requirements
Hardware Server Requirements
The Cisco Unified Presence system is a software product that is loaded onto a hardware server. The hardware server must meet the following requirements:
•
–
–
•
•
The Cisco Unified Presence installer checks for the presence of the DVD-ROM drive, sufficient hard drive and memory sizes, and sufficient CPU type and speed.
Related Topics
Server Software Requirements
The Cisco Unified Presence server runs on the Cisco Linux-based operating system. This operating system is included with the application.
Related Topics
•
Supported Browsers
You can access Cisco Unified Presence Administration, Cisco Unified Serviceability, and Cisco Unified Communications OS Administration using the following browser:
–
•
Installation and Upgrade Notes
•
•
Supported Upgrade Paths to Cisco Unified Presence Release 6.0(x)
Cisco Unified Presence Release 6.0(x) supports the following software upgrade paths:
•
See the note below for information on upgrading from Release 1.0(3) to Release 6.0(6) or a higher 6.0(x) release of Cisco Unified Presence.
Caution
Upgrade from Cisco Unified Presence Releases 1.0(3) and 6.0(1) to Release 6.0(6) and Higher Releases Fail with a Sign Error
Problem
If you upgrade from Release 1.0(3) to Release 6.0(6) or higher releases of Cisco Unified Presence, the system cannot authenticate the selected signed file and the upgrade fails. Similarly, an upgrade from Release 6.0(1) to Release 6.0(6) or higher releases of Cisco Unified Presence will fail.
Cause
This condition occurs if you are upgrading from:
•
•
Solution
•
•
Related Topics
New System Installation
For new installations, you must order the Cisco Unified Presence system software and licensing. Go to http://www.cisco.com/en/US/ordering/ or contact your Cisco sales representative.
Each Cisco Unified Presence shipment comes with an installation DVD, which is required for all new installations of a major software release of Cisco Unified Presence, for example, Cisco Unified Presence Release 6.0(1). The Cisco Unified Presence operating system and application software is installed from the installation DVD.
For new installations of the Cisco Unified Presence 6.0(x) application, use the DVD that indicates Cisco Unified Presence 6.0(x) Installation.
Related Topics
•
Upgrade from Cisco.com
Cisco does not support downloading major Cisco Unified Presence software releases from Cisco.com, for example, Cisco Unified Presence Release 6.0(1). From Cisco.com you can download upgrade-only software images that are used to upgrade from a previous major software release to a subsequent software point release of Cisco Unified Presence. For example, you can download Cisco Unified Presence Release 6.0(2) from Cisco.com.
To download this software, go to http://www.cisco.com/public/sw-center/sw-voice.shtml. You must have an account on Cisco.com to access the Software Center. The images posted at the Software Center require existing installations of Cisco Unified Presence.
Related Topics
•
•
The Latest Software Upgrades for Cisco Unified Presence on Cisco.com
Before You Begin
You can only download point releases of Cisco Unified Presence software from Cisco.com.
•
•
•
•
•
•
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(1) to 6.0(2)
Before You Begin
Review the requirements for the Cisco Unified Presence 6.0(2) Engineering Special, and additional software installation instructions.
Related Topics
Cisco Unified Presence Release 6.0(2) Engineering Special
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.2.1000-27.sgn.iso, has been
divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.2.1000-27.sgn.iso_part1of2 UCSInstall_UCOS_6.0.2.1000-27.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.2.1000-27.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.2.1000-27.sgn.iso_part1of2+UCSInstall_UCOS_6.0.2.1000-27.sgn.iso_part2of2 UCSInstall_UCOS_6.0.2.1000-27.sgn.iso
Step 3
•
Troubleshooting Tips
•
•
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(3)
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.3.1000-12.sgn.iso, has been
divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.3.1000-12.sgn.iso_part1of2 UCSInstall_UCOS_6.0.3.1000-12.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.3.1000-12.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.3.1000-12.sgn.iso_part1of2+UCSInstall_UCOS_6.0.3.1000-12.sgn.iso_part2of2 UCSInstall_UCOS_6.0.3.1000-12.sgn.iso
Step 3
•
Troubleshooting Tips
You can upgrade the iso image onto a remote server as an alternative to using the upgrade DVD. After you reunite the two files as documented in this procedure, copy the iso (UCSInstall_UCOS_6.0.3.1000-12.sgn.iso) to your FTP or SFTP server.
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(4)
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.4.1000-4.sgn.iso, has been
divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.4.1000-4.sgn.iso_part1of2 UCSInstall_UCOS_6.0.4.1000-4.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.4.1000-4.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.4.1000-4.sgn.iso_part1of2+UCSInstall_UCOS_6.0.4.1000-4.sgn.iso_part2of2 UCSInstall_UCOS_6.0.4.1000-4.sgn.iso
Step 3
•
Troubleshooting Tips
You can upgrade the iso image onto a remote server as an alternative to using the upgrade DVD. After you reunite the two files as documented in this procedure, copy the iso (UCSInstall_UCOS_6.0.4.1000-4.sgn.iso) to your FTP or SFTP server.
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(5)
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.5.1000-13.sgn.iso, has been
divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.5.1000-13.sgn.iso_part1of2 UCSInstall_UCOS_6.0.5.1000-13.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.5.1000-13.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.5.1000-13.sgn.iso_part1of2+UCSInstall_UCOS_6.0.5.1000-13.sgn.iso_part2of2 UCSInstall_UCOS_6.0.5.1000-13.sgn.iso
Step 3
•
Troubleshooting Tips
You can upgrade the iso image onto a remote server as an alternative to using the upgrade DVD. After you reunite the two files as documented in this procedure, copy the iso (UCSInstall_UCOS_6.0.5.1000-13.sgn.iso) to your FTP or SFTP server.
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(6)
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.6.1000-4.sgn.iso, has been divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.6.1000-4.sgn.iso_part1of2 UCSInstall_UCOS_6.0.6.1000-4.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.6.1000-4.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.6.1000-4.sgn.iso_part1of2+UCSInstall_UCOS_6.0.6.1000-4.sgn.iso_part2of2 UCSInstall_UCOS_6.0.6.1000-4.sgn.iso
Step 3
•
Troubleshooting Tips
You can upgrade the iso image onto a remote server as an alternative to using the upgrade DVD. After you reunite the two files as documented in this procedure, copy the iso UCSInstall_UCOS_6.0.6.1000-4.sgn.iso to your FTP or SFTP server.
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Accessing The Upgrade File for Cisco Unified Presence Release Release 6.0(x) to 6.0(7)
Because of its size, the original UCSInstall iso file, UCSInstall_UCOS_6.0.7.1000-5.sgn.iso, has been divided into two parts that you must download and reunite:
•
•
Procedure
Step 1
Step 2
a.
cat UCSInstall_UCOS_6.0.7.1000-5.sgn.iso_part1of2 UCSInstall_UCOS_6.0.7.1000-5.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.7.1000-5.sgn.iso
b.
COPY/B UCSInstall_UCOS_6.0.7.1000-5.sgn.iso_part1of2+UCSInstall_UCOS_6.0.7.1000-5.sgn.iso_part2of2 UCSInstall_UCOS_6.0.7.1000-5.sgn.iso
Step 3
•
Troubleshooting Tips
You can upgrade the iso image onto a remote server as an alternative to using the upgrade DVD. After you reunite the two files as documented in this procedure, copy the iso UCSInstall_UCOS_6.0.7.1000-5.sgn.iso to your FTP or SFTP server.
Related Topics
Image Extensions Can Cause Install Problems with Patch File Download
Additional Installation and Upgrade Considerations
•
How to Upgrade Your Hardware to Cisco Unified Presence Release 6.0(6) or a Higher 6.0(x) Release from Legacy Hardware Servers
You cannot directly upgrade to Cisco Unified Presence Release 6.0(6) from Cisco Unified Presence Release 1.0(3). We recommend that you upgrade to an intermediate 6.0(x) release of Cisco Unified Presence (Release 6.0(5) is best), and then upgrade that version to Release 6.0(6) or or a higher release of Cisco Unified Presence. This indirect upgrade path is for hardware migration purposes only. The platform will issue alerts to this effect.
If you upgrade from an unsupported hardware server to intermediate Cisco Unified Presence Release 6.0(5) as advised above, you will need to complete the following hardware migration:
1.
2.
3.
4.
In addition, you can check the Cisco Unified Presence Troubleshooter to determine if software is running on a supported hardware platform.
•
•
•
Prerequisites
Ensure you have the following prerequisites:
•
•
•
•
•
•
Note
Backing Up Data on an Unsupported Cisco Unified Presence1.0(3) server upgraded to 6.0(5)
Procedure
Step 1
a.
b.
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Step 7
Step 8
•
•
•
•
•
•
•
•
What To Do Next
Shutting Down the System
Procedure
Step 1
a.
b.
Step 2
Step 3
Step 4
a.
b.
Step 5
What To Do Next
Migrating Data To a Cisco Unified Presence 6.0(5) Server Installed on New Hardware
Migrating Data To a Cisco Unified Presence 6.0(5) Server Installed on New Hardware
Procedure
Step 1
a.
b.
Step 2
Step 3
Step 4
Step 5
Step 6
•
•
•
•
Step 7
Step 8
Step 9
Step 10
Step 11
Note
Step 12
Step 13
Step 14
Step 15
Step 16
What To Do Next
Restarting the System
Procedure
Step 1
a.
b.
Step 2
The Version Settings window displays and shows the software version on both the active and inactive partitions.
Step 3
What To Do Next
Uploading the License File
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
What To Do Next
Activating Feature Services
Procedure
Step 1
a.
b.
Step 2
Step 3
a.
b.
Step 4
Step 5
What To Do Next
Verifying System Configuration
Verifying System Configuration
Procedure
Step 1
a.
b.
Step 2
Cisco Unified Presence Release 6.0(2) Engineering Special
•
•
Resolved Caveats
CSCsl28100, CSCsl39615
Problem Description and Resolution
CSCsl28100 - In Cisco Unified Communications Manager 6.1, the User-Agent header format changed from "Cisco-CCMxx" to "Cisco-CUCMxx". Consequently, Cisco Unified Communications Manager 6.1 did not support the Do Not Disturb (DND) feature. The User-Agent header format is now changed to support devices in the DND state.
CSCsl39615 - If an administrator unlicensed a user in a remote cluster, the user's contact list information was not maintained. The intercluster sync agent in Cisco Unified Presence reported zero users for unlicensed users with contacts. Cisco Unified Presence now filters users who are not licensed, and the contact list of an unlicensed user is preserved.
Special Installation Instructions
Both the Cisco Unified Presence Release 6.0(2) Installation File and the Engineering Special must be installed to address the resolved caveats. After you install the Cisco Unified Presence Release 6.0(2) Installation File, upgrade to 6.0.2.1101.
For more information about performing a L2 upgrade, refer to the Cisco Unified Communications Operating System Maintenance Guide for Cisco Unified Presence.
Download File
Alternatively, access the file at this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cup-ES
New and Changed Behavior
None.
Limitations and Restrictions
Table 2 contains a list of caveats, now in Closed state, that describe possible unresolved behavior (limitations) in the latest Cisco Unified Presence release. These caveats may also be open in previous releases. Bugs are listed in order of severity and then in alphanumeric order by bug identifier.
Table 2 Closed Caveats for Cisco Unified Presence
3
database
Cannot login to GUI Admin, CUPC Authentication fail
New and Changed Information
•
•
•
•
Cisco Unified Presence Release 6.0(1)
The following sections describe new features and changes that are pertinent to Cisco Unified Presence, Release 6.0(1) or later. The sections may include configuration tips for the administrator, information about users, and where to find more information.
•
•
•
About Cisco Unified Communications Manager Alignment
To align with the new Cisco Unified Communications Manager 6.0(1) features, Cisco Unified Presence 6.0(1) includes the following enhancements.
•
SIP Publish
For Cisco Unified Presence Release 6.0(1), Cisco Unified Communications Manager can push the presence status to Cisco Unified Presence using a PUBLISH statement, instead of Cisco Unified Presence querying for it through backend subscriptions.
In Cisco Unified Presence Administration, the Presence Gateway settings associate the presence interface with the appropriate Cisco Unified Communications Manager SIP trunk.
In Cisco Unified Communications Manager Administration, you must configure the trunk as the Cisco Unified Presence Publish trunk. For more information, see the Cisco Unified Communications Manager Administration Guide.
Line Appearance Based Presence
For Cisco Unified Presence Release 6.0(1), Cisco Unified Presence bases presence status on line appearances rather than on the primary extension of the Cisco Unified Presence user. You can map line appearances to users in Cisco Unified Communications Manager Administration. Associate the end user with the line appearance (Device > Phone Configuration). From the Phone Configuration window, click the DN that the user will use to access the Cisco Unified Presence Server. Click the Associated End Users button. From the Find and List Users window, select an end user that will access the Cisco Unified Presence.
You can also use Bulk Administration in Cisco Unified Communications Manager Administration to migrate existing users to the line-appearance-based model. Bulk Administration includes the following options:
•
•
•
Do Not Disturb Status
Cisco Unified Communications Manager 6.0(1) includes DND Support for SIP Trunk PUBLISH. Because DND is device-based in release 6.0, if a device is changed to the DND state, all Cisco Unified Presence-enabled line appearances associated with this device could get published. When a device gets changed to the DND state, both DND as well as the busy/idle status will be published together to give Cisco Unified Presence more flexibility to process the data.
Mobile Phone Presence
Cisco Unified Presence now supports mobile presence status through Cisco Unified Communications Manager SIP PUBLISH. Presence information for mobile users can then be included in their overall reachability status. Cisco Unified Presence displays mobile phone status as a separate line appearance but will not display a separate directory number.
Cisco Unified Communications Manager only knows the status of a mobile phone that is registered within the enterprise; if the mobile is not registered, its status is published as available.
Cisco Unified Presence Features
To align with the new Cisco Unified Communications Manager 6.0(1) features, Cisco Unified Presence Release 6.0(1) includes the following features.
•
•
•
What's New Guide
The What's New in This Release pop-up window displays the first time you start Cisco Unified Presence 6.0(1). You can also access the What's New Guide by clicking the What's New link on the Cisco Unified Presence Administration window or by choosing Help > What's New.
The What's New Guide provides the following information:
•
•
•
To disable the What's New Guide pop-up window, check the Do not display this window at startup check box on the What's New Guide window.
Cisco Unified Communications Manager Navigation Link
For Cisco Unified Presence Release 6.0(1), the Administration main window displays a link directly to the associated Cisco Unified Communications Manager publisher server.
To open Cisco Unified Communications Manager Administration, click the Cisco Unified Communications Manager Publisher Address link.
End-User Privacy
To enhance privacy for the end user, Cisco Unified Presence 6.0(1) allows the user to configure customized presence rules on the User Options window. Select User Options > Privacy > Policies. Table 3 summarizes the available end-user privacy rules.
Calendar Integration with Microsoft Exchange
The Microsoft Exchange Calendar Integration feature allows an end user to include Microsoft Outlook calendar status information in their presence status. Cisco Unified Presence updates presence status based on the status shown in Microsoft Outlook calendar, such as busy or out-of-office. End users can configure calendar integration in the User Options window.
For more information on configuring Microsoft Exchange calendar integration, see the Cisco Unified Presence Deployment Guide.
Interclustering Support
Cisco Unified Presence Release 6.0(1) adds support for interclustering, which enables one Cisco Unified Presence cluster to route requests to user names and phone numbers on other Cisco Unified Presence clusters. This feature enables users on different clusters to watch presence status and send instant messages to users connected to a different cluster
IP Phone Messenger Meeting Notification with Microsoft Outlook
Cisco Unified Presence Release 6.0(1) supports meeting notifications from Microsoft Exchange Server. After you configure notifications, meeting reminders not only display on the email client of the user but also will get sent to an IPPM-enabled phone, which enables the user to join a conference by simply pressing the Join key.
When a user is in a conference call, the user can also see the meeting participants on their IPPM-enabled phone. Users do not need to be active on their desktop clients to receive meeting notifications as the notifications originate from the Exchange server. Users can disable this service if the user does not want to receive meeting notifications.
About Application Programming Interfaces
To align with the new Cisco Unified Communications Manager 6.0(1) features, Cisco Unified Presence 6.0(1) includes the following programming interfaces.
•
Unified Client Change Notifier (UCCN)
Cisco Unified Presence UCCN notifies the Cisco Unified Personal Communicator of changes to the provisioning data stored in the Cisco Unified Presence database.
The UCCN detects changes within the Cisco Unified Presence database and communicates those changes to the Cisco Unified Personal Communicator using a SIP Subscribe/Notify exchange. For more information, see the Cisco Unified Presence Interoperability Guide.
AXL Interface
For Cisco Unified Presence Release 6.0(1), Cisco Unified Presence adds Administrative XML Layer (AXL) commands for the following functions:
•
•
•
For more information, see the Cisco Unified Presence Interoperability Guide.
Cisco Unified Presence Release 6.0(2)
•
•
Support Status for Transport Layer Security (TLS) in SIP Trunk
TLS cannot be used to interface between Cisco Unified Presence Release 6.x and the Cisco Unified Communications Manager SIP trunk.
How to Configure Cisco Unified Presence for Integration with Microsoft Exchange 2007
Cisco Unified Presence requires an Exchange account with special permissions to query end-user calendaring data. The Exchange account must comply with the following minimum requirements:
1.
2.
Note
Perform these procedures on the Microsoft Exchange Server to create a Receive-As account.
•
•
•
Creating an Exchange Account with a Mailbox
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Introduction Window
Page 1 of 6
a.
b.
User Type Window
Page 2 of 6
a.
b.
User Information Window
Page 3 of 6
a.
b.
Mail Settings Window
Page 4 of 6
a.
b.
New Mail User Window
Page 5 of 6
a.
•
•
Completion Window
Page 6 of 6
a.
What To Do Next
Delegating Roles and Receive-As Permissions to the Exchange Account.
User Information Settings
Table 4 describes the user information configuration parameters.
Mailbox Settings
Table 5 describes the mailbox configuration parameters.
Delegating Roles and Receive-As Permissions to the Exchange Account
In order for Cisco Unified Presence to read Exchange calendaring data, it needs to use an Exchange account. The Exchange account must have "Receive-As" permission on all mailboxes. The Exchange account must also be an "Exchange View-Only Administrator" role."
Before You Begin
Complete the steps in Creating an Exchange Account with a Mailbox.
Procedure
Step 1
Step 2
Syntax
Add-ADPermission -Identity "Mailbox Store" -User "Trusted User" -ExtendedRights Receive-As
Example
Add-ADPermission -Identity "First Storage Group" -User CUPSAdmin -ExtendedRights Receive-As
Note
What To Do Next
Verifying Permissions on the Exchange Account.
Verifying Permissions on the Exchange Account
After you have assigned the permissions to the Exchange account, you need to verify that the permissions propagate to mailbox level, and you can access the mailbox of the end-user.
Note
Before You Begin
•
•
Procedure
Step 1
Step 2
a.
([ADSI]"LDAP://CN=CUPS Admin,CN=Users,DC=r7,DC=com").memberof
Note
b.
Example: Command Output
Step 3
a.
Get-ADPermission "First Storage Group" -user cupsadmin | Format-Table -AutoSize
Note
b.
Example: Command Output
- - - - - -- - - -- - - - -
Step 4
a.
Get-MailboxPermission jdoe -user cupsadmin | Format-Table -autosize
Note
b.
Example: Command Output
- - - - - -- - - -- - - - - - - -- - - - - - - -- - -{FullAccess}
Note
Cisco Unified Presence Release 6.0(3)
•
•
•
Recommended Best Practice for Microsoft Exchange 2007 Integration
Cisco recommends that the default SSL certificate, generated for Exchange on IIS, should use the Fully Qualified Domain Name (FQDN) of the Exchange server and be signed by a Certificate Authority that is trusted by Cisco Unified Presence. Configure the FQDN of the Exchange server in the:
•
•
Exchange Calendaring Using Forms-based Authentication (FBA)
Cisco Unified Presence release 6.0(3) supports the use of FBA with Microsoft Exchange 2003 and Microsoft Exchange 2007.
Related Topics
For more information on how to configure FBA for Outlook web access in Exchange 2007, see:
http://technet.microsoft.com/en-us/library/aa998867(EXCHG.80).aspx
New Data Field to Authenticate Microsoft Office Communicator Users At Login
Cisco Unified Presence allows users to log in to Microsoft Office Communicator using a new data field, that is, the value of the "msRTCSIP-primaryuseraddress" attribute from Active Directory.
Cisco Unified Presence sychronizes the data from Active Directory, and authenticates the user at login. This new data field will not effect any existing features or behavior.
As a prerequisite for this feature, ensure that Cisco Unified Presence is associated with Unified Communications Manager 6.1(3).
Cisco Unified Presence Release 6.0(5)
•
Licence Change for the Cisco Phone Control and Presence with IBM Lotus Sametime Application
A Cisco Unified Personal Communicator licence is no longer required to activate a user of the Cisco Phone Control and Presence with IBM Lotus Sametime application on Cisco Unified Presence. You now only need to assign one DLU, as a Cisco Unified Presence user, to activate a user of the Cisco Phone Control and Presence with IBM Lotus Sametime application.
Important Notes
•
•
•
•
•
•
•
About Cisco Unified Presence Release 6.0(1)
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Presence Release 6.0(1).
•
•
•
•
•
•
•
•
•
IP Address Change Unsupported After Installation
Cisco recommends that you do not attempt to change the IP address of the publisher server after installing Cisco Unified Presence, either in Cisco Unified Communications Operating System Administration or by using the Command Line Interface (CLI).
If you try to do this in Cisco Unified Communications Operating System Administration, the IP configuration of the server may be lost and Cisco Unified Presence may not function properly.
The only solution, if this occurs, is to reinstall Cisco Unified Presence.
You cannot use the set network ip command to reconfigure the IP address and netmask via the CLI. The command does not execute successfully because of a known issue with syntax and arguments.
No Status Displays For a Buddy
Problem
If you add a user who is not known to the local Cisco Unified Presence cluster to your buddy list, no status displays for the buddy. If that user then gets licensed in a remote cluster, the user displays in the local Cisco Unified Presence cluster but the clustering code does not update the appropriate settings to cause presence to start working for the user.
Solution
After the user has been licensed on the remote server, delete the user and add it again.
Microsoft Office Communicator Logins Fail
Problem
If you run a Microsoft Live Communication Server (LCS) and the Microsoft Office Communicator (MOC) feature of Cisco Unified Presence, after Cisco Unified Presence Release 1.0(3) is upgraded to Cisco Unified Presence Release 6.0(1), MOC logins for users fail.
Cause
This condition occurs when Cisco Unified Presence Release 1.0(3) that has the CTI gateway application status set to "On" is upgraded to Cisco Unified Presence Release 6.0(1).
Solution
Disable the CTI gateway application status setting then re-enable it.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Wait 5 minutes for data updates to complete. MOC logins should operate properly.
Cisco Unified Presence Server Upgrades
Configuration changes migrate only from older to newer versions of Cisco Unified Presence. If a Cisco Unified Presence server that has been upgraded and configured gets reverted to any previous Cisco Unified Presence release and upgraded again, any data configured in the server after the first upgrade, prior to the reversion gets erased.
Intercluster Code Cannot Determine the Correct Routing
If the same end user gets licensed for Cisco Unified Presence in two Cisco Unified Communications Manager clusters and if the two Cisco Unified Presence clusters paired with the Cisco Unified Communications Manager clusters are set up for intercluster, the intercluster code cannot determine the correct routing for the user. When the duplicate licensing is corrected, the Cisco Unified Presence clusters may not adjust appropriately.
Microsoft Office Communicator Call Forward Fails
Problem
When you use Microsoft Office Communicator to activate call forwarding on an IP phone that is logged in to extension mobility, call forwarding fails and you receive a visual indication that the operation has failed.
Cause
The Cisco Unified Communications Manager call forwarding settings get configured like this:
•
•
Solution
No workaround exists.
Server and Phone Support Information
Use this URL to find information about supported servers and phones:
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.htmlCisco Unified Presence Administration GUI Drop-Down Menus Display Cryptic Values
Problem
If you change the language selection on the browser before you load a valid localization package, the Cisco Unified Presence Administration GUI displays cryptic values in the drop-down menus.
Solution
To see the valid drop-down values, select the English locale. The drop-down values display enough information to allow you to make a selection.
IPPM Automatic Meeting Reminder Feature
Problem
If you enable or disable the IPPM automatic meeting reminder feature on the End User > Preference menu, you should log out and then log in for the change to take effect.
Solution
In addition to the information above regarding logging out and then logging in, you can also enable or disable the meeting notification feature by using the user desk phone.
About Cisco Unified Presence Release 6.0(2)
•
•
•
•
•
CTI Gateway Authentication against Cisco Unified Communications Manager is Case-Sensitive
Problem
Application users with CTI privileges are configured with case-sensitive User IDs on Cisco Unified Communications Manager. Capital letters, lowercase letters, or a combination of both may be used. CTI Gateway application users must have identical usernames and passwords configured on both Cisco Unified Presence and Cisco Unified Communications Manager. This condition applies to all versions of Cisco Unified Presence.
Solution
When you configure CTI Gateway settings on Cisco Unified Presence, ensure that you enter the exact same application CTI Gateway username and password that you configured on Cisco Unified Communications Manager.
IBM SameTime Click-to-Call Support Information
Use this URL to find end-user support information for SameTime version 7.5, the IBM Lotus instant messaging client:
http://www-1.ibm.com/support/docview.wss?rs=477&uid=swg21195515
Allowed ACL Formats
Cisco Unified Presence accepts a range of IP address patterns in addition to a fully qualified name of an incoming host or domain. The Allow directive followed by "from" determines which hosts can access the server.
When configuring incoming and outgoing ACL settings, you can choose from the following formats:
Table 6 ACL Address Patterns
Exchange Server Updates
You should ensure that your Exchange Server has the latest updates installed. Servers should be running the latest Service Packs for both Windows Server 2003 (currently SP2) and Microsoft Exchange 2003 (currently SP2).
Problem
If you encounter problems with the exchange server and it returns a "500 Internal Server Error", check that Microsoft HotFix KB841561 has been applied to your Microsoft Exchange 2003 Server.
Solution
Apply Microsoft HotFix KB841561.
Procedure
Step 1
Step 2
Step 3
Step 4
440 Login Timeout Errors
Problem
If the Microsoft Exchange 2003 Server has Form-Based Authentication (FBA) enabled, there is a possibility that the Exchange Server will reject calendar transactions with the error "440 Login Timeout".
Solution
To avoid these errors, disable FBA on the Exchange server.
Cisco Unified Presence Administration GUI Drop-Down Menus are Inaccessible
Problem
If you use version 6.x of Internet Explorer to log into the Cisco Unified Presence Administration GUI, the GUI drop-down menus may be disabled after you log in.
Cause
This condition occurs when the Cisco Unified Presence server is not recognized as a trusted site.
Workaround
Add the Cisco Unified Presence server hostname to the list of trusted sites.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Intercluster Code Can Determine the Correct Routing
In Cisco Unified Presence Release 6.0(2), the intercluster code can determine the correct routing for the user even if the same end user gets licensed for Cisco Unified Presence in two Cisco Unified Communications Manager clusters, and if the two Cisco Unified Presence clusters paired with the Cisco Unified Communications Manager clusters are set up for intercluster. When the duplicate licensing is corrected, the Cisco Unified Presence clusters will automatically adjust appropriately.
Call Forwarding Status Not Updating in Microsoft Office Communicator
Problem
When you forward a call to another extension from an IP phone, the enabled Microsoft Office Communicator client for this phone may not recognize the forwarding change. In Microsoft Office Communicator, you receive a visual indication that the operation has failed with the message "Call Forwarding: OFF".
Cause
This condition occurs when initiating Call Forwarding from an IP phone device.
Solution
To have both the Microsoft Office Communicator client and the phone recognize the forwarding change, forward the call using Microsoft Office Communicator.
Presence Update Delay on Cisco Unified Personal Communicator if the Reverse Lookup Scope is Missing
Problem
It takes approximately five seconds for presence status to update on Cisco Unified Personal Communicator.
Cause
This is due to DNS failures on the route lookup.
Solution
DNS must be configured in both directions in order to verify that the ACL is trusted. Add the reverse lookup entry for the Cisco Unified Personal Communicator subnet on the DNS server.
About Cisco Unified Presence Release 6.0(3)
•
•
•
•
Synchronizing Cisco Unified Communications Manager (Business Edition) with Cisco Unified Presence via LDAP
Problem
Cisco Unified Communications Manager (Business Edition) can be used with Cisco Unified Presence 6.x; however, Cisco Unified Communications Manager (Business Edition) 6.x does not currently support LDAP synchronization or authentication.
Cause
Cisco Unified Presence gets user information from Cisco Unified Communications Manager. The Cisco Unified Communications Manager user database can be populated one of two ways, either via manual configuration or via an LDAP synchronization. Since Cisco Unified Communications Manager (Business Edition) does not support an LDAP synchronization, the users have to be populated manually to ensure the user ID in LDAP is consistent with the configuration in Cisco Unified Communications Manager.
Solution
Users of Cisco Unified Communications Manager (Business Edition) must be configured to match the users configured in LDAP (first and last name, user ID, and directory number) and to avoid any potential mismatch of user information when using Cisco Unified Personal Communicator.
Note
Switching UDP Requests to TCP
Problem
Cisco Unified Presence SIP proxy is hard-coded to use TCP for larger SIP packets (greater or equal to 1300 bytes) even if the request was intended for UDP. This also applies for Static Routes and Method/Event Routes even if UDP is configured as the specified transport in the Cisco Unified Presence Administration.
Cause:
The SIP proxy upgrades outbound UDP requests to TCP if the packet size exceeds 1300 bytes. The switch from UDP to TCP occurs, by default, if the packet size is 1300 bytes or larger. You can configure the transport type to change for any packet size between 0-65535 bytes.
Solution
This system behavior is in compliance with RFC 3261.
Sync Agent Test in System Configuration Troubleshooter
Problem
The System Troubleshooter performs a test to compare the current version of Cisco Unified Communications Manager with the version stored in the Cisco Unified Presence database, and restarts the SyncAgent if Cisco Unified Communications Manager has been upgraded. However, until the SyncAgent successfully executes at least one time, the System Troubleshooter will continue to report AXL connectivity issues with Cisco Unified Communications Manager.
Cause
This condition occurs when the SyncAgent retrieves the Cisco Unified Communications Manager version and stores it in the Cisco Unified Presence database. The Cisco Unified Communications Manager version in the Cisco Unified Presence database remains set to NULL until the SyncAgent runs successfully at least one time.
Solution
No workaround exists.
Reverse Look-up of International Dial Plans in E. 164 Format
Problem
A reverse look-up of a directory number to username will not work under these conditions:
•
•
•
•
Under these conditions, the application identifies the call as coming from an extension number, and the username will not display in Microsoft Office Communicator.
Cause
Microsoft Office Communicator has a Reverse DN Lookup capability to:
•
•
Solution
Set up the correct normalization rules for the AD address book on the Microsoft Office Communicator server, and then complete your setup and verification on the MOC client as follows:
Before you Begin
The CA-signed certificate for the OCS needs to be on the Microsoft Office Communicator PC to achieve correct certificate distribution for address book synchronization. If a common CA is used to sign certificates, for example Verisign or RSA, the CA certificate may already come installed on the PC.
Procedure
Step 1
C:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Files\Company_Phone_Number_Normalization_Rules.txt
Tip
Step 2
C:\Program Files\Microsoft Office Communications Server 2007\Server\Core>Abserver.exe -regenUR
Note
Step 3
C:\Program Files\Microsoft Office Communications Server 2007\Server\Core>ABServer.exe -syncnow
Note
Step 4
Step 5
C:\Program Files\Microsoft Office Communications Server 2007\Server\Core>Abserver.exe -testPhoneNorm <E164 phone number>
What To do next
Follow this procedure to verify that the user is able to see name of the calling party in the popup window that displays when the call is made.
Complete this setup on the MOC client:
Procedure
Step 1
Step 2
C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\Communicator
Step 3
Step 4
Step 5
Troubleshooting Tips
Sample Normalization rules follow:
# ++ test RTP## PSTN:+61262637900, Extension:37XXX# +61262637ddd[\s()\-\./\+]*(61)?[\s()\-\./]*0?(2)\)?[\s()\-\./]*(6263)[\s()\-\./]*(7\d\d\d)3$4;phone-context=dialstring# ++ test1 RTP## Site:, PSTN:+61388043300, Extension:33XXX[\s()\-\./\+]*(61)?[\s()\-\./]*0?(3)\)?[\s()\-\./]*(8804)[\s()\-\./]*(3\d\d\d)3$4;phone-context=dialstring#Test input +61388043187, Test result-> tel:33187;phone-context=dialstring# ++ test2 RTP## PSTN:+61292929000, Extension:29XXX[\s()\-\./\+]*(61)?[\s()\-\./]*0?(2)\)?[\s()\-\./]*(9292)[\s()\-\./]*(9\d\d\d)2$4;phone-context=dialstring# Test input +61292929761, test result-> tel:29761;phone-context=dialstringDuplicate Users in Cisco Unified Presence Limited to 250 Records
Problem
In Cisco Unified Presence, the Duplicate User List only displays the first 250 records.
Cause
Configure an intercluster Cisco Unified Presence environment that contains more than 250 duplicate users licensed to multiple Cisco Unified Presence servers.
a.
b.
Only the first 250 duplicate users are displayed. The UI does not display User 251 and higher.
Solution
Using the Platform CLI on Cisco Unified Presence, run the following command:
run sql select unique c.userid, c.peerid pub from cupsuserlocation c, cupsuserlocation d where c.userid=d.userid and d.peerid!=c.peerid
This command reports the duplicate user and the publisher of the cluster to which the user has been licensed. If the value of "local" returns for the publisher, that user is licensed on the local Cisco Unified Presence cluster associated with the SQL query.
About Cisco Unified Presence Release 6.0(4)
•
•
Call Transfer Fails Via SIP Proxy
Problem
When a call is transferred, the SIP Proxy routes a mid-call Invite message. The Request URI incorrectly updates to match the next hop address and does not maintain the contact address of the endpoint. As multiple hops are traversed, the call transfer fails after 30 seconds.
Cause
This condition occurs when a call is a transfer call. The issue could also occur on a direct call, when a re-invite message updates the session timer.
Solution
No workaround exists.
Release 6.0(3) to 6.0(4) Upgrade of Cisco Unified Presence Does Not Preserve CA Certificate
Problem
Integration betweenCisco Unified Presence and the Microsoft Exchange server does not work after you upgrade from Cisco Unified Presence Release 6.0(3) to 6.0(4).
Cause
This condition occurs because the CA certificate that was uploaded via the backend Presence Gateway window is not preserverd during an upgrade of Cisco Unified Presence from Release 6.0(3) to 6.0(4).
Solution
Re-upload the CA certificate without the subject Common Name (CN) in the backend Presence Gateway page. This ensures that the Exchange certificate will be signed.
About Cisco Unified Presence Release 6.0(5)
•
•
•
•
•
•
•
Image Extensions Can Cause Install Problems with Patch File Download
Problem
When the Cisco Unified Presence upgrade patch file is downloaded from cisco.com, some browsers may download files with the extension tar.gz.sgn as tar.gz.gz. The .gz.gz file cannot be successfully installed.
Cause
This condition occurs if you use Internet Explorer or Opera browsers to download the signed Cisco Unified Presence patch file from cisco.com.
Solution
After the patch file is downloaded, rename it with the extension .gz.sgn (in place of.gz.gz) and proceed with the install. Alternatively, use a Mozilla-based browser such as Firefox (any version) to download the patch file.
AXL executeSQLQuery Request Hangs or Fails on Large Request
Problem
If an AXL executeSQLQuery is sent that returns a large data set (greater then 16 MB), it can cause the Tomcat web server to hang or to reject the request.
Cause
This condition occurs when an AXL executeSQLQuery is sent that returns a data set that contains a large number of rows in a database table.
Solution
Retrieve the data in chunks using the format "select skip X first Y * from table".
Cisco Unified Presence Engine Database Service is not Correct in SYSAPPL-MIB
Problem
No valid SNMP management information is available for the Cisco Unified Presence Engine Database service beyond the basic sysApplInstallPkgProductName.
Cause
This condition occurs in a basic Cisco Unified Presence configuration with SNMP enabled.
Solution
No workaround exists.
Sync Agent Fails to Synchronize Data from Cisco Unified Communications Manager
Problem
If large queries are being sent to Cisco Unified Communications Manager via AXL, the Cisco Unified Presence Sync Agent can fail to synchronize data from Cisco Unified Communications Manager. In some cases the AXL request from the Sync Agent will hang and in others it will receive this error: "Maximum AXL Memory Allocation Consumed".
Cause
This condition occurs when the Sync Agent synchronizes data from Cisco Unified Communications Manager while large AXL queries are being sent to Cisco Unified Communications Manager.
Solution
Restart the Sync Agent.
Config Agent Static routes Do Not Update Correctly
Problem
Static routes send messages to a wrong (previously entered) address.
Cause
If a customer changes a static route, while the config-agent is down, the route will be updated in the database but not on the server. The server will continue to use the previous setting.
Solution
First enable Routing debugs and examine the logs. If routing to the address does not match the current configuration, you must:
•
•
•
IPPM : XML Parse Error when showing Message History
Problem
After receiving a message in Japanese, an XML Parse Error may occur when showing the Message History (IPPM Service -> Messages).
Cause
This problem may occur for languages other than English, in this setup environment:
•
•
•
Solution
No workaround exists.
MOC Call Transfers to External Destinations Fail
Problem
The CTI call transfer request that Cisco Unified Presence uses to relay from MOC to Cisco Unified Communications Manager is empty. As a result, the call transfer via MOC fails.
Cause
This occurs in the following conditions:
•
•
•
Solution
No workaround exists.
Disabling DNS and Reverse DNS Lookup on Cisco Unified Presence for CVP integration
Problem
Reverse DNS lookup queries on Cisco Unified Presence may take longer to process if there are network issues or problems with the DNS server. Delays can occur if you do not use DNS, or IP addresses, in your Cisco Unified Presence and CVP environment.
Cause
The delay occurs because Cisco Unified Presence continues to wait for a response from the DNS server.
Solution
If you are not using DNS in your network configuration, do not adda DNS entry on Cisco Unified Presence. Perform the following actions to disable Reverse DNS lookup:
•
•
•
About Cisco Unified Presence Release 6.0(6)
Upgrade from Cisco Unified Presence Releases 1.0(3) and 6.0(1) to Release 6.0(6) Fail with a Sign Error
For more information, see Supported Upgrade Paths to Cisco Unified Presence Release 6.0(x).
About Cisco Unified Presence Release 6.0(7)
Upgrade from Cisco Unified Presence Releases 1.0(3) and 6.0(1) to Release 6.0(7) Fail with a Sign Error
For more information, see Supported Upgrade Paths to Cisco Unified Presence Release 6.0(x).
Caveats
Using Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:
•
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
Before You Begin
•
–
–
–
Procedure
Step 1
Step 2
Step 3
Note
Open Caveats
The caveats in Table 7 describe possible unexpected behavior in the latest Cisco Unified Presence release. These caveats may also be open in previous releases. Bugs are listed in order of severity and then in alphanumeric order by bug identifier.
Table 7 Open Caveats for Cisco Unified Presence
Resolved Caveats
This section lists caveats that are resolved but that may have been open in previous releases.
Bugs are listed in order of severity and then in alphanumeric order by bug identifier. Because defect status continually changes, be aware that this document reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access the Bug Toolkit (see the "Using Bug Toolkit" section).
•
•
•
•
•
•
Cisco Unified Presence Release 6.0(2)
Table 8 lists caveats that are resolved in Cisco Unified Presence Release 6.0(2) but that may have been open in previous releases.
Table 8 Resolved Caveats for Cisco Unified Presence
Cisco Unified Presence Release 6.0(3)
Table 9 lists caveats that are resolved in Cisco Unified Presence Release 6.0(3) but that may have been open in previous releases.
Table 9 Resolved Caveats for Cisco Unified Presence
Cisco Unified Presence Release 6.0(4)
Table 10 lists caveats that are resolved in Cisco Unified Presence Release 6.0(4) but that may have been open in previous releases.
Table 10 Resolved Caveats for Cisco Unified Presence
Cisco Unified Presence Release 6.0(5)
Table 11 lists caveats that are resolved in Cisco Unified Presence Release 6.0(5) but that may have been open in previous releases.
Table 11 Resolved Caveats for Cisco Unified Presence
Cisco Unified Presence Release 6.0(6)
Table 12 lists caveats that are resolved in Cisco Unified Presence Release 6.0(6) but that may have been open in previous releases.
Table 12 Resolved Caveats for Cisco Unified Presence
4
vos
Port CSCsr74305 ntp_one_shot.sh intermittently kills wrong processes
Cisco Unified Presence Release 6.0(7)
Table 13 lists caveats that are resolved in Cisco Unified Presence Release 6.0(7) but that may have been open in previous releases.
Table 13 Resolved Caveats for Cisco Unified Presence
Documentation Updates
•
•
•
Cisco Unified Presence Release 6.0(1)
This section provides documentation changes that were unavailable when the Cisco Unified Presence Release 6.0(1) documentation suite was released.
Omissions
This section contains information that may have been left out of the documentation for Cisco Unified Presence Release 6.0(1).
Intercluster Peers
The following two parameters apply to the Intercluster Peers chapter of the Cisco Unified Presence Administration Guide:
•
•
Errors
This section contains information about inaccuracies in the documentation for Cisco Unified Presence Release 6.0(1).
IP Phone Messenger Settings
The IP Phone Messenger Settings chapter in the Cisco Unified Presence Administration Guide incorrectly lists the following two parameters, which are not available in Cisco Unified Presence 6.0(1):
•
•
Cisco Unified Presence Release 6.0(2)
This section provides documentation changes that were unavailable when the Cisco Unified Presence Release 6.0(1) documentation suite was released.
Omissions
This section contains information that may have been left out of the documentation for Cisco Unified Presence Release 6.0(1).
Proxy Static Routes Precedence
The following example should be added to the Static Routes chapter of the Cisco Unified Presence Administration Guide to clarify how the priority and weight associated with a route determines precedence.
Consider these three routes with associated priorities and weights:
•
•
•
In this example, the static routes are listed in the correct order. The priority route is based on the lowest value priority, that is 1. Given that two routes share the same priority, the weight parameter with the highest value decides the priority route.
Required User permissions for Intercluster Peer Configuration
Problem
Permissions required for the Cisco Unified Presence intercluster peer user are not documented in the Intercluster Peers chapter of the Cisco Unified Presence Administration Guide.
Solution
The administrator can grant allowed permissions based on user roles. If necessary, add SuperUser permissions to the user assigned as the Cisco Unified Presence intercluster peer in Cisco Unified Communications Manager.
Configuration Troubleshooter: Interclustering Test
The following Intercluster test applies to the Configuration Troubleshooter chapter of the Cisco Unified Presence Administration Guide:
Problem
One or more users are licensed in more than one Cisco Unified Presence cluster. This causes inconsistent presence and instant message routing.
Solution
Determine the true cluster to which each of the duplicate users belongs. Investigate which of the Cisco Unified Communications Manager clusters associated with the Cisco Unified Presence cluster has the user incorrectly licensed for Cisco Unified Presence.
Intercluster Peer Duplicates Navigation Link
There is an additional hyperlink description that should be added to the Status chapter of the Cisco Unified Presence Administration Guide. The Cisco Unified Presence System Status window displays a link when end users associated with an intercluster peer are duplicated.
To view the duplicate users, click the X Duplicates found link.
Uploading Microsoft Exchange Certificates
The following should be added to the "Exchange Calendar Integration Configuration" section of the Cisco Unified Presence Deployment Guide.
Cisco Unified Presence Release 6.0(2) allows you to upload Exchange server trust certificates with or without a Subject Common Name (CN).
•
•
•
Note
Uploading CA-Signed Certificates
The following step should be added to the "Configure the Security Certificate" section of the Cisco Unified Presence Deployment Guide. To complete the certificate exchange process, the user must upload the signed certificate to the Cisco Unified Presence server after uploading it to the CA server.
When you upload a signed certificate to Cisco Unified Presence, you must state the root certificate name by specifying the.PEM filename as it appears in the certificate list.
Procedure
Step 1
Step 2
Step 3
Note
Step 4
a.
b.
Step 5
Step 6
Step 7
Step 8
a.
b.
Step 9
How to Configure the LCS Certificate Chain
The LCS certificate configuration process should be added to the Microsoft Integration Overview chapter of the Cisco Unified Presence Deployment Guide.
To configure an LCS certificate on the LCS server, complete the following tasks:
•
•
•
•
Downloading a CA Certification Chain
Procedure
Step 1
a.
b.
c.
Step 2
Step 3
Step 4
Troubleshooting Tips
Step 5
•
•
Installing a CA Certification Chain
Procedure
Step 1
a.
b.
c.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
a.
b.
Step 8
Step 9
Step 10
Step 11
Step 12
a.
b.
c.
Step 13
Step 14
a.
b.
c.
Step 15
Step 16
Step 17
Step 18
Requesting a Certificate
Procedure
Step 1
a.
b.
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Step 7
Note
Step 8
Step 9
Step 10
Step 11
Manually Approving a Certificate Issuance Request
Procedure
Step 1
Step 2
a.
b.
c.
Step 3
Step 4
Step 5
a.
b.
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
a.
b.
c.
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
a.
b.
Step 19
a.
b.
Uploading Supported x509 Certificates
The following x509 formats for user-uploaded certificates should be added to the Security chapter of the Cisco Unified Communications Operating System Administration Guide.
SIP Proxy and Presence Engine certificates (own and trust) should be X.509 version 3 compliant. Tomcat certificates (own and trust) should be X.509 version 1 compliant.
Enabling and Disabling Empty TLS Fragments
There is an additional checkbox description that should be added to the TLS Context Configuration chapter of the Cisco Unified Presence Administration Guide. The TLS Configuration window displays a checkbox that allows users to enable or disable empty TLS fragments.
The checkbox is checked by default.
Managing Live Communications Server (LCS) Security Certificates
The certificate exchange process between Cisco Unified Presence and LCS should be added to the Cisco Unified Presence Configuration Overview chapter of the Cisco Unified Presence Deployment Guide.
Step 1
Download the root certificate
a.
b.
–
c.
d.
e.
f.
Note
Step 2
Upload the root certificate into the trust store of the Cisco Unified Presence server.
a.
b.
•
•
c.
d.
e.
f.
g.
h.
Step 3
Generate a CSR for Cisco Unified Presence on the Cisco Unified Presence server.
a.
b.
c.
d.
Step 4
Download the CSR from the Cisco Unified Presence server.
a.
b.
c.
d.
e.
Step 5
Have the root trust of the MS CA sign the CSR
a.
b.
http://local-server/certserv
or
http://127.0.0.1/certsrv
c.
d.
e.
f.
g.
-----BEGIN CERTIFICATE REQUEST
to and including
END CERTIFICATE REQUEST-----
h.
i.
j.
k.
•
•
l.
m.
Step 6
Download the signed certificate.
a.
b.
–
–
c.
d.
e.
f.
g.
h.
i.
j.
k.
Step 7
Upload the signed certificate tothe Cisco Unified Presence server as a sipproxy-trust certificate.
Step 8
Configure the LCS certificate installed on the LCS server.
See the "How to Configure the LCS Certificate Chain" section.
Step 9
Configure FIPS-compliant algorithms on the LCS server
Configure the LCS server to send TLSv1 with TLS cipher TLS_RSA_WITH_3DES_EDE_CBC_SHA:
a.
b.
c.
•
•
d.
e.
Step 10
Create a new TLS-PEER Subject on the Cisco Unified Presence server
a.
–
–
b.
c.
d.
e.
f.
g.
Step 11
Add the newly created TLS Peer to the Selected TLS Peer Subjects list.
a.
b.
c.
d.
e.
f.
g.
h.
Step 12
Configure the incoming ACL.
a.
b.
c.
d.
Step 13
Restart the SIP Proxy service.
a.
b.
c.
Office Communications Server 2007 Support
Cisco Unified Presence Release 6.0(2) adds support for Microsoft Client mode (CSTA Integration) with Office Communications Server 2007.
Use this URL to find information about integrating Cisco Unified Presence with Office Communications Server 2007:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/6_0/pbxint/617030nt.pdfThe parameters that are required for Microsoft Office Communications Server 2007 have changed names from Live Communications Server 2005. The TEL URI parameter, defined in Live Communications Server 2005, is the same as the Line URI parameter in Office Communications Server 2007. The Remote Call Control SIP URI parameter, defined in Live Communications Server 2005, is the same as the Server URI parameter in Office Communications Server 2007.
Errors
This section contains information about inaccuracies in the documentation for Cisco Unified Presence Release 6.0(1).
Message Reply in IP Phone Messenger
Problem
The Sending Messages section of the Cisco IP Phone Messenger Guide incorrectly suggests that you can use the Msg softkey on the phone to reply to a person who is not in your contact list.
The Msg softkey does not display unless the sender of the message is in the contact list of the receiver.
Solution
To reply to a message using the Msg softkey, add the person who sent the message to your contact list.
Root Certificate URL
Problem
The Microsoft Integration Overview chapter in the Cisco Unified Presence Deployment Guide directs users to an incorrect URL to download a root certificate:
•
Solution
Open the following URL to download a root certificate:
•
Root Certificate Upload Procedure
The Microsoft Integration Overview chapter in the Cisco Unified Presence Deployment Guide contains an obsolete step in the procedure that describes how to upload the root certificate to the Cisco Unified Presence Server.
Step 7 can be ignored.
Cisco Unified PresenceTrust Certificate Filename
The Microsoft Integration Overview chapter in the Cisco Unified Presence Deployment Guide does not accurately describe the Trust Certificate Subject CN (Outlook Only) field.
If the CN that you enter contains a space, the space is replaced with an underscore when naming the certificate. During the upload process, a CN of "CA Server," for example, would equate to entering "CA_Server" in the Trust Certificate Subject CN field.
Incorrect Procedure Sequence
The Microsoft Integration Overview chapter in the Cisco Unified Presence Deployment Guide lists the following procedures in an incorrect order:
•
•
The procedure that describes how to configure the security certificate on the Cisco Unified Presence Server needs to be completed before a presence gateway can be configured on the server. Some of the data fields necessary for the presence gateway are not known until the CA server is installed.
Cisco Unified Presence Upgrade Considerations
The Software Upgrades chapter in the Cisco Unified Communications Operating System Administration Guide should state that existing configuration data is not overwritten in an upgrade to Cisco Unified Presence 6.0(1) or later. Once you upgrade to version 6.0(1), you can switch to the new version without reconfiguring your data.
Cisco Unified Presence Release 6.0(3)
This section provides documentation changes that were unavailable when the Cisco Unified Presence Release 6.0(1) documentation suite was released.
Omissions
This section contains information that may have been left out of the documentation for Cisco Unified Presence Release 6.0(1) or 6.0(2).
Cisco Unified Communications Manager CtiGw Application User Name is Case Sensitive
The caveat referred to above should be added to the Cisco Unified Presence Administration Guide and the Cisco Unified Presence Deployment Guide.
Related Topics
CTI Gateway Authentication against Cisco Unified Communications Manager is Case-Sensitive
Restarting the SIP Proxy to Complete Installation of Second Node
You must restart the SIP Proxy service after you configure the second node in a Cisco Unified Presence cluster.
This additional step should be documented as the final step in the "Configuring the Second Node" section of the Installing Cisco Unified Presence Guide.
Cisco Unified MeetingPlace Express Unsupported in Cisco Unified Presence
Cisco Unified Presence does not support Cisco Unified MeetingPlace Express. This should be stated in the Meeting Notifications chapter of the Cisco Unified Presence Administration Guide and the chapter in the Cisco IP Phone Messenger for Cisco Unified Presence Guide that describes Reviewing and Rejoining Meetings.
Configuration of SSL Security Certificate for Meeting Notifications
As you configure meeting notification settings in Cisco Unified Presence Administration, you can check Use SSL to specify that the connection to Cisco MeetingPlace will use transport layer security (TLS). The Meeting Notifications chapter of the Cisco Unified Presence Administration Guide should include a hyperlink that points users to the security certification configuration procedures, as described in the Microsoft Integration chapter of the Cisco Unified Presence Deployment Guide.
Errors
This section contains information about inaccuracies in the documentation for Cisco Unified Presence Release 6.0(2).
Installing CA on the Exchange Server
The Microsoft Integration Overview chapter in the Cisco Unified Presence Deployment Guide informs users not to install the CA service on the same computer that is running the Exchange server.
This information note is incorrect. The CA can be installed on the Exchange server.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
© 2010 Cisco Systems, Inc. All rights reserved.
