Intermittently, the Start meetings icon becomes disabled in the Conversations window when users undock and then dock their computers.
This issue is resolved in version 9.2.5 with CSCui22875.
User Login Issue with Cloud-Based Single Sign-On (SSO)
In some cases, Cisco Jabber for Windows does not allow users to progress beyond the sign in window after users successfully sign in to the client.
This issue affects only cloud-based SSO deployments and is resolved in a future version with CSCui08413.
Client Behaves Unpredictably on Import of Large Enterprise Groups
Cisco Jabber for Windows can behave unpredictably if you import an enterprise group that contains one thousand or more contacts.
This issue affects only cloud-based deployments and is resolved in a future version with CSCui48719 and CSCui48699.
Desktop Share Icon Becomes Disabled
The Share your desktop icon becomes disabled in the Conversations window for users after they join a group chat.
The following is an example scenario of this issue:
User A sends an instant message to user B. The Share your desktop icon is enabled in the Conversations window for both user A and user B.
User A initiates a group chat with user B and user C. The Share your desktop icon becomes disabled in the Conversations window for all users.
User A sends an instant message to user B. The Share your desktop icon becomes disabled in the Conversations window for both users.
This issue is resolved in a future version with CSCui22283.
Group Chats Initiated from Cisco Unified Personal Communicator
Cisco Jabber for Windows users cannot join group chats if another Cisco Jabber for Windows user invites them to a group chat that was started in Cisco Unified Personal Communicator.
User A starts a group chat in Cisco Unified Personal Communicator and selects the Allow participants to invite others option.
User A then invites two Cisco Jabber for Windows users, User B and User C, to the group chat.
If User B or User C then invite other
Cisco Jabber for Windows users to the group chat, those users cannot join the group chat with User A, User B, and User C.
Phone Numbers Display as IM Address
In some circumstances, phone numbers display as IM addresses, for example, #######@domain.
When phone numbers display as IM addresses, users cannot call the number. Likewise, because the phone numbers display as IM addresses, the client displays presence and incorrect number types in the user interface.
This issue occurs if URI dialing is enabled on Cisco Unified Communications Manager. This issue only affects phone numbers that are not in the user's contact list or in the corporate directory.
Changing from Full UC to Phone Mode
Cisco Jabber for Windows does not currently support changing product mode from a Full UC or Cisco Jabber for Everyone (IM Only) deployment to a phone mode deployment.
Performance and Behavior Notes
Review the content in this topic to understand client performance and behavior in certain cases.
Multiple Resource Login
The following issues currently apply to multiple resource login with
Cisco Jabber for Windows:
Availability states change to 'Available' on all clients when users resume from hibernate on one client.
Resuming from idle overrides custom availability states.
In on-premises deployments, signing in on one client changes custom availability states to 'Available' on other clients.
In on-premises deployments, 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.
Users who are signed in to multiple Cisco Jabber for Windows clients can join group chats from only one client.
Cisco Jabber for Windows does not always reformat incoming text correctly when the sender is signed in to a client other than Cisco Jabber for Windows.
The following restrictions currently apply to voicemail messages:
The client cannot play broadcast voicemail messages.
The client cannot play voicemail messages that are encoded with the g.729a codec.
Disabling File Transfers and Screen Captures
You can disable file transfers and screen captures on Cisco Unified Communications IM and Presence with the Enable file transfer parameter.
If you disable the setting on the server, you must also disable file transfers and screen captures in the client configuration. Set the following parameters to false in your configuration file:
Blocking Users in Enterprise Groups
Blocking users does not deny availability status if the blocked users exist 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.
This issue applies to Cisco Jabber for Windows in cloud-based deployments only.
Contacting Federated Users After Changing Privacy Policies
on-premises deployments, the following can occur:
Users add federated contacts to their contact lists.
Users change the policy for contacts outside the domain from Prompt me every time to Block everyone on the Privacy tab of the Options window. As a result, the federated contacts remain in the contact list but do not display availability. Likewise, users cannot send or receive instant messages from those federated contacts.
Users then change that policy from Block everyone to Prompt me every time. As a result, Cisco Unified Presence removes the federated contacts from the contact lists. Cisco Unified Presence does not repopulate the federated contacts.
Because Cisco Unified Presence removes the federated contacts from the contact lists, users must add the federated contacts to their contact lists again to send instant messages or display availability status to those federated contacts. However, the federated contacts can send instant messages to the users, even if they are not in the contact list.
Descriptions for Multiple Devices
If Cisco Jabber for Windows users have multiple desk phone devices of the same model, you should enter descriptions for each device. Cisco Jabber for Windows displays these descriptions to users so that they can tell the difference between multiple desk phone devices. If you do not enter descriptions, Cisco Jabber for Windows displays the model name of the device. As a result, users cannot tell the difference between their devices if they have multiple devices of the same model.
Diverting Calls in Do Not Disturb State
As of this release, setting your status to 'Do Not Disturb' in the client does not divert, or block, incoming calls.
To divert calls, users must set 'Do Not Disturb' on their desk phone devices.
Extension Mobility Cross Cluster
Cisco Jabber for Windows does not currently support extension mobility cross cluster (EMCC).
Space Characters in Credentials
In some cases, users cannot log in to Cisco Jabber for Windows if their credentials contain space characters.
In both on-premises deployments and cloud-based deployments, passwords must not contain space characters.
In cloud-based deployments, usernames must not contain space characters.
In on-premises deployments, the first and last characters of usernames must not be space characters. You should also ensure that the credentials you synchronize to your presence server from Microsoft Active Directory, or other directory source, do not contain spaces as the first or last character.
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 topic describes issues with interoperability with other clients, devices, and third party software, along with server-side issues or defects that impact client functionality. In addition, this topic includes some best practice information to prevent issues with the client.
Presence issues with Microsoft SharePoint 2013
Intermittent issues with presence integration can occur in Microsoft SharePoint 2013 if Microsoft Office 2013 is installed on the client computer.
These issues are the result of a Microsoft defect. A case has been opened with Microsoft to address this defect.
Phone Mode Deployments with the Microsoft Lync Client
You should not install Cisco Jabber for Windows in phone mode on the same computer as the Microsoft Lync client. This combination of Cisco Jabber for Windows in phone mode with the Microsoft Lync client is not supported.
Upgrade Cisco WebEx Connect Client
If you use the Cisco WebEx Connect client, you can upgrade to Cisco Jabber for Windows 9.2(2) or higher from Cisco WebEx Connect version 7.2.2 only.
You can upgrade from Cisco WebEx Connect version 7.x to any Cisco Jabber for Windows version up to 9.2(0). You can then upgrade the Cisco Jabber for Windows client to version 9.2(1) or higher.
Cisco Jabber for Windows and the Cisco WebEx Connect Client
You should not install and run Cisco Jabber for Windows on the same computer as the Cisco WebEx Connect client. If you do run both the Cisco WebEx Connect client and Cisco Jabber for Windows on the same computer, unexpected behavior is likely to occur.
In the event that you do install Cisco Jabber for Windows version 9.2(2) on the same computer as the Cisco WebEx Connect client, the following error message displays when you launch the Cisco WebEx Connect client:
Can't load webxcOIEx.exe, error code, please check whether the executable is in your install directory.
To resolve this error, you must reinstall the Cisco WebEx Connect client.
Cloud-Based SSO with Microsoft Internet Explorer 9
In cloud-based deployments that use single sign-on (SSO), an issue exists with Internet Explorer 9. Users with Internet Explorer 9 get security alerts when they sign in to Cisco Jabber for Windows. To resolve this issue, add webexconnect.com to the list of websites in the Compatibility View Settings window.
BFCP Desktop Share with Cisco TelePresence SX20
Cisco Jabber for Windows does not currently support BFCP video desktop sharing on calls that you escalate to multipoint, ad-hoc conferences with Cisco TelePresence SX20 endpoints.
BFCP Desktop Share with PVDM3
Packet Voice Digital Signal Processor Module (PVDM3) enabled routers do not support BFCP video desktop sharing capabilities.
Presence States After Loss of Network Connection
In cloud-based deployments, it can take several minutes for the Cisco WebEx Messenger service to detect when clients lose network connections or become abruptly disconnected. For example, the Cisco WebEx Messenger service might take 10 minutes or longer to detect when a client loses a network connection when the user removes the network cable.
As a result of the delay in the server detecting the loss of connection with the client, the server does not immediately publish the presence state of users who have lost their network connection. For this reason, there is a period of time during which users can see an online presence state even when remote contacts are offline.
Continuous Spinner for Voicemail Service
In some cases, users might see a continuous spinner in the Voicemail section of the Phone accounts tab on the Options window. This issue is the result of limitations with Cisco Unity Connection.
Calls on Hold Dropped During Failover
If a user puts a call on hold, the call drops if
Cisco Unified Communications Manager failover occurs. An example of this behavior is as follows:
User A and user B are connected to the primary instance of Cisco Unified Communications Manager.
User A calls user B.
User A puts the call on hold.
Failover occurs from the primary instance of Cisco Unified Communications Manager to the secondary instance.
As a result, user A's call drops. User B's call remains available in preservation mode.
Hold Active Calls During Failover
You cannot place an active call on hold if failover occurs from the primary instance of Cisco Unified Communications Manager to the secondary instance.
MAPI Server Requests for Local Outlook Contacts
Cisco Jabber for Windows attempts to retrieve local Microsoft Outlook contacts from the Outlook PST file. If Outlook does not cache local contacts in the PST file, Cisco Jabber for Windows sends contact resolution requests to the MAPI server. As a result, the MAPI server can experience an impact to performance. Cisco recommends that you configure Outlook to cache local contacts in the PST file. Otherwise, you must ensure that your MAPI server is capable of managing the requests from Cisco Jabber for Windows.
Upgrading with Microsoft Group Policy
Microsoft Group Policy does not detect existing installations of Cisco Jabber for Windows. As a result, if you upgrade Cisco Jabber for Windows with Microsoft Group Policy, Group Policy does not uninstall the existing version before installing the upgrade version.
Calls Drop Intermittently on Network Profile Change
A known bug exists with Microsoft Windows 7 and Microsoft Windows Server 2008 R2 that causes the network profile to change unexpectedly. This change in the network profile closes network ports that Cisco Jabber for Windows requires for calls. As a result, if you are on a call when the network profile changes, that call automatically terminates.
You should use Samsung Kies version 2.5.0 or higher with Cisco Jabber for Windows. Versions of Samsung Kies lower than 2.5.0 have compatibility issues with Cisco Jabber for Windows.
Voicemail Prompt Truncated
The start of the audio that prompts users to leave voicemail messages can be truncated in some instances. The result of the truncation is that users do not hear the first second or two of the voicemail prompt.
Cisco TelePresence System (CTS) devices do not allow users to send video only.
For this reason, when users place calls from their software phones (CSF devices) to CTS devices, loss of video and video desktop sharing occurs if users de-escalate from a video call to an audio only call.
Removing Participants from Conference Calls
The functionality to remove participants from conference calls while using software phone devices is available on Cisco Unified Communications Manager version 8.6.2 and higher.
Integration with Microsoft Outlook
You must restart Microsoft Outlook after you install Cisco Jabber for Windows to enable integration with Microsoft Outlook.
Clients That Do Not Support Graceful Registration
You should exit clients that do not implement graceful registration before you start Cisco Jabber for Windows if both clients use the same CSF device.
For example, Cisco Unified Personal Communicator does not support graceful registration. Cisco Unified Personal Communicator takes over registration of the CSF device if:
You are signed in to both Cisco Unified Personal Communicator and Cisco Jabber for Windows at the same time.