Cisco Jabber for Windows
These are the limitations that apply to the Jabber for Windows client.
Limitations for All Deployments
These limitations apply to all Jabber for Windows deployments.
Allow Paste Operations via Script
Jabber versions 11.8.5 and later may have issues with Copy/Paste when the policy Allow paste operations via script is enabled for Internet Explorer at.
Automatic Detection of Proxy Settings (WPAD)
Cisco Jabber doesn’t support Web Proxy Auto-Discovery (WPAD) proxy discovery. For information about how to configure proxy settings for Cisco Jabber, see Configure Proxy Settings in the On-Premises Deployment for Cisco Jabber guide.
Bluetooth Connectivity Unsupported with Cisco Headset 56x
Cisco Jabber doesn’t support the use of Bluetooth with Model 56x Cisco headsets. You can use these headsets with a USB-C to USB connector cable.
When you’re transferring a call to a third party, the third party must respond to the call before you can complete the transfer. You can’t currently dial the third party and connect the first party while waiting for the call to connect (also known as a blind transfer).
Prior to Release 12.7(1), Cisco Jabber doesn’t correctly inform Unified Communications Manager that a call being transferred is on hold. This behavior results in incorrect reporting when you use Jabber with Cisco Finesse.
Cannot Copy Image
You can’t right-click over an image in a conversation in Jabber and select copy. Instead, highlight the image and then right-click to copy it.
Chat Reply and No Voicemail Profile
If the user has no voicemail profile configured, the chat reply feature doesn’t work. If the user selects Chat reply in an incoming call, the call continues to ring and the Chat reply and Answer options are grayed out. CSCux75667 documents this limitation.
Chat Behavior During Transition to MRA
Jabber loses chat messages that are sent while the Jabber client is transitioning from an on-premises network connection to an MRA network connection, or vice versa. Users receive an error message when they try to send chat messages during this transition period.
Cisco AnyConnect Secure Mobility Client
Cisco Jabber for Windows supports Cisco AnyConnect Secure Mobility Client version 4.0 and later. CSCuy14721 documents this limitation.
Cisco IP Communicator
Cisco IP Communicator isn’t supported as a controlled device on Jabber when users choose to use their desk phone for calls.
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 doesn’t support Cisco Unity Connection dispatch messages. CSCuw31908 documents this limitation..
Contact Resolution for Enterprise Groups
Jabber resolves contacts in enterprise groups individually rather than all at once. As a result, when you add an enterprise group to your users' contact lists—or if they clear their local cache—they'll only see the username and domain for each person until they hover over or interact with them.
Emails to a Group of Contacts
There’s a limit of 2083 characters in the To field when sending an email to a group of contacts. With long email addresses or many recipients, 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.
Jabber doesn’t support the Cisco Extension Mobility Cross Cluster (EMCC) feature.
Device Name with Extension Mobility
When Extension Mobility is enabled, the controlled devices menu in Jabber displays the phone type only, instead of the phone type and user name.
Do Not Disturb (DND)
If Jabber is controlling the Deskphone and if Do Not Disturb (DND) is set on the Deskphone,the presence status of the Jabber client does not change.
This behavior indicates that the Jabber client is functioning as designed. No action is required from the user.
HTML Sanitization Code
The Jabber HTML sanitization code has been modified to disallow 'masked' links in XMPP message payloads due to its potential abuse in phishing attacks. These links are no longer allowed for security reasons.
It is recommended that Jabber Administrators educate potential users who may be affected by this feature enhancement.
IBM Notes Contact Search
When searching for an IBM Notes contact, entering either " or \ as the first character in the search string won't find the correct contact.
Jabber Config Change Detected Loop Scenario
A Jabber "Config Change Detected" loop can occur if you assign the Jabber Config Profile (jabber-config.xml) on UC service and in the Group Config file for Phone page/common phone profile, and then you remove the Jabber Config Profile from the UC Service while Fast Login is enabled. In this scenario, once you remove the Config Prilfe from UC Service, the config change detected loop is triggered.
Workaround: Disable Fast Login, see Planning Guide for Cisco Jabber.
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 same internet-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. This behavior is documented in CSCuw32007.
Joining Meetings by Meeting Number
In deployments that use a Cisco Webex Meeting Server, you cannot use the meeting number when joining by Webex. Use the meeting URL instead.
Joining Webex Meetings from Jabber
Webex site disclaimers don't appear when you join Webex meetings from Jabber. This limitation applies whether joining from the meeting reminder popup, or by selecting Join in Webex in Jabber.
LDAP Credential Delivery with Unified Communications Manager 12.5(1) SU2
In Unified Communications Manager Release 12.5(1) SU2, Unified CM added support for securely passing encrypted LDAP credentials in the Service Profile. This update secures access to your directory by ensuring that the password is always stored and sent in an encrypted format. This change includes encryption during directory access authentication, client configuration file downloads, BAT imports/exports, and upgrades.
In Jabber 12.8 with this Unified CM release or later, we take advantage of this capability by downloading the LDAP credentials as part of User Profile after end-user authentication.
In Jabber 12.7 and earlier with this Unified CM release or later, we can’t use these credentials from the Service Profile as we did before. They pass an encrypted password to Active Directory which causes a connection failure. For these Jabber releases with the upgraded Unified CM, provide the LDAP credentials through the jabber-config.xml file.
For more details, see the Release Notes for Cisco Unified Communications Manager and the IM and Presence Service, Release 12.5(1) SU2 and the section on LDAP Service Accounts in the Planning Guide for Cisco Jabber.
Limit of 450 Participants in a CMS Meeting
You can have a maximum of 450 people in a single CMS meeting.
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 now doesn't work for newly added domain users. Users in the initial domain are unaffected. CSCuu63734 documents this limitation.
Logitech Keyboard Display Changes
The built-in display for Logitech UC keyboard K725-C doesn’t display caller or device information on incoming calls. Instead, the Cisco logo is displayed.
Cisco Jabber displays pop-up reminders for Cisco Webex meetings only. Reminders for non-Cisco Webex meetings are not displayed.
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. This behavior is documented in CSCux03658.
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). CSCuo57172 documents this limitation.
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.
Cisco Jabber can't make calls from any line, while there's an incoming call ringing on another line. While another line is ringing, the green Call button is dimmed and not available. Users can wait for the ringing to stop, or decline the incoming call.
168 Byte Limit for Transferred Filenames
When transferring a file, the filename cannot exceed 168 bytes (including extension). If you attempt to send a file with a longer name, you are notified that you have exceeded 168 bytes.
Phone Mode Deployments with Microsoft Lync
Disable Click-to-x functionality 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.
Presence indicators on Sharepoint 2016
When you sign-out of Jabber, the presence indicator bubbles are grayed out and do not refresh after signing back into Jabber.
You can resolve this behavior by refreshing the webpage. This will ensure that accurate presence information is displayed.
Real-Time Transport Control Protocol (RTCP)
Jabber sends RTCP packets even when disabled. RTCP is an integral component of Jabber Telephony services.
Remote Desktop Control over Mobile and Remote Access
Remote desktop control over Mobile and Remote Access isn’t supported. This limitation is documented in CSCuz19139.
Removing Participants During Conference Calls
Users can only remove participants from a conference call when using a softphone (CSF) device for calls in a non-VDI deployment. Users can't remove participants from conference calls in desk phone control mode or using extend and connect.
SAML Single Sign-On Limitations
When configuring SAML SSO on Cisco Unified Communications Manager 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 isn’t valid. The requirement to use an FQDN is because the embedded Internet Explorer browser isn’t able to validate IP addresses in the Subject Alternate Name (SAN) certificate.
For the same reason, when you configure SAML SSO on Cisco Unity Connection servers, use a fully qualified domain name (FQDN) in Cisco Unified Communications Manager Service Profile 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 isn't valid.
Schedule Meeting Button Disabled on Phone-Only Mode
When Outlook is installed, and the MacCalendarIntegrationType parameter is set to Outlook, the Schedule Meeting button is displayed. However in phone-only mode, the button is not shown.
Single Number Reach
For Cisco TelePresence Video Communication Server Control (VCS) versions earlier than 8.10.X, configure the editable inbound rules to enable the single number reach for users who are using Cisco Jabber over Mobile and Remote Access. For more information, see Limitations in Enable Single Number Reach section from the Feature Configuration Guide for Cisco Jabber 12.0.
Space Characters in Credentials
The following rules apply to space characters and credentials:
Usernames can contain spaces in on-premises deployments.
The first and last characters of usernames in on-premises deployments can't be spaces. This rule is also true for usernames synchronized from a directory source.
Usernames can’t contain spaces in cloud-based deployments.
Passwords can’t contain spaces in any deployment scenario.
Standard CTI Secure Connection User Group
Cisco Jabber for Windows doesn’t currently support CTI connections over transport layer security (TLS). As a result, Cisco Jabber for Windows users can’t 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.
Supported Characters in a Cisco Jabber User ID/E-mail Address
The following characters are supported in a Cisco Jabber user ID/E-mail Address:
Uppercase (A to Z) and lowercase (a to z) characters
TIFF Images Not Supported
In this release, if users have a .tiff image as their avatar, then Jabber displays the default icon image instead. To use a personal avatar, users must upload an image in a supported format, such as jpg, bmp, or png.
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.
The Start My Video button doesn't work immediately after a call connects. Users must wait approximately 6 seconds after the call starts before clicking the Start My Video button. This behavior is documented in CSCuz06415.
Voicemail Credential Popup during Sign-in
In a hybrid deployment, if Webex messenger, Call Manager and Unity connection are all SSO enabled, and voicemail credentials
have been previously saved to cloud, users may see the Update Credentials popup for voicemail during the sign-in process. The workaround is not to configure voicemail server address on the cloud
server but only configure it in the service profile or the
Windows 10 Crash Using Cisco 700 Series Headsets
If you use Cisco 700 Series headsets, you might experience Windows OS crashes (Blue screen). This occurs on Windows 10 version 1803 and earlier versions. Update to a later version of Windows 10 to correct the problem.
Limitations for On-Premise Deployments
These limitations apply to Jabber for Windows 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):
Signing in on one client changes custom availability states to 'Available' on other clients.
If you set the availability state from 'On a call' to another state while on a call, the availability state does not automatically change to 'On a call' for subsequent calls.
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.
Port Contention Disrupts Sennheiser Plug-In
Call control with the Sennheiser plug-in uses port 8001 by default. If another application uses this port, it can cause issues.
As a workaround, you can change the EPOS SDK's PortNumber parameter to another port in the appropriate file:
Consult Sennheiser for more information about these files.
Shut down Jabber before changing the port in the SDK. Then, restart Jabber after you change the port.
Limitations for Cloud Deployments
These limitations apply to Jabber for Windows on Webex Messenger and Team Messaging Mode 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 credentials, see the following article, https://help.webex.com/en-us/yhq7pw/Reset-Forgotten-Password-in-Cisco-Jabber.