//data/KIT/CIPC.zip //data/KIT/group 41663712 Mar 4 2013 CIPC.zip 2 matched. - Connect this storage.
Contents
First Published: June 30, 2015
Last Updated: August 29, 2016
These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Windows Release 11.0.x and 11.1.x. These release notes are updated for every maintenance release but not for patches or hot fixes. Note that each maintenance release includes the features, requirements, restrictions, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Windows, we recommend that you review this document for information about issues that may affect your system.
Build Number
What's New in Release 11.1(4)Updated JCF Library
The Cisco Jabber Client Framework (JCF) Components includes a version of the 'LibTiff' library that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2013-1961, CVE-2013-1960, CVE-2013-4244, CVE-2013-4243, CVE-2012-4447, CVE-2012-3401, CVE-2015-1547, CVE-2014-9655, CVE-2013-4231
The LibTiff library has been removed from the JCF component. This vulnerability has been resolved with caveat CSCva89914.
What's New in Release 11.1(3)Resolved Caveats
This release provides fixes for a number of known issues. See theResolved Caveats in Release 11.1(3) section for a listof caveats fixed in this release.
What's New in Release 11.1(2)Cut and Paste in IMs
You can configure whether users are allowed to copy or cut text and paste it into a chat window. Configure this behavior in Cisco Unified CM IM and Presence Administration > Messaging > Settings with the Allow cut & paste in instant messages check box.
Configurable Domain for Exchange Authentication
To save chat history to an Outlook folder, you must specify an authentication method to the Exchange Server. Use the new ExchangeDomain parameter to specify the domain of the Exchange server. For more information about the ExchangeDomain parameter, see the Cisco Jabber 11.0 Parameters Reference Guide.
What's New in Release 11.1(1)Configurable System Language
The new parameter UseSystemLanguage determines which language is used for Cisco Jabber. The default value for this parameter is false.
The Cisco Jabber language is determined using the following logic:
For more information about parameters, see the Cisco Jabber Deployment and Installation Guide.
Build Number Reported to Cisco Unified Communications Manager
The exact Cisco Jabber for Windows build number is reported to Cisco Unified Communications Manager. The build number can be seen from the Device Settings and Phone Configuration windows on Cisco Unified Communications Manager.
Automatic Sign-in Option Enabled with Installation
A new installer parameter, AUTOMATIC_SIGN_IN, allows you to check the Sign me in when Cisco Jabber starts check box when the user installs Cisco Jabber. The default value for this installer parameter is false. For more information about command line arguments, see the Cisco Jabber Deployment and Installation Guide.
What's New in Release 11.1IBM Notes Contact Search
Users can now search for and add local IBM Notes contacts to their contact lists. Configure this feature with the new EnableLotusNotesContactResolution parameter. The default value for this parameter is false, meaning that users cannot search for or add local IBM Notes contacts. For more information about the EnableLotusNotesContactResolution parameter, see the Cisco Jabber 11.0 Parameters Reference Guide.
For this contact resolution to work properly, the Messaging ID field in IBM Notes must have a valid value.
Jabber to Jabber Calling
This feature applies to cloud deployments only.
Jabber to Jabber calling provides basic voice and video calling between Cisco Jabber clients without Cisco Unified Communications Manager registration. Jabber to Jabber calling is supported only for users who authenticate to the Cisco WebEx Messenger service. Multiple Jabber to Jabber calls are not supported. Jabber to Jabber calling supports the following basic calling features:
Documentation Improvements
Cisco Jabber for Windows end-user documentation, including videos and getting started content, is now also available on the Help Central knowledge base at https://help.webex.com/community/jabber. Documentation for system administrators remains at http://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/tsd-products-support-series-home.html.
Information about Cisco Jabber parameters has been removed from the Cisco Jabber 11.0 Deployment and Installation Guide and included in a new document titled Cisco Jabber 11.0 Parameters Reference Guide. You can find this new document at this link: http://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html
What's New in Release 11.0(1)Compliance and Audit Support for IM-only Screen Sharing
For all IM-only screen sharing events, you can now configure Cisco Jabber clients to send information about all user actions to the Presence server for compliance or auditing purposes. This feature is useful if you want to collect information about IM-only screen sharing, for example, users who initiate screen shares, users who accept screen share invites, users who request control during screen shares, or users who end screen shares. Configure this support with the ScreenShareAuditMessages parameter. The default value is false, whereby Cisco Jabber does not send any information to the Presence server about user actions during IM-only screen sharing.
Administrator Control of Saving Chats to Microsoft Outlook
This release provides greater Administrator control of the feature to save chats to Microsoft Outlook. The EnableSaveChatHistoryToExchange parameter has been removed and replaced with a new parameter SaveChatHistoryToExchangeOperationMode, which can have one of the following values:
![]()
Work Number Shown in Microsoft Outlook 2010Contact Card
In previous releases, when URI Dialing is enabled and Cisco Jabber is running, Microsoft Outlook 2010 contacts show the SIP URI in the click-to-call menu, but no phone number is shown in the contact information. The phone number is shown when Cisco Jabber is not running. This is a known limitation with Microsoft Outlook 2010. In Microsoft Outlook 2013, both the SIP URI and the phone number are shown when Cisco Jabber is running.
With release 11.0(1), the business phone number is shown as the default for click-to-call from Microsoft Outlook 2010.
Email Subject Field in Group Chat Topic Label
When users launch a group chat from a Microsoft Outlook email, the group chat topic is prepopulated with the Subject field of the email. Users can edit the topic in the group chat pop-up prior to starting the group chat.
SIP URI Support in Contact SourcePhone Fields
In previous releases, Cisco Jabber did not recognize SIP URIs in phone number fields in any contact source, and converted each SIP URI to a numeric value in the user profile window. With this release, SIP URI values are now maintained and displayed correctly in the user profile window.
Administrator Control of Extend and Connect Device Editing for Users with Multiple Devices
In previous releases, the Extend and Connect functionality operates as follows:
With this release, the RemoteDestinationEditingWithMultipleDevices parameter allows you to determine whether users with multiple devices can edit or add remote destinations. Set this parameter to false to disallow users with multiple devices to edit or add remote destinations. The default value for this new parameter is true.
Read-only Username on Sign In Screen after Successful First Login
A new parameter, MakeUsernameReadOnly, provides the option to make the Username field on the Sign In screen read-only after the user logs in successfully for the first time. The default setting for this parameter is false. When set to true the MakeUsernameReadOnly parameter delivers the following user experience:
New Chat Font Sizes
Two new font sizes have been added, sizes 8 and 9. Font size 10 remains the default font size for chats.
What's New in Release 11.0Calling Features
Chat and Presence Features
Persistent Chat Features
Sharing Features
Platform Features
Security Features
RequirementsSoftware Requirements
Hardware Requirements
Network RequirementsPorts and Protocols
Third-Party Requirements
Antivirus Exclusions
If you deploy antivirus software, include the following folder locations in the antivirus exclusion list:
Limitations and RestrictionsLimitations and Restrictions for All DeploymentsIBM Notes Contact Search
Jabber doesn't support searching for IBM Notes contacts using ' or as the first character in the search string.
Call History Limit
The client can store up to 250 entries in your call history.
Call Transfers
When you are transferring a call to a third party, the third party must respond to the call before you can complete the transfer. You cannot currently dial the third party and connect the first party while waiting for the call to connect (also known as a blind transfer).
Certificate Requirements for Non-Domain Computers
All computers that run Cisco Jabber must have both base and delta Certificate Revocation List (CRL) files. Computers within the domain automatically get these files, but computers outside of the domain require manual installation of the base and delta CRL files. These files are required for Cisco Jabber to trust to the Cisco WebEx Meetings Server certificate.
Chat Reply and No Voicemail Profile
The chat reply feature does not work if the user has no voicemail profile configured. If the user selects Chat reply in an incoming call, the call continues to ring and the Chat reply and Answer options are greyed out. This limitation is documented in CSCux75667.
Check Point VPN
Cisco Jabber for Windows does not currently support Check PointVPN.This limitation is documented in CSCuy34099.
Cisco AnyConnect Secure Mobility Client
Cisco Jabber for Windows supports Cisco AnyConnect Secure Mobility Client version 4.0 and later. This limitation is documented in CSCuy14721.
Cisco Medianet SupportCipc Admin Ffr 8 6 1 0 Zip Code Map
The Cisco Medianet Metadata feature is no longer supported in Cisco Jabber for Windows.
The Cisco Medianet CDP driver leveraged by the Cisco Jabber desk phone video feature is supported for Windows 7 & 8 deployments. The desk phone video feature and Cisco Medianet CDP driver installation are not supported on Windows 10 workstations.
Cisco Unity Connection Dispatch Messages
In Cisco Unity Connection, a dispatch message is sent to a distribution list with the messageconfigured in such a way that only one user responds to thatmessage. A user can accept, decline, or postpone the dispatchmessage.Cisco Jabber for Windows does not support Cisco Unity Connection dispatch messages. This limitation is documented in CSCuw31908.
Configuration Parameters for Photo Retrieval
Include the configuration parameters for photo retrieval in the global configuration XML file (jabber-config.xml). If you include them in the group configuration XML file, photo retrieval might fail.
Emails to a Group of Contacts
There is a limit of 2083 characters in the To field when sending an email to a group of contacts. Depending on the length of the email addresses and the number of contacts, not all contacts may be added to the email. For more information about the 2083 character limitation, see https://support.microsoft.com/en-ie/kb/208427. This limitation is documented in CSCuz80198.
High DPI Devices
Cisco Jabber for Windows does not support IM-only screen share in a high DPI environment. This limitation is documented in CSCuw50217.
Location Feature and Multiple Domain Support in Release 11.1
Consider the following deployment scenario:
When you deployed your Cisco Unified Communications Manager IM and Presence Service node, all users were imported with single domain support. You later changed the address scheme to Directory URI (multiple domain support).
The location feature will now not work for newly added domain users. Users in the initial domain are unaffected. This limitation is documented in CSCuu76519.
Microsoft Outlook Local Contacts and Presence
Users' presence is unknown when the contact is manually added to contacts in Microsoft Outlook 2010 and 2013, when the contact is added to local (custom) contacts with an email address type of SMTP. To resolve this issue, delete the contact and add it again manually, ensuring the email address type is Exchange (EX). This item is documented in CSCuo57172.
Plantronics Accessories and Software
If you use Plantronics accessories for Cisco Jabber call management, and if you have Plantronics Hub installed, ensure that at least version 3.5 is installed. Download Plantronics Hub 3.5 from the Plantronics website.
Remote Desktop Control over Mobile and Remote Access
Remote desktop control over Mobile and Remote Access is not supported.
SAML Single Sign-On Limitations
When configuring SAML SSO on Cisco Unified Communications Manager and Cisco Unity Connection servers, use a fully qualified domain name (FQDN) instead of an IP Address to define the server name. If you use an IP Address, the client displays a warning message that the certificate is not valid. The requirement to use an FQDN is because the embedded Internet Explorer browser is not able to validate IP addresses in the Subject Alternate Name (SAN) certificate.
Space Characters in Credentials
The following rules apply to space characters and credentials:
Special Characters in Usernames or Passwords
The ASCII printable character set is supported, except for space and delete. The ASCII control and extended character sets are not supported, such as ü, Ü, ä, or ö. Using these characters with Cisco Jabber for Windows will result in softphone registration failure. The following error message is displayed: “Invalid username or password entered. Go to Phone Services in the Options window and enter the correct username and password'.
Standard CTI Secure Connection User Group
Cisco Jabber for Windows does not currently support CTI connections over transport layer security (TLS). As a result, Cisco Jabber for Windows users cannot switch from using a CSF device to using a desk phone device if they belong to the Standard CTI Secure Connection user group. This limitation is documented in CSCux83786.
Upgrades from Release 10.6.6
If you are upgrading from Cisco Jabber Release 10.6.6, complete the following procedure:
If you do not remove all the files from the specified location, installation of Cisco Jabber 11.0(x) will fail.
Using Click-To-X Feature with Contacts in Microsoft Outlook
If you use UDS as a directory source, users can only use Click-To-X capabilities, such as Click-To-Call and Click-To-IM, to contact Microsoft Outlook users if they are already in the cache file. A cache file is created for someone if they are in the users' Cisco Jabber contacts list, or have a Cisco Jabber history created by the user previously searching, IMing, or calling them, or by leaving a voice message.
Limitations and Restrictions For On-Premises DeploymentsAdding Federated Contacts
When adding federated contacts, Cisco recommends that users add the federated contacts as company contacts (File > New > Company Contact), rather than as custom contacts. Adding federated contacts as custom contacts can cause intermittent presence issues. This issue is documented in CSCuz59060.
Creating and Configuring Devices for Users in Cisco Unified Communications Manager 11.0
If you are creating devices for users in Cisco Unified Communications Manager 11.0, you can now specify a key order as RSA Only, EC Only or EC Preferred, RSA Backup. However, the EC Only option is not currently supported by Cisco Jabber, and if you select it, the client will fail to connect to the server.
Multiple Resource Login
When a user signs in to multiple instances of the client at the same time, the chat feature behaves as follows in on-premises deployments (more on multiple resource login in Common Deployment Scenarios):
Space Characters in Credentials
The following rules apply to space characters and credentials in on-premises deployment scenarios:
Server Presence Issue in Client
If you use Cisco Unified Presence 8.6.5 SU2 or earlier, or Cisco Unified Communications Manager IM and Presence 9.1.1 SU1 or earlier, the client might display users' presence as offline when the user is actually online and has a network connection. This presence issue is fixed in Cisco Unified Presence 8.6.5 SU3 and Cisco Unified Communications Manager IM and Presence 9.1.1 SU1 and 10.0.1. This item is documented in CSCui29999.
Contacting Federated Users After Changing Privacy Policies
Users may experience issues contacting federated users in the scenario below when the privacy policy is changed:
Limitations and Restrictions For Cloud DeploymentsBlocking Users in Enterprise Groups
Blocking users does not prevent a blocked user's status from being displayed if the blocked users are in a contact list as part of an enterprise group. For example, User A blocks User B. However, User A is in User B's contact list as part of an enterprise group. As a result, User B can view User A's availability status.
Invitees to Instant WebEx Meetings
Invitees to instant WebEx meetings must be provisioned with WebEx accounts before they can join an instant WebEx meeting. For example, User A has a WebEx account and starts an instant WebEx meeting from Cisco Jabber. Use A then invites User B, who does not have a WebEx account, to the meeting. When User B clicks on the meeting link in Cisco Jabber, an error message is displayed and the user can't join the meeting. User B must be provisioned with a WebEx account before attempting to join any instant WebEx meetings.
Jabber to Jabber Calls
For Release 11.1, we recommend running Internet Explorer 10 or greater while using the Jabber to Jabber calling feature. Using this feature with previous versions of Internet Explorer or with Internet Explorer in Compatibility Mode can cause issues with Cisco Jabber client login (non-SSO setup) or Jabber to Jabber calling capability (SSO setup).
Photo Display
In late 2011, the WebEx server made changes to how photos are stored and formatted on the server. Due to this change, any photo uploaded before January 1, 2012 is not displayed in the client. To resolve the issue, users must re-upload the photo. For more information on this item, see CSCui05676.
Users in Common Identity
There is a known issue with signing into Cisco Jabber for some users who have migrated to Common Identity. If users receive an Incorrect user name or password error message when entering their username and password, see the following knowledge base article https://cisco-support.webex.com/guest/articles/en_US/Troubleshooting/WBX000019555/myr=false
Performance and Behavior NotesDisplay Name Changes in Corporate Directory
When a user's first name or last name is changed either in LDAP or UDS directories, Cisco Jabber does not automatically update this information in the contact list for all watchers of this user. Users must manually update their contact lists using the following procedure:
Jabber to Jabber Calls and Symantec Host IDS (HIDS)
Jabber to Jabber calls can trigger errors in Symantec HIDS.
Symantec HIDS has a rule that disables connections from internet-based servers if it receives 5 connection requests from the sameinternet-based server within 200 seconds.For example, 3 Jabber to Jabber calls within 200 seconds will trigger Symantec HIDS. When this happens, ongoing Jabber to Jabber calls are dropped and Jabber to Jabber calls are disabled for 600 seconds.
To avoid this scenario, you must add Cisco Jabber to the Symantec exception list.
Meeting Reminders
Cisco Jabber displays pop-up reminders for Cisco WebEx meetings only. Reminders for non-Cisco WebEx meetings are not displayed.
Two meeting reminders are displayed for a meeting. One reminder displays the Time to join message. The other reminder includes a Meeting details link. Both reminders are sent automatically by the meeting host at the meeting start time. This behavior is documented in CSCuz06684.
If the URL for a WebEx meeting is changed (for example, by URL filter software), attempts to join the meeting from the meeting reminder or from the Meetings tab fail.
Phone-only Mode after Cisco Unified Communications Manager IM and Presence Service Upgrade
For on-premise deployments, if Cisco Unified Communications Manager IM and Presence Service is upgraded from release 9.1(1) to release 10.5(2) and clients appear in phone-only mode after the upgrade, then all clients must be reset.
Removing Participants During Conference Calls
Users can only remove participants from a conference call when using the softphone(CSF) device for calls. Users can't remove participants from conference calls in desk phone control mode or using extend and connect.
Caveats
Caveats describe unexpected behavior. The following sections describe how to obtain the latest information.
Bug Severity Levels
Known defects, or bugs, have a severity level that indicates the priority of the defect. These release notes include the following bug types:
Search for Bugs
To search for bugs not listed here, use the Bug Search Tool.
Procedure
Open Caveats in Release 11.1(4)Resolved Caveats in Release 11.1(4)
Open Caveats in Release 11.1(3)
There are no changes to the open caveats since Release 11.1(2). See theOpen Caveats in Release 11.1(2) section for a listof open caveats in this release.
Resolved Caveats in Release 11.1(3)
Open Caveats in Release 11.1(2)
Resolved Caveats in Release 11.1(2)
Open Caveats in Release 11.1(1)
Resolved Caveats in Release 11.1(1)
Open Caveats in Release 11.1
Cisco Ip Communicator 8 6 1 0 User GuideResolved Caveats in Release 11.1
Open Caveats in Release 11.0(1)
Resolved Caveats in Release 11.0(1)
Open Caveats in Release 11.0
Resolved Caveats in Release 11.0
Closed Caveats in Release 11.0
Documentation Resources
The following documents are available for Cisco Jabber forWindows:
Math
Copyright © 2016, Cisco Systems, Inc. All rights reserved.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |