Limitations and Restrictions for All Deployments
IBM Notes Contact Search
Jabber doesn't support searching for IBM Notes contacts using " or \ as the first character in the search string.
Microsoft Outlook OST File
Intermittently Cisco Jabber for Windows is unable to access the Microsoft Outlook OST file. To resolve this issue, restart Jabber and restart Outlook.
Automatic Detection of Proxy Settings (WPAD)
The Cisco Jabber for Windows Meetings Service no longer supports automatic detection of proxy settings. Web Proxy Auto-Discovery (WPAD) protocol lookup is supported only for iOS devices. For information about how to configure proxy settings for Cisco Jabber, see Configure Proxy Settings in the On-Premises Deployment for Cisco Jabber guide.
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).
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 Point VPN. 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 Unity Connection Dispatch Messages
In Cisco Unity Connection, a dispatch message is sent to a distribution list with the message configured in such a way that only one user responds to that message. A user can accept, decline, or postpone the dispatch message. Cisco Jabber for Windows does not support Cisco Unity Connection dispatch messages. This limitation is documented in CSCuw31908.
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.
Location Feature and Multiple Domain Support
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.
Phone Mode Deployments with Microsoft Lync
Click-to-x functionality must be disabled if you want to deploy Cisco Jabber for Windows in phone mode on the same computer as Microsoft Lync. See the Common Installation Arguments section of the Deployment Guide for more information about the CLICK2X installer switch.
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. This limitation is documented in CSCuz19139.
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:
- Usernames can contain spaces in on-premises deployments.
- Usernames cannot contain spaces in cloud-based deployments.
- Passwords cannot contain spaces in any deployment scenario.
- The first and last characters of usernames in on-premises deployments must not be spaces. This rule is also true for usernames synchronized from a directory source.
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.
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 Deployments
Adding Federated Contacts
When adding federated contacts, Cisco recommends that users add the federated contacts as company contacts (), 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):
SIP Trunk for Phone Presence
From Release 11.5(3), you must configure a SIP trunk between Cisco Unified Communications Manager and IM and Presence Service if you want Cisco Jabber users to see phone presence. In previous releases, a SIP trunk was not required for phone presence. This limitation is documented in CSCuz85578.
Limitations and Restrictions for Cloud Deployments
Blocking 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. This limitation is documented in CSCux52068.
Jabber to Jabber Calls
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).
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