Cisco Jabber for Windows 9.6 Release Notes
Known Issues, Limitations, and Important Notes
Downloads: This chapterpdf (PDF - 1.21MB) The complete bookPDF (PDF - 2.09MB) | The complete bookePub (ePub - 129.0KB) | Feedback

Known Issues, Limitations, and Important Notes

Known Issues, Limitations, and Important Notes

Known Issues

Microsoft SharePoint 2013 Presence Integration

Cisco Jabber for Windows 9.6.1 presence integration with Microsoft SharePoint 2013 does not work correctly for non-contacts when the JID and email are different. The presence bubble intermittently does not light up in the SharePoint Contact Card. This item is documented in CSCuh09658.

Microsoft Outlook Local Contacts and Presence

Active Directory users with different Instant Messaging and email addresses saved as local contacts in Microsoft Outlook 2010 and 2013 no longer have presence information displayed for them. This item is documented in CSCuj91246.

Desktop Phone Video

Desktop phone video will not work on Microsoft Windows 8 with MSI 4 installed. This issue is documented in CSCul29528.

Performance and Behavior Notes

Review the content in this topic to understand client performance and behavior in certain cases.

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.

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.

Voicemail Messages

The following restrictions currently apply to voicemail messages:
  • The client cannot play broadcast voicemail messages.

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:
  • Screen_Capture_Enabled
  • File_Transfer_Enabled

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

In on-premises deployments, the following can occur:
  1. Users add federated contacts to their contact lists.
  2. 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.
  3. 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

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

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 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.

Important Notes

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.

Audio Issues with Cisco Security Agent

In some cases audio calls hang and users cannot end active calls if you run the Cisco Security Agent (CSA) while using Cisco Jabber.

This issue:
  • Affects users with USB microphones or USB cameras that include microphones, but might not be limited to USB devices.
  • Is most likely to occur when the computer's battery is running low.

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.

This issue is documented in CSCuh09658.

Phone Mode Deployments with the Microsoft Lync Client

Click-to-x functionality must be disabled to deploy Cisco Jabber for Windows in phone mode on the same computer as the Microsoft Lync client. See New Features for information on the CLICK2X installer switch that can accomplish this task.

Upgrade Cisco WebEx Connect Client

If you use the Cisco WebEx Connect client, you can upgrade to Cisco Jabber for Windows 9.6 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 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 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 5 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.

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:
  1. User A and user B are connected to the primary instance of Cisco Unified Communications Manager.
  2. User A calls user B.
  3. User A puts the call on hold.
  4. 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.

To resolve this issue, apply the fix available from the Microsoft support site at: http:/​/​support.microsoft.com/​kb/​2524478/​en-us

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.

To resolve this issue, set a value for the Delay After Answer field in the Cisco Unity Connection advanced telephony integration settings. See the Cisco Unity Connection documentation at: http:/​/​www.cisco.com/​en/​US/​docs/​voice_ip_comm/​connection/​8x/​gui_reference/​guide/​8xcucgrg120.html#wp1056978

Loss of Video on Calls with CTS Devices

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 incoming 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.
  • Both clients register to the same CSF device.

Call History and Roaming Profiles

Call history is lost when the application is running in a Roaming Profile environment. Roaming Profile environments include those running Virtual Desktop Infrastructure such as VMware View or Citrix Xen or hot desks.

UDS Directory Source

Cisco Unified Communications Manager User Data Services (UDS) is not supported for directory integration in this release.

URI Handlers

Cisco Jabber for Windows no longer supports the sips: URI hander.

Video Calls on Hold

Cisco Jabber for Windows does not send video while a video call is in the process of being transferred to another device. Video will be displayed after the call transfer is complete or the transfer process is aborted.

Upgrading Cisco Jabber for Windows and Service Discovery

There are two upgrade scenarios administrators must be aware of when moving to Cisco Jabber for Windows 9.6.1. They are as follows:

  • Upgrading from an EAP client Enterprises that have participated in the Early Adopter Program for Release 9.6 must perform the following tasks before installing the final version of the application:
    1. Uninstall the EAP version of the client from the Control Panel.
    2. Delete all files from the following folders:
      1. %appdata%\Cisco\Unified Communications\Jabber
      2. %userprofile%\AppData\Local\Cisco\Unified Communications\Jabber
  • Upgrading from Cisco Jabber for Windows 9.2 Service Discovery information will be read from the cached configuration during the upgrade. No administrative intervention or user input is required if Service Discovery information is found in this configuration.

Service Discovery Steps in New Installations

Service Discovery information is retrieved by the client in new installations using the following steps:

  1. The client will look for a services domain value in the SERVICES_DOMAIN installer switch. This value is for the services domain if found and the user will not be prompted to provide services domain information.
  2. The client will look for fallback authenticator information in the AUTHENICATOR installer switch if it cannot find it in the SERVICES_DOMAIN switch.
  3. The client will prompt the user to enter services domain information if it was not found in the previous steps.

Microsoft Internet Explorer 11

Cisco Jabber for Windows 9.6 or later supports up to Microsoft Internet Explorer 10, the default browser on Microsoft Windows 8. Cisco Jabber for Windows 9.6 or later does not support Microsoft Internet Explorer 11.