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.0.6 with defect number CSCug51731.
Video Desktop Sharing Considerations
Video desktop sharing refers to desktop sharing functionality on CSF devices on Cisco Unified Communications Manager that are BFCP-enabled.
As of this release, Cisco Jabber for Windows supports video desktop sharing in software phone mode only. Video desktop sharing is not available in desk phone mode.
Migration of your video desktop sharing configuration is not possible. 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 configure video desktop sharing on 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. For example, you should not attempt to enable video desktop sharing on a Cisco Jabber for MacCSF device.
If Cisco Jabber for Windows cannot resolve contacts by their phone numbers, video desktop sharing is available from the active call window only, not the chat window. To prevent this issue, you should ensure that user phone numbers in your directory are correct.
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.
If you run two clients that use the same CSF device, contention occurs for that CSF device. This contention can result in dropped calls, busy tones, or other unpredictable behavior
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.
Audio Device Configuration on Microsoft Windows
As a general rule, you should do one of the following to configure audio devices in Microsoft Windows:
Set the correct device as your default communications device.
For example, set your external headset as your default communications device, not speakers built into your computer.
Select Do nothing on the Communications tab on the Sound window in Microsoft Windows.
Selecting this setting ensures that Microsoft Windows does not attempt to adjust the sound volume during audio or video calls.
You can also apply this setting through the Microsoft Windows registry with the following steps:
If you do not correctly configure your audio devices on Microsoft Windows, you might experience unexpected behavior or difficulty receiving audio with your device. See the appropriate Microsoft Windows documentation for more information on configuring audio devices.
Options Configuration in Cisco Jabber for Windows
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.
The Video and Calls tabs are not available on the Options window if:
Users select the Use my phone for calls option.
Users do not add their credentials on the Phone accounts tab on the Options window.
Cisco Jabber for Windows deletes phone credentials when different primary users sign in, or attempt to sign in, to the same instance of the client. Even if a different primary enters credentials to sign in but does not sign in successfully, the client deletes any existing phone credentials. The following steps are an example of this functionality:
User A signs in to Cisco Jabber for Windows.
User A selects File > Options > Phone accounts and specifies phone credentials.
User A signs out of Cisco Jabber for Windows.
User B signs in to the same instance of Cisco Jabber for Windows.
Cisco Jabber for Windows deletes the phone credentials that user A specified.
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.
For example, you change a user's Active Directory account password. Cisco Unified Communications Manager synchronizes this password with the phone service password. You should notify the user to update their password in Cisco Jabber for Windows as follows:
Log in to Cisco Jabber for Windows.
Select File > Options.
Select Phone accounts.
Specify the new password in the Password in the Phone services section.
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.
Desktop sharing capabilities that Cisco WebEx provides are currently available in English only.
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:
End Users Cannot Retrieve Phone Account Details
Problem description:Cisco Jabber for Windows users cannot retrieve phone account details when they log in to an extension mobility profile. As a result, error messages display in the Phone services section of the Phone accounts tab on the Options dialog box.
The affected users have multiple devices configured on Cisco Unified Communications Manager.
The following exceptions are written to the csf-unified.log file in the %USER_PROFILE%\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs directory:
<time_stamp> DEBUG [0x00001d80] [src\config\CCMCIPClient.cpp(230)] [csf.ecc] [curlDebugCallback] -
Resolution: To resolve this issue, do the following:
Disassociate the affected users from all extension mobility profiles.
Contact your Cisco support representative and request an Engineering Special (ES) to resolve this issue on Cisco Unified Communications Manager.
After you apply the ES on Cisco Unified Communications Manager, you can re-associate the affected users with the extension mobility profiles.
On-Premises Integration with UDS
As of version 9.0.4, you must specify UDS as the value for the DirectoryServerType parameter in your Cisco Jabber for Windows configuration file for directory integration with Cisco Unified Communications Manager User Data Service. For more information about the DirectoryServerType parameter, see the Directory Configuration topic in the Configure Cisco Jabber for Windows chapter of the Cisco Jabber for Windows Administration Guide. Deployments with Enhanced Directory Integration are not affected by this change. EDI is the default value for the DirectoryServerType parameter in version 9.0.4.
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.
Contact Photos in GIF Format
Contact photos in GIF format might render incorrectly or with less than optimal quality. To obtain the best quality, you should use PNG format for your contact photos.
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.