The following limitations apply to all devices:

• As of Release 12.7, Jabber for Android doesn't support automatically starting with the OS.

• Webex site disclaimers don't appear when you join Webex meetings from Jabber. This limitation applies whether joining from the meeting reminder popup, or by selecting Join in Webex in Jabber.

• If another app is using the camera, Jabber for Android can't start video calls from your Chromebook.

• Because of a limitation of Cisco Unity Connection, the voicemail server can't display the URI for a missed call. This issue occurs when you decline an incoming Cisco Jabber call from a URI and the call diverts to voicemail. If the contact information for the caller contains only a URI, the voicemail server displays the caller as Unknown. If the contact information contains a URI and a directory number, the voicemail server displays the directory number for that contact.

• When you play music with a third-party application, the music doesn't automatically pause when you make or receive a Cisco Jabber for Android video call. To work around this issue, you can open the third-party application to pause and resume the music.

• If you make a Cisco Jabber for Android call using Expressway for Mobile and Remote Access over a 2G, 3G, or 4G network, you may experience audio quality issues from network instability.

• If you use Cisco AnyConnect Secure Mobility Client, MobilePASS one-time password generator from SafeNet, and Cisco Jabber for Android on the same device, you may experience problems due to compatibility issues between these applications. For example, during a Cisco Jabber for Android call, you may hear no audio or one-way audio, or you may experience delays if you transfer the call.

• Some users who have migrated to Common Identity server have an issue signing into Cisco Jabber. These users receive an "Incorrect username or password" error message when they enter their username and password. To resolve the issue, see this troubleshooting article.

• Jabber team messaging mode doesn't support notifications on Android Wear devices.

• Contact Resolution for Enterprise Groups—Jabber resolves contacts in enterprise groups individually rather than all at once. As a result, when you add an enterprise group to your users' contact lists—or if they clear their local cache—they see only the username and domain for each person until they hover over or interact with them.

• Creating and Configuring Devices for Users in Cisco Unified Communications Manager 11.0—If you're creating devices for users in Cisco Unified Communications Manager 11.0, you can specify a key order:

  • RSA Only

  • EC Only

  • EC Preferred

  • RSA Backup

  However, Jabber doesn't support the EC Only option, and if you select it, the client fails to connect to the server.

• In a Mobile and Remote Access non-SSO environment, when Jabber loses its connection to the Cisco VCS Expressway server there's an interval of 120 seconds between sending connection requests. This interval prevents multiple requests to the server from multiple clients. During this 120-seconds interval, even if your network connection is active, Jabber remains inactive.

• There's an audio quality issue in Samsung devices with chipset Exynos 7580. The audio becomes unclear when the device screen is off. Here is the device list:

  • Samsung Galaxy A3 2016

  • Samsung Galaxy A5 2016

  • Samsung Galaxy A7 2016

  • Samsung Galaxy S5 Neo

  • Samsung Galaxy J7

  • Samsung Galaxy View

• When you install Jabber for the first time, Samsung devices automatically put Jabber in the unmonitored apps list. The device doesn't put unmonitored apps to sleep while they run in the background. However, if you upgrade your Samsung OS from a version without unmonitored apps list, you have to add Jabber to the unmonitored apps list manually.

• For Cisco TelePresence Video Communication Server Control (VCS) versions earlier than 8.10.X, configure the editable inbound rules to enable the single number reach for users who are using Cisco Jabber over Mobile and Remote Access. For more information, see Limitations in Enable Single Number Reach section from the Feature Configuration Guide for Cisco Jabber 12.0.

• If your users have issues with signing into Cisco Jabber in SSO mode, they can upgrade Android System WebView and Chrome browser to resolve the issue. Users can upgrade Android System WebView and Chrome browser from Google Play Store.

The following restrictions apply to all devices:

• HTTP basic SAML SSO authentication—Sign in fails when switching users with the Reset Jabber option. Reset Cisco Jabber, quit the application fully in the Android OS, and try again.

• Because of the large number of third-party applications that support the tel:// URI feature, we cannot guarantee interoperability of this feature on all third-party applications. In some third-party applications, this feature allows you to click a tel:// link and select Cisco Jabber for Android to call.

• When transferring a file, the filename cannot exceed 168 characters (including extension). If you attempt to send a file with a longer name, you are notified that you have exceeded 168 characters.

• Security Survivable Remote Site Telephony (SRST) is not supported in Cisco Jabber for Android Release 10.6.

• If the Cisco Unified Communications Manager version is 11.0 and later, and you don't accept an invalid certificate when prompted within 10 seconds, for some HTTPS connections, the function of your application may be affected. You may have some issues such as, not being able to download some configuration from the server, or not being able to connect to the phone service or the voicemail.

• Only for users on SSO account Jabber stops working if the Android Webview is reset, upgraded, or restarted.

• During file transfer, only files with JPEG file format are compressed.

• Cisco WebEx Meetings—If the meeting siteType is "ORION", then Cisco Jabber for Android cannot start WebEx Meeting over Expressway for Mobile and Remote Access network.

• Auto authentication at startup is no longer supported.

• Jabber turns off Wi-Fi when you answer a call on cellular network to avoid call drops.