Table Of Contents
DLUs Required for Cisco Unified Communications Manager 6.1(4) and 6.1(3)
Cisco Unified IP Phone Requirements
Audio Codecs for Use with Cisco UC Integration for Microsoft Office Communicator
Tips for Searching Cisco Documentation
Restart of Conversation Pane Required If Windows Security Fails
Docking, Undocking, Hibernating, Resuming, and Suspending Client Computers
Mute Microphone Keyboard Shortcut Performs Graphics Action
Updating Availability Status from Microsoft Outlook Calendar
Microsoft PowerPoint 2007 Support
Conference Calls Between Users in Different Clusters
Numbers Published by Users in Microsoft Office Communicator Not Recognized
Conversation Pane Menu Items Available But Not Functional
Cisco Unified Communications Manager 6.1(3) and Conference Participant Lists
Availability Status Transitions
Availability Status and Cisco Unified Presence
Partial Support for Multiple Lines
Call Control on Cisco Unified IP Phone 9900, 8900, and 6900 Model Series
Adding Users to the Standard CTI User Groups
Setting Logging Levels Before You Create a Problem Report
Cisco IP Communicator Listed as a Desk-Phone Device
QoS Packet Marking on Windows Vista
Enabling Packet Marking for CSF on Cisco Unified Communications Manager
Enabling Packet Marking for CSF with Active Directory 2008 on Windows Vista
Support for Microsoft Business Productivity Online Standard Suite
Requirements for Using Cisco UC Integration for Microsoft Office Communicator with BPOS
Architecture of Cisco UC Integration for Microsoft Office Communicator in a BPOS Environment
User Phone Numbers Must Use +E.164 Formatting
Microsoft Office Communicator 2007 R1
Microsoft Office Communicator 2007 R2
Location of Custom Availability Statuses File
Differences Between English-Language and Translated User Documentation
Corrections to User Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Integration for Microsoft Office Communicator Release 7.1
July 13, 2010
These release notes describe features and caveats for all versions of Cisco UC Integration for Microsoft Office Communicator Release 7.1.
To access the latest software upgrades for all versions of Cisco UC Integration for Microsoft Office Communicator, go to:
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=282588075
Contents
•
Obtaining Documentation and Submitting a Service Request
Introduction
These release notes describe requirements, restrictions, and caveats for Cisco UC Integration for Microsoft Office Communicator Release 7.1. These release notes are updated for every maintenance release but not for patches or hot fixes.
Before you install Cisco UC Integration for Microsoft Office Communicator, review this document for information about issues that might affect your system. For a list of the open caveats, see Open Caveats.
System Requirements
•
Network Requirements
Table 1 Ports Used for Inbound Traffic by Cisco Unified Client Services Framework
16384-32766
UDP
Receives Real-Time Transport Protocol (RTP) media streams for audio and video. These ports are configured in Cisco Unified Communications Manager. For more information about device configuration files, see the Cisco Unified Communications Manager System Guide:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Server Requirements
DLUs Required for Cisco Unified Communications Manager 6.1(4) and 6.1(3)
Note
Client Computer Requirements
Hardware Requirements
Tested Audio Devices
The audio devices tested with Cisco UC Integration for Microsoft Office Communicator are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
Software Requirements
Note
Cisco Unified IP Phone Requirements
Table 7 lists the Cisco Unified IP Phone models that are supported for Cisco UC Integration for Microsoft Office Communicator, and whether Skinny Call Control Protocol (SCCP) and Session Initiation Protocol (SIP) are supported:
Note
Audio Codecs for Use with Cisco UC Integration for Microsoft Office Communicator
A codec is an implementation of an algorithm capable of performing encoding and decoding on a digital data stream. Codecs are used to encode and decode data, such as sound and video streams, that would otherwise use large amounts of network bandwidth when transmitted or disk space when stored.
You can use the following codecs with Cisco UC Integration for Microsoft Office Communicator:
•
•
•
•
About Voice Quality
Cisco UC Integration for Microsoft Office Communicator is designed to provide premium voice quality under a variety of conditions; however, in some instances users may notice interruptions of audio transmission or temporary audio distortions ("Artifacts") which are considered a normal part of the operation of the application.
These artifacts should be infrequent and temporary when using:
•
•
We take reasonable measures to interface with the operating system in ways that decrease the likelihood that other applications running on the system will interfere with softphone audio and video quality. However, the shared nature of system environments in which these products run is very different than a closed environment like Cisco Unified IP Phones and we cannot guarantee equivalent performance.
The following are some conditions that may cause artifacts:
•
•
•
•
•
•
Avoiding or recovering from the conditions previously listed will help minimize audio distortion artifacts.
Finding Documentation
Provide the following URL to your users:
http://www.cisco.com/en/US/products/ps10317/products_user_guide_list.html
For a complete list of documents, see the Documentation Guide for Cisco Unified Communications Integration for Microsoft Office Communicator at http://www.cisco.com/en/US/products/ps10317/products_documentation_roadmaps_list.html.
Cisco Unified Communications Manager Documentation
Refer to the Cisco Unified Communications Manager Documentation Guide and other publications specific to your Cisco Unified Communications Manager release. Navigate from the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Cisco Unified IP Phone Documentation
Refer to publications that are specific to your language, phone model, and Cisco Unified Communications Manager release. Navigate from the following URL:
http://www.cisco.com/cisco/web/psa/maintain.html?mode=prod&level0=278875240
Tips for Searching Cisco Documentation
We recommend using the external Google Search (http://www.google.com) to find information.
Use the following formula in the search field:
<product name> <release number> <topic keywords> site:cisco.com
Examples of Google Search entries:
•
•
•
New and Changed Information
Release 7.1(4)
This release provides the following new functionality and enhancements:
•
•
Limitations and Restrictions
Review Table 8 before you work with Cisco UC Integration for Microsoft Office Communicator. Table 8 lists known limitations that will not be fixed, and there is not always a workaround. The table is sorted by severity, then by identifier in alphanumeric order.
Some features might not work as documented, and some features could be affected by recent changes to the product. Make sure to read the Important Notes.
For information about open and resolved caveats, see Open Caveats, and Resolved Caveats.
Important Notes
Warning
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Restart of Conversation Pane Required If Windows Security Fails
Cisco Unified Communications Integration for Microsoft Office Communicator uses Windows security to secure communication between the conversation pane in Microsoft Office Communicator and Cisco Unified Communications Integration for Microsoft Office Communicator itself. If Windows security fails, the conversation pane displays the following error:
"Could not start the conversation pane. A windows authentication error occurred, please contact your administrator"
The conversation pane stops trying to communicate with Cisco Unified Communications Integration for Microsoft Office Communicator. This failure is typically due to the inability of the client computer to connect to a domain controller. This can be caused by the following issues:
•
•
If the cause of failure is resolved, you must reload the conversation pane to trigger it to attempt to connect to Cisco Unified Communications Integration for Microsoft Office Communicator again.
To reload the conversation pane, sign out of Microsoft Office Communicator, then sign in again. Alternatively, restart Microsoft Office Communicator.
Docking, Undocking, Hibernating, Resuming, and Suspending Client Computers
If you dock, undock, hibernate, resume, or suspend your computer while you have an active call on your desk phone, the call remains active, but you cannot control the call from your computer.
Mute Microphone Keyboard Shortcut Performs Graphics Action
In the active conversations window, you can use the Ctrl+Alt+Down Arrow keyboard shortcut to set your microphone to mute, or switch mute mode off. Some ATI and Intel graphics cards also use this shortcut to rotate the screen 180 degrees. The graphics keyboard shortcut action is performed instead of the active conversations window action. That is, your screen is rotated, but your microphone is set to mute, or mute mode is not switched off.
Updating Availability Status from Microsoft Outlook Calendar
If you have selected in Microsoft Office Communicator to update your availability status from your Outlook calendar information, you might find that your availability status is not accurate after you end a call. Your availability status might be "Busy" after you end a call. You might need to reset your availability status after you end a call.
Microsoft PowerPoint 2007 Support
Cisco Unified Communications Integration for Microsoft Office Communicator does not support Microsoft PowerPoint 2007 because the context menu functionality in Microsoft PowerPoint 2007 no longer permits third party integrations.
Conference Calls Between Users in Different Clusters
If users have a conference call that involves users in different clusters, some users might not be able to see the participant list for the conference call. Instead, the conference call resembles a call between two users.
Numbers Published by Users in Microsoft Office Communicator Not Recognized
You can publish numbers to other Microsoft Office Communicator users. To do this, you select the Menu button in the Microsoft Office Communicator title bar, then select Tools > Options. Then you select the Phones category.
Cisco Unified Communications Integration for Microsoft Office Communicator does not recognize numbers published in this way.
Conversation Pane Menu Items Available But Not Functional
Cisco Unified Communications Integration for Microsoft Office Communicator adds menu items to the Tools menu in Microsoft Office Communicator. If the conversation pane is stopped, these menu items remain available but are not functional. This is expected behavior.
Cisco Unified Communications Manager 6.1(3) and Conference Participant Lists
If you use Cisco Unified Communications Manager 6.1(3), in conference calls the names of the participants are incorrect in the participant list.
Calls Received from Cisco Unified MeetingPlace Might End If You Put on Hold and Resume Multiple Times
If you receive a call from Cisco Unified MeetingPlace, then put the call on hold, and resume the call several times in quick succession, the call might end. This issue occurs in all releases of Cisco Unified MeetingPlace earlier than 8.0.
Availability Status Transitions
Microsoft Office Communicator provides the availability information in Cisco UC Integration for Microsoft Office Communicator. Cisco UC Integration for Microsoft Office Communicator updates the availability status of users after calls start and end as shown in the following table:
Availability Status and Cisco Unified Presence
If Cisco Unified Presence is deployed in your Cisco Unified Communications system, your phone application might reset the availability status of your phone from Do Not Disturb to Available. This can occur on the following events:
•
•
•
For example, if you set your availability status to Do Not Disturb, sign out of Microsoft Office Communicator, then sign in again, the availability status of your phone is reset automatically to Available.
Partial Support for Multiple Lines
Cisco UC Integration for Microsoft Office Communicator can only control one call session button on a phone that is configured for multiple lines. Cisco UC Integration for Microsoft Office Communicator can control the first line in the list of lines returned by the Cisco Unified Communications Manager CTI service.
You cannot change which line is controlled.
Call Control on Cisco Unified IP Phone 9900, 8900, and 6900 Model Series
Cisco UC Integration for Microsoft Office Communicator monitors only one call session button on the desk phone that is associated with it. The Cisco Unified IP Phone 9900, 8900, and 6900 model series allow simultaneous calls on multiple call session buttons. Any call operations that happen on buttons other than the one that Cisco UC Integration for Microsoft Office Communicator monitors are not reflected in the Cisco UC Integration for Microsoft Office Communicator user interface.
If you place or answer a call on a call session button that is not the one that Cisco UC Integration for Microsoft Office Communicator monitors, the call does appear in a conversation window. You cannot use Cisco UC Integration for Microsoft Office Communicator to control calls on the buttons that Cisco UC Integration for Microsoft Office Communicator does not monitor.
The impact of JAL and DTAL operations on a call that Cisco UC Integration for Microsoft Office Communicator controls depends on whether the operation moves a call to a monitored call session button.
If a JAL operation moves a call to a monitored call session button, the call transitions to a conference call. If a JAL operation moves a call to an unmonitored button, the call disappears from the Cisco UC Integration for Microsoft Office Communicator user interface. Cisco UC Integration for Microsoft Office Communicator cannot control the call.
Similarly, a DTAL operation moves a call to a monitored call session button, Cisco UC Integration for Microsoft Office Communicator can control the call, but if the call moves to an unmonitored button, Cisco UC Integration for Microsoft Office Communicator cannot control the call.
Adding Users to the Standard CTI User Groups
If you want Cisco UC Integration for Microsoft Office Communicator to be able to control the desk phone of the user, you must select the Allow Control of Device from CTI option when you create the device for the user. You must also ensure that the user is added to the Standard CTI Enabled user group.
If the phone of the user is a Cisco Unified IP Phone 9900, 8900, or 6900 series model, you must also add the user to the Standard CTI Allow Control of Phones supporting Connected Xfer and conf user group.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
If the phone of the user is a Cisco Unified IP Phone 9900, 8900, or 6900 series model, select the Standard CTI Allow Control of Phones supporting Connected Xfer and conf user group also.
Step 6
Step 7
Setting Logging Levels Before You Create a Problem Report
By default, when start Cisco UC Integration for Microsoft Office Communicator and CSF, the logging level is set to Reduced.
If you want to report a problem with Cisco UC Integration for Microsoft Office Communicator, you must set the logging level in Cisco UC Integration for Microsoft Office Communicator to Verbose before you create the problem report. To set the logging level, select the Options button in the conversation pane, select Verbose as the logging level, then select OK.
Cisco IP Communicator Listed as a Desk-Phone Device
If you are using your computer for phone calls, you can select a desk-phone device to use if you switch to use your desk phone for phone calls. If you have Cisco IP Communicator open, Cisco IP Communicator is listed as a desk-phone device. This is expected behavior.
QoS Packet Marking on Windows Vista
You can enable Quality of Service (QoS) packet marking for CSF in Cisco Unified Communications Manager. Packet marking requires administrator privileges for Windows Vista computers in Active Directory 2003 domains. Therefore users must have administrator privileges to overcome this operating system limitation and enable QoS packet marking for CSF deployments on Windows Vista on Active Directory 2003 domains.
For Windows Vista computers in Active Directory 2008 Domains you can use Group Policy to overcome this limitation.
•
•
Enabling Packet Marking for CSF on Cisco Unified Communications Manager
Procedure
Step 1
Step 2
Step 3
Enabling Packet Marking for CSF with Active Directory 2008 on Windows Vista
Procedure
Step 1
Step 2
Step 3
For example, create a policy called Cisco CSF UDP.
Step 4
Step 5
Step 6
cucsf.exe
Step 7
Step 8
•
•
Step 9
Step 10
For example, select UDP, and select From any source port and To any destination port.
Step 11
Step 12
The settings that are applied to the client computers from the example above are as follows:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\QoS\Cisco CSF UDP]
"Version"="1.0"
"Application Name"="cucsf.exe"
"Protocol"="UDP"
"Local Port"="*"
"Local IP"="*"
"Local IP Prefix Length"="*"
"Remote Port"="*"
"Remote IP"="*"
"Remote IP Prefix Length"="*"
"DSCP Value"="46"
"Throttle Rate"="-1"
Support for Microsoft Business Productivity Online Standard Suite
Cisco UC Integration for Microsoft Office Communicator Release 7.1(4) supports environments where a Microsoft Office Communications Server is hosted within the Microsoft Business Productivity Online Standard Suite (BPOS).
The following sections provide an overview of the configuration consideration when you deploy the Cisco UC Integration for Microsoft Office Communicator in an environment that is hosted by BPOS:
•
•
•
Requirements for Using Cisco UC Integration for Microsoft Office Communicator with BPOS
You can use Cisco UC Integration for Microsoft Office Communicator with Microsoft Office Communicator and BPOS if the following conditions are met:
•
•
–
–
•
•
Architecture of Cisco UC Integration for Microsoft Office Communicator in a BPOS Environment
The following illustration shows how the Cisco UC Integration for Microsoft Office Communicator operates in a BPOS environment:
The Cisco UC Integration for Microsoft Office Communicator has no direct interaction with the hosted Microsoft Office Communicator servers. All interaction happens through the Microsoft Office Communicator application programming interfaces (APIs).
The Cisco UC Integration for Microsoft Office Communicator uses LDAP to interact with an enterprise-based Active Directory server. The Cisco UC Integration for Microsoft Office Communicator also interacts with Cisco Unified Communications Manager for voice and video media services.
User Phone Numbers Must Use +E.164 Formatting
When you call a contact, the Cisco UC Integration for Microsoft Office Communicator mostly gets contact phone numbers from the Microsoft Office Communicator address book. In a BPOS environment, the address book is downloaded from the BPOS service.
To populate the address book with the phone numbers of the Microsoft Office Communicator users, the OCS address book service in the BPOS data center must enter the phone numbers into address book files correctly.
The OCS address book service only enters +E.164-formatted phone numbers into the address book. Phone numbers that are not in this format are excluded from the address book. All phone numbers provided to the BPOS service must be in +E.164 format.
For more information about the +E.164 standard and Cisco UC Integration for Microsoft Office Communicator, see the Installation Guide for Cisco Unified Communications Integration for Microsoft Office Communicator at the following URL:
http://www.cisco.com/en/US/products/ps10317/tsd_products_support_series_home.html
Note
User Authentication
The Microsoft Online Services Sign In tool performs Microsoft Office Communicator authentication. This tool manages the Microsoft Office Communicator sign-in process.
The Cisco UC Integration for Microsoft Office Communicator sign-in process is authenticated using Cisco Unified Communications Manager and/or Active Directory, depending on how the authentication is set up. The BPOS environment does not change the default authentication process for the Cisco UC Integration for Microsoft Office Communicator.
Note
Using Cisco UC Integration for Microsoft Office Communicator With Microsoft Exchange in a BPOS Environment
The BPOS service can also provide a Microsoft Exchange service. The Cisco UC Integration for Microsoft Office Communicator includes an option that users can select to save conversation history in Microsoft Outlook. This option has been tested with an Outlook client integrated into a BPOS-hosted Exchange server.
The Cisco UC Integration for Microsoft Office Communicator can also operate in an environment where OCS is hosted within BPOS, and Exchange is hosted within the enterprise data center.
Configuring Microsoft Office Communicator 2007 R2 to Use HTTPS to Access Custom Availability Statuses
Cisco UC Integration for Microsoft Office Communicator includes custom availability statuses such as "On the Phone". These statuses are stored in a custom availability status file, cisco-presence-states-config.xml.
Microsoft Office Communicator 2007 R1
The location of this file is set in the Custom presence states URL Microsoft Office Communicator group policy setting. In Microsoft Office Communicator 2007 R1 this URL can use any of the following protocols:
•
•
•
Cisco UC Integration for Microsoft Office Communicator installs the cisco-presence-states-config.xml file in the local file system of the computer of the user. Cisco UC Integration for Microsoft Office Communicator also updates the Custom presence states URL group policy setting to refer to this file with the file:// protocol.
Microsoft Office Communicator 2007 R2
By default, in Microsoft Office Communicator 2007 R2, the URL specified in the Custom presence states URL group policy setting must begin with https://.
As a result, Microsoft Office Communicator 2007 R2 cannot use the Cisco UC Integration for Microsoft Office Communicator custom availability statuses. In this case, Cisco UC Integration for Microsoft Office Communicator uses the generic Microsoft Office Communicator "Busy" availability status instead of the Cisco UC Integration for Microsoft Office Communicator "Busy: On the phone" custom availability status.
To enable the custom availability statuses, do the following:
1.
2.
For information about how to apply these policy settings to Microsoft Office Communicator, see Microsoft Office Communications Server 2007 R2 Client Group Policy Documentation at the following URL:
Location of Custom Availability Statuses File
On computers that have Cisco UC Integration for Microsoft Office Communicator installed, the cisco-presence-states-config.xml file is in the following locations:
Windows XP
<drive>:\Documents and Settings\All Users\Cisco Systems\CUCIMOC\config\presence
Windows Vista
<drive>:\ProgramData\Cisco Systems\CUCIMOC\config\presence
Differences Between English-Language and Translated User Documentation
The English-language version of the online help and the User Guide for Cisco Unified Communications Integration for Microsoft Office Communicator on which the translations are based is slightly different from the English-language version that is built into the product and available from the corporate website. The following table lists the differences between the two versions:
Corrections to User Documentation
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
To access Bug Toolkit, you need the following items:
•
•
•
Procedure
Step 1
Step 2
Step 3
For information about how to search for bugs, create saved searches, and create bug groups, click Help in the Bug Toolkit page.
Open Caveats
Table 9 describes possible unexpected behavior that might occur in Cisco UC Integration for Microsoft Office Communicator. Only severity 1, severity 2, and select severity 3, 4, and 5 open caveats, as well as all customer-found defects, are provided in this document. The table is sorted by severity, then by identifier in alphanumeric order.
Unless otherwise noted, these caveats apply to all Cisco UC Integration for Microsoft Office Communicator releases. For details about an individual defect, click the identifier to access the online record for that defect in the Bug Toolkit.
Because defect status continually changes, be aware that the table reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access the Bug Toolkit. For details, see Using Bug Toolkit.
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).
The following sections list caveats that are resolved in Cisco Unified Communications Integration for Microsoft Office Communicator Release 7.1(4) but that may have been open in previous releases:
Release 7.1(4)
Table 10 lists the caveats that were resolved in Release 7.1(4).
Release 7.1(3a)
Table 11 lists the caveats that were resolved in Release 7.1(3a).
Release 7.1(3)
Table 12 lists the caveats that were resolved in Release 7.1(3).
Release 7.1(2) MR1
Table 13 lists the caveats that were resolved in Release 7.1(2) MR1.
Troubleshooting
The following Cisco UC Integration for Microsoft Office Communicator documents provide troubleshooting information:
•
•
Use this link to access this documentation:
http://www.cisco.com/en/US/products/ps10317/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, 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
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
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)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
