Limitations and important considerations
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 Mac CSF 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.
Multiple devices and clients configuration
- 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
- In some instances, Cisco Jabber for Windows users might be disconnected if they have both a CSF device and TNT device such as Cisco Jabber for iPhone configured on Cisco Unified Communications Manager.
- 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 WindowsAs a general rule, you should do one of the following to configure audio devices in Microsoft Windows:
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.
- 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.
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:
- 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:
- 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:
- In an on-premises deployment, you can specify a configuration parameter to use the phone service credentials specified on Cisco Unified Communications Manager. See the Phone service credentials configuration parameter topic in the Cisco Jabber for Windows Administration Guide for more information.
- In a hybrid cloud-based deployment, you can specify a configuration parameter to use the voice mail service credentials specified on Cisco Unity Connection. See the Voice mail service credentials configuration parameter topic in the Cisco Jabber for Windows Administration Guide for more information.
Integration with Microsoft SharePoint
You must use Microsoft Internet Explorer for availability status to be displayed in Microsoft SharePoint. Availability status does not display in Microsoft SharePoint if users access the site with other browsers such as Mozilla Firefox.
To enable availability status in Microsoft SharePoint, add the Microsoft SharePoint site to the list of trusted sites in Microsoft Internet Explorer.
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 W500The 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:
To resolve these issues, you should remove the Ricoh driver for your integrated camera so that your computer uses the default Microsoft UVC driver.
Cisco Jabber for Windows supports Computer Telephony Integration (CTI) servitude, or CTI control of Cisco Jabber for Windows from a third party application.
For more information on CTI servitude, see the CTI documentation for the appropriate version of Cisco Unified Communications Manager.
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] - <html> <body> org.apache.jasper.JasperException: java.lang.reflect.InvocationTargetException<br> <!-- org.apache.jasper.JasperException: java.lang.reflect.InvocationTargetException at org.apache.jasper.runtime.JspRuntimeLibrary.handleSetPropertyExpression(JspRuntimeLibrary.java:622) at org.apache.jsp.ControlledDevices_jsp._jspx_meth_c_005fforEach_005f0(ControlledDevices_jsp.java:834) at org.apache.jsp.ControlledDevices_jsp._jspService(ControlledDevices_jsp.java:180) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)Resolution: To resolve this issue, do the following:
After you apply the ES on Cisco Unified Communications Manager, you can re-associate the affected users with the extension mobility profiles.
- 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.