photos cannot be displayed in Cisco Jabber for Windows due to an issue
supporting authenticated proxies, even if the server is listed in the Bypass
setting. For more information on this item, see CSCul02706.
Screen Share over VXME
are connecting to the client and meet all criteria below, the person you are
sharing your screen with does not see the video content inside the share
window. The user only sees a black rectangle.
can store up to 250 entries in your call history.
Pickup feature contains the following limitations:
Calling Party Information and
Called Party Information are disabled in Cisco
Unified Communications Manager, then users logged into Call Pickup in softphone
mode do not see either calling party or called party information displayed in
the call alert notification. However, if those options are disabled and users
log into Call Pickup in deskphone mode, then calling party or called party
information is still displayed in the alert.
Audio only notification on Cisco Unified
Communications Manager and the user is on a call, then the user does not hear
any sound indicating that there is a call to pick up.
Pickup on their deskphone when in Deskphone Mode, a
conversation window is displayed momentarily.
pickup notification alert only displays a maximum of 23 characters.
for Windows does not currently support Check Point VPN.
Medianet Metadata Support
Medianet Metadata is no longer supported in Cisco Jabber for Windows.
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
Cisco Jabber for Windows does not support Cisco Unity Connection dispatch messages.
Configuration Parameters for Photo Retrieval
You must 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.
Calls in Hunt Group
Legacy Immediate Divert option in Cisco Unified
Communications Manager, users cannot decline calls when they are logged into
Hunt Group in softphone mode, but can decline calls in deskphone mode. To
disable users to decline Hunt Group calls in both softphone and deskphone mode,
you must enable the parameter
preventdeclineonhuntcall in the configuration file.
for Multiple Devices
enter descriptions for each device if Cisco Jabber for Windows users have
multiple deskphone devices of the same model. Cisco Jabber for Windows displays
these descriptions to users so that they can distinguish between multiple
deskphone devices. If you do not enter descriptions, the client displays the
model name of the device and users cannot distinguish between various devices
of the same model.
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.
Not Displayed in IM Notifications
receive an IM notification that contains an emoticon, the IM notification only
displays the description of the emoticon and not the actual emoticon. The
emoticon is displayed normally in the actual IM conversation.
for Mobile and Remote Access Unsupported Features
Expressway Mobile and Remote Access to connect to services from outside the
corporate firewall, the client does not support the following capabilities:
- Some High Availability
services and audio and video services are not supported for high availability
when you are connected to the client using the Expressway for Mobile and Remote
Access. High availability for instant messaging and presence is supported.
- LDAP for contact
resolution—Instead, the client must use UDS for contact resolution.
- Desk phone control mode
(CTI), including extension mobility.
Remote desktop control.
- Extend and Connect—You cannot
use the Jabber client to make and receive calls on a non-Cisco IP Phone in the
office; to control a non-Cisco IP Phone in the office, such as hold/resume; or
control a home or hotel phone when connecting with Expressway Mobile and Remote
- Session persistency—The client
cannot recover from disruptions caused by network transitions. For example, if
a users start a Cisco Jabber call inside their office and then they walk
outside their building and lose Wi-Fi connectivity, the call drops as the
client switches to use Expressway Mobile and Remote Access.
- Cisco WebEx Meetings
Server—The client cannot access Cisco WebEx Meetings Server, or join or start
Cisco WebEx meetings.
- Sending problem reports—To work around this issue, users can save the report locally and send the
report in another manner.
- CAPF enrollment.
- Early Media—Early Media
allows the client to exchange data between endpoints before a connection is
established. For example, if a user makes a call to a party that is not part of
the same organization, and the other party declines or does not answer the
call, Early Media ensures that the user hears the busy tone or is sent to
voicemail. When using Expressway Mobile and Remote Access, the user does not
hear a busy tone if the other party declines or does not answer the call.
Instead, the user hears approximately one minute of silence before the call is
- Self Care Portal—Users cannot
access the Cisco Unified Communications Manager Self Care Portal when outside
the firewall. The Cisco Unified Communications Manager user page cannot be
accessed externally. The Cisco VCS Expressway or Cisco Expressway-E proxies all
communications between the client and unified communications services inside
the firewall. However, The Cisco VCS Expressway or Cisco Expressway-E does not
proxy services that are accessed from a browser that is not part of the Cisco
- End-to-end media
encryption— Media is
not encrypted on the call path between the Cisco VCS Control or Cisco
Expressway-C and devices that are registered locally to Cisco Unified
Communications Manager. The media path outside of the enterprise is encrypted.
Mobility Cross Cluster
for Windows does not currently support extension mobility cross cluster (EMCC).
Outlook Local Contacts and Presence
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.
When a user
signs in to multiple instances of the client at the same time, the chat feature
behaves as follows in common deployment scenarios (more on multiple resource
login in On-Premises Deployment Scenarios):
Availability states change to 'Available' on all clients when
users resume from hibernate on one client.
from idle overrides custom availability states.
who are signed in to multiple
Cisco Jabber for
clients can join group chats from only one client.
Cisco Jabber for
does not always reformat incoming text correctly when the sender is signed in
to a client other than
Cisco Jabber for
Plantronics Accessories and Software
If you use
Plantronics accessories for
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.
configuring SAML SSO on Cisco Unified Communications Manager and Unity
Connection servers, you must 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.
Phone Not Supported in Virtual Environments (VDI mode)
phones (CSF devices) are not supported in virtual environments. Use Cisco
Virtualization Experience Media Engine (VXME) for Cisco Jabber for Windows call
capabilities in a virtual environment.
Characters in Credentials
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 is
also true for usernames synchronized from a directory source.
Characters in Usernames or Passwords
upper ACSII characters in their usernames or passwords is supported in Cisco
Unified Communications Manager 9.1(2) or later, or users must use lower ASCII
characters for their username and passwords for earlier versions. The Cisco
Jabber for Windows softphone fails to register with Cisco Unified
Communications Manager when users enter some special characters such as
ö in the username or password. The user receives the
following error message: “Invalid username or password entered. Go to Phone Services in
the Options window and enter the correct username and password".
Secure Connection User Group
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.
Unified Communications Applications
Cisco Jabber for Windows and third-party unified communications applications on
the same machine may result in broken presence integration with Microsoft
Office. This behavior is a result of both applications attempting to use the
same Microsoft Office API. To resolve the issue, you can disable the
Click2X command line installation switch in Cisco
Jabber, or remove the third-party application. For more information, see
Common Installation Arguments in the
Jabber Deployment and Installation Guide.
Click-To-X feature with Contacts in Microsoft Outlook
If you are
using 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.
Group on Desk Phones
Use my phone for calls in their client to enable
deskphone mode, then they must log in or logout of their hunt groups using the
deskphone. If users are in deskphone mode, then the
Log Into Hunt Groups option in the Cisco Jabber
client becomes disabled.
Resolution of Lifesize Endpoint after Hold/Resume
experience resolution issues when using Jabber to make a call with a Lifesize
Express 220 endpoint. If the user puts the call on hold, then after resuming
the call the send and receive video resolutions on the Jabber end is greatly
cannot play broadcast voice messages.