EMM Support for Microsoft Intune and BlackBerry Dynamics
Enterprise Mobility Management (EMM) supports two new clients:
-
Cisco Jabber for Intune
-
Cisco Jabber for BlackBerry
Your organization can deploy these clients to enforce policies for using Jabber on mobile devices in deployments that allow "Bring Your Own Device".
Use the new EMMType parameter to control the Jabber clients on which your users can sign in.
For details, see the following guides:
-
Planning Guide for Cisco Jabber
-
Jabber deployment guides
-
Parameters Reference Guide for Cisco Jabber
Cisco Jabber for Intune
For Microsoft Intune, your administrator sets up protection policies in Microsoft Azure to control use of the Jabber for Intune client. Users download the new client from the App Store or Google Play Store. When the user runs the new client, it synchs with the policies that the administrator created.
For Android devices, users first install and sign into the Intune Company Portal on their device to get the protection policies from Azure.
Cisco Jabber for BlackBerry
For BlackBerry Dynamics, your administrator sets up policies in the BlackBerry Unified Endpoint Management (UEM) to control use of the Jabber for BlackBerry client. Users download the new client from the App Store or Google Play Store. The new client has integrated the BlackBerry SDK and can directly fetch the policies from BlackBerry UEM.
Cisco Jabber for BlackBerry Release 12.8(1)
Cisco Jabber for BlackBerry 12.8(1) is now available in the App Store and Google Play Store. Jabber for BlackBerry is undergoing BlackBerry certification and isn’t yet available in BlackBerry Marketplace.
This release on Android adds support for sending emails with BlackBerry Works. This feature requires that your administrator enable the DLP policy in the BlackBerry UEM.
Cisco Jabber for Intune Release 12.8(2)
This release includes stability improvements.
Cisco Jabber for BlackBerry Release 12.8(2)
This release includes stability improvements and these features:
-
Support for configuring some parameters through the app, such as ServicesDomain, VoiceServicesDomain, ServiceDiscoveryExcludedServices, and ServicesDomainSsoEmailPrompt
-
Added a configuration setting to enable cross-launching Webex Meetings. This setting allows Webex Meetings as an exception when the BlackBerry Dynamics container doesn't allow other non-Dynamics apps.
Additional Maintenance Releases
For additional maintenance release information, refer to:
-
Feature enhancements — see https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-release-notes-list.html for the latest version of release notes.
-
Caveats — see https://bst.cloudapps.cisco.com/bugsearch/ for latest caveat updates.
-
Security Advisories — see https://tools.cisco.com/security/center/publicationListing.x for a listing of the latest advisories.
What's New in Release 12.8(2)
This maintenance release contains defect fixes. See the Caveats section for details.
What's New in Release 12.8(1)
Force a Reset When User Signs Out
This release adds the ResetOnLogOutOnMobile parameter to force an automatic reset of the client when the user signs out. The Sign Out button changes to Reset Jabber when you set this parameter.
More Visible Phone Service Disconnection Warnings
This release adds the GlobalPhoneServiceErrorOnMobile parameter to make the error message more visible to the user when the phone service is registered on another device. When you set this parameter to true, the error message appears at the top of the client, rather than in the Calls tab.
What's New in Release 12.8
Android 10 Support
We added support for Android 10.
Support for Facial Recognition on Android Devices
You can now use facial recognition to authenticate on appropriate Android devices.
In previous releases, users can authenticate by fingerprint on Android devices. You can disable this capability with the LocalAuthenticationWithBiometrics parameter. For more information on this feature, see the section on biometric authentication in the Feature Configuration for Cisco Jabber.
Hunt Group Enhancements
You can now sign in or out of hunt groups on mobile clients.
For more information, see the hunt group section in the Feature Configuration for Cisco Jabber guide.
Voicemail Improvements
We extended the Release 12.7 voicemail improvements from the desktop clients to the mobile clients.
Users can create voicemails without making a call and then send the voicemail to one or more contacts. The voicemail server's administrator can also create distribution lists to which users can send voicemails. Users can select recipients from the voicemail server's catalog.
Users can directly reply to the sender of a voicemail or to all recipients of that message. Users can also forward voicemails to new recipients.
Force Upgrading on Android Devices
Administrators can enforce upgrading to the latest version from the Google Play with the ForceUpgradingOnMobile parameter.
Custom Contacts for Team Messaging Mode
Jabber Team Messaging Mode deployments support custom contacts. You can now create, edit, and delete custom contacts on a desktop client. These contacts are also available in your mobile client. But, you can't create, edit, or delete custom contacts from the mobile client.
Jabber Analytics through Webex Control Hub
![]() Note |
This release note describes a new feature in Webex Control Hub that impacts Jabber deployments. Because it’s a change in Control Hub, you can access this feature for any release of Jabber. |
If your deployment has Webex Control Hub configured, you can access Jabber analytics through the Control Hub. This feature is available for the following deployment modes:
-
On-premises with full UC
-
On-premises IM-Only
-
On-premises Phone-Only
-
Jabber with Webex Messenger
Jabber analytics provides key performance indicators with trending, such as:
-
Active users
-
Messages sent
-
Calls made or received from Jabber
-
Screen share from Jabber
See the Feature Configuration for Cisco Jabber guide for more information.
Requirements
Cisco Jabber Requirements
Many Cisco Jabber requirements are common between client types. Client specific requirements are documented in the Release Notes, all other requirements are documented in the Planning Guide for Cisco Jabber.
Operating Systems for Cisco Jabber for Android
Refer to the Play Store for the latest supported operating system version information.
![]() Note |
Cisco Jabber for Android is available as a 32-bit app and a 64-bit app. If your Android device has a 64-bit OS, you get a faster and richer experience by running the 64-bit Jabber client. |
![]() Note |
If Cisco Jabber is installed on Android 6.0 Marshmallow OS or later, and if it is kept idle:
Tap Change Settings and ignore battery optimization to receive calls and messages. |
Last Jabber Release for Android 5.x Support
Cisco Jabber 12.8 is the last release that supports devices running Android 5.x.
The next Jabber release will end support for all devices that cannot upgrade to Android 6.x.
Hardware Requirements for Cisco Jabber for Android
Minimum requirements for Android devices:
Android Operating System |
CPU |
Display |
---|---|---|
5.0 or later |
1.5 GHz dual-core Recommended: 1.2-GHz quad-core or higher |
For two-way video: 480p x 800p or higher. For IM only: 320p x 480p or higher. |
Cisco Jabber for Android supports Full UC mode in the devices with these OS versions:
Device |
Model |
Minimum Android OS Version |
Notes |
---|---|---|---|
BlackBerry |
Priv |
5.1 |
If you remove Jabber from the recently viewed apps list and you keep the device idle for some time, then Jabber becomes inactive. |
Fujitsu |
Arrows M357 |
6.0.1 |
|
|
Nexus 4 |
5.1.1 |
|
Nexus 5 |
5.0 |
||
Nexus 5X |
6.0 |
||
Nexus 6 |
5.0.2 |
||
Nexus 6P |
6.0 |
For Google Nexus 6P with Android OS version 6.x or 7.0, your administrator must set your Jabber phone service as a secure phone service. Otherwise, your device might not respond. No action is required for Android OS version 7.1 or later. |
|
Nexus 7 |
5.0 |
||
Nexus 9 |
5.0.2 |
||
Nexus 10 |
5.0 |
||
Pixel |
7.0 |
||
Pixel C |
6.0 |
||
Pixel XL |
7.0 |
||
Pixel 2 |
8.0 |
During a Jabber call, if the user switches audio from the mobile device to a headset, momentary audio issues are possible. |
|
Pixel 2 XL |
8.0 |
During a Jabber call, if the user switches audio from the mobile device to a headset, momentary audio issues are possible. |
|
Pixel 3 |
8.0 |
If you use the attached headset with the phone, then there might be some issues with the audio for few seconds. |
|
Pixel 3 XL |
8.0 |
If you use the attached headset with the phone, then there might be some issues with the audio for few seconds. |
|
Honeywell Dolphin |
CT50 |
5.0 |
|
CT40 |
7.1.1 |
||
CT60 |
7.1.1 and 8.1 |
We only support the CT60 with Android OS 7.1.1 and 8.1. |
|
HTC |
10 |
6.0 |
|
A9 |
6.0 |
||
E9 PLUS |
5.0.2 |
||
M7 |
5.0 |
||
M8 |
5.0 |
||
M9 |
5.0 |
||
One Max |
5.0 |
||
X9 |
6.0 |
||
Huawei 1 |
Honor 7 |
5.0 |
|
M2 |
5.0 |
||
Mate 7 |
5.0 |
||
Mate 8 |
6.0 |
||
Mate 9 |
6.0 |
||
Nova |
7.0 |
||
Mate 10 |
8.0 |
||
Mate 10 Pro |
8.0 |
||
P8 |
5.0 |
||
P9 |
6.0 |
||
P10 |
7.0 |
||
P10 Plus |
7.0 |
||
P20 |
8.0 |
||
P20 Pro |
8.0 |
||
Mate20 |
8.0 |
||
Mate20 Pro |
8.0 |
||
P30 |
9.0 |
||
P30 Pro |
9.0 |
||
LG |
G2 |
5.0 |
|
G3 |
5.0 |
||
G4 |
5.1 |
||
G5 |
6.0 |
||
G6 |
7.0 |
||
V10 |
5.0 |
||
V30 |
8.0 |
||
Motorola |
MC40 |
5.0 |
Cisco Jabber supports only audio mode with an MC40 device. Jabber doesn’t support launching Webex Meetings from an MC40 device. |
Moto G4 |
5.0 |
||
Moto G5 |
7.0 |
||
Moto G6 |
8.0 |
||
Moto X (1st Gen.) |
5.0 |
||
Moto Z Droid |
6.0 |
||
Nokia |
6.1 |
8.0 |
|
OnePlus |
One |
5.0 |
|
5 |
8.0 |
||
5T |
8.0 |
||
6 |
9.0 |
||
6T |
9.0 |
||
Panasonic |
Toughpad FZ-X1 |
5.0 |
Contact your administrator to set your Jabber phone service to be secure. Jabber plays ringback tone and busy tone at 24 kHz. |
Samsung |
All |
5.0 |
|
Smartisan |
M1L |
6.0.1 |
|
Sonim |
XP8 |
7.1.1 |
|
Sony Xperia |
M2 |
5.0 |
|
XZ |
7.0 |
||
XZ1 |
8.0 |
||
XZ2 |
8.0 |
||
XZ3 |
9.0 |
||
Z1 |
5.0 |
||
Z2 |
5.0 |
||
Z2 tablet |
5.0 |
||
Z3 |
5.0 |
Sony Xperia Z3 (Model SO-01G) with Android OS 5.0.2 has poor audio on Jabber calls. |
|
Z3 Tablet Compact |
5.0 |
||
Z3+/Z4 |
5.0.2 |
Video call is unstable on Sony Z3+/Z4. Try disabling your self-video for a video call. Otherwise, make a voice call only. |
|
Z4 TAB |
5.0 |
||
Z5 Premium and Z5 |
5.0.2 |
||
ZR/A |
5.0 |
Sony devices with Android OS 6.0 can’t play voicemail in Jabber. |
|
Xiaomi |
4C |
5.1 |
Only the 32-bit version runs on these devices. |
MAX |
5.1 |
||
Mi 4 |
5.0 |
||
Mi 5 |
6.0 |
||
Mi 5s |
7.0 |
||
Mi 6 |
7.0 |
||
Mi 8 |
8.0 |
||
Mi 9 |
9.0 |
||
Pocophone |
8.0 |
||
Mi Note |
5.0 |
Only the 32-bit version runs on these devices. |
|
Mi Note 2 |
7.0 |
||
Mi Pad 2 |
5.1 |
||
Mi MIX 2 |
8.0 |
||
Mi A1 |
8.0 |
||
Redmi 3 |
5.1 |
||
Redmi Note 3 |
5.1 |
||
Redmi Note 4X |
6.0.1 |
||
Redmi Note 5 |
8.0 |
||
Redmi Note 6 Pro |
8.1 |
||
Zebra |
TC70 |
5.0 |
TC70 devices might sometimes have issues connecting to a Wi-Fi network configured over DHCP. In TC70, the default value of Keep wifi on during sleep is Off, set it to Always On for use with Jabber. |
TC75X |
6.0 |
||
TC51 |
6.0 |
Jabber Support for Samsung Knox
Cisco Jabber for Android supports Samsung Knox as follows:
Knox Version |
Samsung Devices |
---|---|
2.6 |
Note 4 Note 5 Note Edge S5 S6 S6 Edge S6 Edge Plus S7 S7 Edge Note 10.1 (2014 Edition) |
2.7.1 |
Galaxy Note5 |
3.1 |
Galaxy A5 (2017) |
3.2 |
Galaxy On5 (2016) |
3.3 |
Galaxy S10 |
![]() Note |
When you run Cisco Jabber for Android inside Samsung Know, the security design of Samsung Knox requires you to unlock Knox first. You can't answer or decline a call with Jabber until you unlock Knox. |
Jabber Supports Samsung Dex
Cisco Jabber for Android supports Samsung Dex in Samsung S8, S8 Plus, and Note 8.
Support Policy on Earlier Android Versions for Cisco Jabber
Due to an Android kernel issue, Cisco Jabber can’t register to the Cisco Unified Communications Manager on some Android devices. To resolve this problem, try the following:
Upgrade the Android kernel to 3.10 or later version.
Set the Cisco Unified Communications Manager to use mixed mode security, enable secure SIP call signaling, and use port 5061. See the Cisco Unified Communications Manager Security Guide for your release for instructions on configuring mixed mode with the Cisco CTL Client. You can locate the security guides in the Cisco Unified Communications Manager Maintain and Operate Guides. This solution applies to the following supported devices:
Device Model |
Operating System |
---|---|
HTC M7 |
Android OS 5.0 or later |
HTC M8 |
Android OS 5.0 or later |
HTC M9 |
Android OS 5.0 or later |
HTC One Max |
Android OS 5.0 or later |
Sony Xperia M2 |
Android OS 5.0 or later and kernel version earlier than 3.10.49.
If the device's Android OS is 5.0.2 or later and kernel version is 3.10.49 or later, then the device can support nonsecure mode. |
Sony Xperia Z1 |
|
Sony Xperia ZR/A |
|
Sony Xperia Z2 |
|
Sony Xperia Z2 tablet |
|
Sony Xperia Z3 |
|
Sony Xperia Z3 Tablet Compact |
|
Xiaomi Mi4 |
Android OS 5.0 or later |
Xiaomi Mi Note |
Android OS 5.0 or later |
Xiaomi Mi Pad |
Android OS 5.0 or later |
Sonim XP7 |
Android OS 5.0 or later |
Honeywell Dolphin CT50 |
Android OS 5.0 or later |
Supported Bluetooth Devices
Bluetooth Devices |
Dependencies |
---|---|
Cisco 561 |
|
Cisco 562 |
|
Plantronics Voyager Legend |
|
Plantronics Voyager Legend UC |
|
Plantronics Voyager edge UC |
|
Plantronics Voyager edge |
|
Plantronics PLT focus |
|
Plantronics BackBeat 903+ |
If you use a Samsung Galaxy S4, you can experience problems due to compatibility issues between these devices. |
Jabra Motion |
Upgrade Jabra Motion Bluetooth headset to firmware version 3.72 or above. The Jabra Motion Bluetooth headsets with firmware version 3.72 or above supports Cisco Jabber call control. |
Jabra Wave+ |
|
Jabra Biz 2400 |
|
Jabra Easygo |
|
Jabra PRO 9470 |
|
Jabra Speak 510 |
|
Jabra Supreme UC |
|
Jabra Stealth |
|
Jabra Evolve 65 UC Stereo |
|
Jawbone ICON for Cisco Bluetooth Headset |
If you use a Samsung Galaxy S4, you can experience problems due to compatibility issues between these devices. |
Bluetooth limitations:
-
Using a Bluetooth device on a Samsung Galaxy SIII may cause distorted ringtone and distorted call audio.
-
If a user disconnects and reconnects the Bluetooth Headset during a Jabber call, then the user can’t hear the audio. This limitation applies to Smartphones with versions earlier to Android 5.0 OS.
-
In Sony Z4 / LG G4 /Devices with OS Android 6.0, users can experience audio loss when switching to a Bluetooth headset after starting a Jabber call. As a workaround, switch the audio output to a speaker and then switch back to Bluetooth. Or connect the Bluetooth headset before making a Cisco Jabber call.
Supported Android Wear
Cisco Jabber runs on all Android wear devices with Android OS 5.0 or later and Google service 8.3 or later. We test Cisco Jabber on these Android Wear devices:
-
Fossil Gen 3 SmartWatch
-
Huawei watch
-
LG G Watch R
-
LG Watch Urbane
-
Moto 360
-
Moto 360 (2nd Gen)
-
Samsung Gear Live
-
Sony SmartWatch 3
![]() Note |
The Cisco Jabber installer for Android wear devices is separate from the main Jabber APK file. Users get the Android wear installer from the Google Play store when they pair the wear device with a mobile device. |
Supported Chromebook Models
Chromebook must have Chrome OS version 53 or later. Users can download Cisco Jabber for Android from Google Play Store.
-
HP Chromebook 13 G1 Notebook PC
-
Google Chromebook Pixel
-
Google Chromebook Pixelbook
-
Samsung Chromebook Pro
-
Asus C302
Requirements to Support IPv6 in Android
Android OS Requirement
Android 5.0 and later
Network Requirements
-
IPv4 Only mode (Android accepts only IPv4 address)
-
Dual Stack with SLAAC (Android accepts both IPv4 and IPv6 address)
-
NAT64 or DNS64 (server uses IPv4 address and client uses IPv6 address)
Limitations
-
DHCPv6 Limitation
-
DHCPv6 is not supported on an Android device.
-
-
Android OS Limitation
-
Android OS does not support IPv6-only network. For more information on this limitation, see the Android developer link.
-
Limitations and Restrictions
Limitations
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.
Restrictions
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.
Caveats
Caveats describe unexpected behavior. The following sections describe how to obtain the latest information.
Bug Severity Levels
Known defects, or bugs, have a severity level that indicates the priority of the defect. These release notes include the following bug types:
-
All severity level 1 or 2 bugs
-
Significant severity level 3 bugs
-
All customer-found bugs except severity level 6 enhancement requests
Severity Level |
Description |
---|---|
1 Catastrophic |
Reasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. No workarounds exist. |
2 Severe |
Important functions are unusable and workarounds do not exist. Other functions and the rest of the network is operating normally. |
3 Moderate |
Failures occur in unusual circumstances, or minor features do not work at all, or other failures occur but low-impact workarounds exist. This is the highest level for documentation bugs. |
4 Minor |
Failures occur under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds and performance impact is tolerable. |
5 Cosmetic |
Defects do not cause any detrimental effect on system functionality. |
6 Enhancement |
Requests for new functionality or feature improvements. |
Search for Bugs
To search for bugs not listed here, use the Bug Search Tool.
Procedure
Step 1 |
To access the Bug Search Tool, go to https://tools.cisco.com/bugsearch/search. |
Step 2 |
Sign in with your Cisco.com user ID and password. |
Step 3 |
To look for information about a specific problem, enter the bug ID number in the Search for field, then press Enter. Alternatively, you can search by product and release. |
Resolved Caveats in Release 12.8(2)
Identifier |
Severity |
Headline |
---|---|---|
3 |
Jabber 12.8.1 and 12.8.2 fails to get phone services over MRA |
|
3 |
Jabber for Android 12.7 not displaying "Far End Camera Control" (FECC) |
|
4 |
Jabber Android not consistently ringing for incoming calls when in background or in sleep mode |
|
4 |
Jabber on Android freezes after end call |
Open Caveats in Release 12.8(1)
Identifier |
Severity |
Headline |
---|---|---|
3 |
[Jabber Android] emoticon replace by ', the display is wrong |
Resolved Caveats in Release 12.8(1)
Identifier |
Severity |
Headline |
---|---|---|
2 |
Certificate based SSO stopped working with Jabber Android 12.8.0.3 |
|
2 |
Jabber for Android does not send IPv6 address in SDP for outgoing INVITE |
|
3 |
Jabber for Android may experience crashes when application is left running overnight |
|
3 |
Calls drop when using 3rd party VPN over 4g & wifi at the same time |
|
3 |
SIP-URI dialing does not work in 'Jabber for Android' with default jabber-config.xml settings |
|
3 |
Jabber android can only see uri in the missed call record even with sipuridialling set to false. |
|
3 |
Jabber not caching the Local IP Address on Sign-in or launch leading to re-connect on network event |
Open Caveats in Release 12.8
Identifier |
Severity |
Headline |
---|---|---|
2 |
Jabber for Android loses incoming call in background |
Resolved Caveats in Release 12.8
Identifier |
Severity |
Headline |
---|---|---|
3 |
Jabber for Android does not refresh access token in failover scenario over MRA |
|
3 |
Notification is sending for two times for screen shot alone in Cisco Jabber for android |
|
3 |
Call via MRA does not update Jabber Display Name |
|
3 |
Jabber for android phone services fails after upgrading to 12.7.2 version |
|
3 |
Jabber for Android may experience crashes when application is left running overnight |