DTMF Digits in Log Files
When users enter DTMF digits in Cisco Jabber, the client writes those digits to a log file in plain text.
Problem reports, or PRTs, that users submit contain the log files with DTMF digits. Cisco treats all log files with the strictest confidentiality and deletes all log files when no longer required to investigate product issues.
This issue is resolved in version 9.1.6 with defect number CSCug51731.
Video Desktop Sharing
Video desktop sharing refers to desktop sharing functionality on CSF devices on Cisco Unified Communications Manager that are BFCP-enabled.
Cisco Jabber for Windows supports video desktop sharing in software phone mode only. Video desktop sharing is not available in desk phone mode.
If you configure video desktop sharing on Cisco Unified Communications Manager 8.6.1 and then upgrade to Cisco Unified Communications Manager 8.6.2, you must install the cmterm-bfcp-e.8-6-2.cop.sgn COP file and then configure video desktop sharing on Cisco Unified Communications Manager 8.6.2. You cannot migrate your video desktop sharing configuration from Cisco Unified Communications Manager 8.6.1 to Cisco Unified Communications Manager 8.6.2.
You should not attempt to enable video desktop sharing, or BFCP, on a device or client that does not support BFCP.
If Cisco Jabber for Windows cannot resolve contacts by their phone numbers, video desktop sharing is not available from chat windows.
In a hybrid cloud-based deployment, Cisco WebEx Connect provides instant messaging capabilities and Cisco Unified Communications Manager provides audio and video communication capabilities. However, both Cisco WebEx Connect and Cisco Unified Communications Manager provide desktop sharing functionality.
Video desktop sharing functionality is provided as follows:
If users initiate desktop sharing sessions in instant messaging conversations, Cisco WebEx Connect provides desktop sharing functionality.
If users initiate desktop sharing sessions during an audio or video conversation, they use the video desktop sharing capabilities on Cisco Unified Communications Manager.
Desktop sharing capabilities that Cisco WebEx provides are currently available in English only.
Cisco Jabber for Windows and the Cisco WebEx Connect Client
Unexpected behavior is likely to occur if you run both the Cisco WebEx Connect client and the Cisco Jabber for Windows client on the same computer. This combination of the Cisco WebEx Connect client and the Cisco Jabber for Windows client on the same computer is not supported.
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.
Integration with Microsoft Outlook
You must restart Microsoft Outlook after you install Cisco Jabber for Windows to enable integration with Microsoft Outlook.
Specifying Device Selection
Users should specify device selection in the Advanced section on the Audio and Video tabs on the Options window. If users do not specify device selection in the Advanced section, Cisco Jabber for Windows resets the device selection each time it restarts.
Microsoft Active Directory Credentials
The potential to lock Microsoft Active Directory credentials exists because Cisco Unified Communications Manager synchronizes directory credentials with user phone service credentials and voice mail credentials. You should ensure any changes to credentials occur for all instances where users enter synchronized credentials.
DNS Configuration in a Cisco Unified Presence Cluster
In a Cisco Unified Presence cluster, ensure that the hostname of each node is available to Cisco Jabber for Windows, even if you configure the client to login using an IP address.
Sending Audio on a Lenovo ThinkPad W520
A known issue exists where Cisco Jabber for Windows cannot send audio on a Lenovo ThinkPad W520. To resolve this issue you should install the following Lenovo ThinkPad driver: 8aad10ww.exe.
Video Calls on a Lenovo ThinkPad W500
The following issues exist for video transmission on Lenovo ThinkPad W500 computers if the integrated camera uses certain versions of Ricoh drivers:
Video does not transmit correctly. In some instances, video calls result in empty, or white, video windows for the user who either sends or receives video.
Cisco Jabber for Windows
stops functioning correctly if you end a video call after the video adapts from a low resolution up to a high resolution. For example:
The video call begins with a resolution of 320x240.
The video resolution then quickly adapts up to a resolution of 640x480.
You end the video call.
Cisco Jabber for Windows stops functioning correctly.
To resolve these issues, you should remove the Ricoh driver for your integrated camera so that your computer uses the default Microsoft UVC driver.
This issue has occurred with the following Ricoh driver versions:
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.
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.
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.
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.
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.
Contacting Federated Users After Changing Privacy Policies
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.
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 video and video desktop sharing occurs if users de-escalate from a video call to an audio only call.
Desk Phone Video Capabilities
The following considerations and limitations apply to desk phone video capabilities:
You cannot use desk phone video capabilities on Microsoft Windows Vista.
You cannot use desk phone video capabilities on devices if video cameras are attached to the devices, such as a Cisco Unified IP Phone 9971. You can use desk phone video capabilities if you remove video cameras from the devices.
You cannot use desk phone video capabilities with devices that do not support CTI.
Video desktop sharing, using the BFCP protocol, is not supported with desk phone video.
It is not possible for endpoints that use SCCP to receive video only. SCCP endpoints must send and receive video. Instances where SCCP endpoints do not send video result in audio only calls.
7900 series phones must use SCCP for desk phone video capabilities. 7900 series phones cannot use SIP for desk phone video capabilities.
If a user initiates a call from the keypad on a desk phone device, the call starts as an audio call on the desk phone device. The client then escalates the call to video. For this reason, you cannot make video calls to devices that do not support escalation, such as H.323 endpoints. To use desk phone video capabilities with devices that do not support escalation, users should initiate calls from the client.
A compatibility issue exists with Cisco Unified IP Phones that use firmware version SCCP45.9-2-1S. You must upgrade your firmware to version SCCP45.9-3-1 to use desk phone video capabilities.
Some antivirus or firewall applications, such as Symantec EndPoint Protection, block inbound CDP packets, which disables desk phone video capabilities. You should configure your antivirus or firewall application to allow inbound CDP packets. The following article provides additional details about this issue: http://www.symantec.com/docs/TECH105234
Extension Mobility Cross Cluster
Cisco Jabber for Windows does not currently support extension mobility cross cluster (EMCC).
Extend and Connect Capabilities
The following considerations and limitations apply to extend and connect capabilities:
Two or more users cannot use the same remote destination.
Users cannot use the same remote destination for multiple devices.
You cannot provision extend and connect capabilities for devices that you configure as endpoints on the Cisco Unified Communications Manager cluster.
Cisco recommends that you use extend and connect capabilities with Cisco Unified Communications Manager 9.1(1) and higher only.
New Contacts Display in Directory Search Results
When users interact with new contacts, those contacts display in the Directory search results until the users restart Cisco Jabber for Windows. After users restart the client, the new contacts display in the Recents search results.
UseSecureConnection Parameter Change
As of Cisco Jabber for Windows version 9.1.0, the UseSecureConnection parameter specifies if Cisco Jabber for Windows uses simple authentication to connect to the directory service.
In the 9.0.x version of Cisco Jabber for Windows, the UseSecureConnection parameter enables or disables encryption of data between Cisco Jabber for Windows and the directory service.
If you plan to upgrade from Cisco Jabber for Windows version 9.0.x, and you specify the UseSecureConnection parameter in a configuration file, you must adjust your configuration to reflect this change.
Samsung Kies Compatibility
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.
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
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.
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.
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.
Conferencing Profile Requirements for the User Interface
You must provision users with conferencing profiles in
Cisco Unified Presence
Cisco Unified Communications IM and Presence
for the following to be available in the
Cisco Jabber for Windows
Meetings tab on the Options window
Cisco WebEx meetings escalation icons on chat and call windows
Integration tab on the Options window
The default calendar integration is set to Microsoft Outlook. Users can access their calendar events from Microsoft Outlook without the Integration tab. However, users cannot access their calendar events from IBM Lotus Notes or Google Calendar if the Integration tab is not available.