Release Notes for Cisco Jabber for Android 12.6

What's New in Cisco Jabber for Android 12.6(1)

Problem Report Save Location

Users can now save problem reports to a local directory instead of having them automatically attached to a blank email. This feature is turned on by default. For more information, see the SaveLogToLocal parameter in the Parameters Reference Guide for Cisco Jabber 12.6.

Support for Viewing ECM Files

In team messaging mode, users are now able to view files sent to them via Enterprise Content Management (ECM) rather than from a local directory. Selecting a shared ECM file will cross-launch a web browser where the file can be viewed.

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats 12.6(1) section for a list of caveats fixed in this release.

What's New in Cisco Jabber for Android 12.6

Jabber Team Messaging Mode

Support on Jabber for Android—Jabber for Android users have a new cloud-based deployment option that lets them work together in a team messaging mode from their Jabber client. In team messaging mode, users get a new Chats tab in their client that they can use for group discussions.

Users will be able to:

- Send and receive direct messages and group messages, and get read receipts for them.

- Use key messaging features like sending files, flagging messages, deleting messages, using @mentions, emoticons, gifs, announcement mode, and message encryption.

- Filter messages (All, Direct Messages, Spaces, Unread, @mention, Favorites, Notifications, Flags).

- See the list of their spaces.

- Turn a conversation into a Webex meeting.

- Show and display the following presence states: Active, Inactive, In a meeting, In a call, Presenting, Do Not Disturb, and Out of Office.

- Search for people, spaces, messages and files.

For a detailed look at what Jabber team messaging mode is and how it works, see the Cloud-Based Deployment Scenarios in the Planning Guide for Cisco Jabber and the workflow for Cisco Webex Platform service in Cloud and Hybrid Deployments for Cisco Jabber.

Upgrade Profiles—You can create upgrade profiles on the Webex Control Hub for individual users or for your organization. Use the upgrade profiles to control which version of Jabber team messaging mode your users are on. For more information about setting up upgrade profiles, see how to Add Upgrade Profiles in the Webex Control Hub in Cloud and Hybrid Deployments for Cisco Jabber 12.6.

Search on CI, UDS and LDAP—Users with Jabber team messaging mode can now search for contacts and their profiles from the company directory (on UDS/LDAP), even if the contact is not in the CI. With the search results, you'll see the person's profile picture, and be able to call them. To define the scope of contacts search, CI-only search is the default behavior. For more information, check out the ContactProfileSource and ContactSearchSource parameters in the Parameters Reference Guide for Cisco Jabber 12.6.

Meeting Controls for Video Device-Enabled Webex Meetings—Users can join Cisco Collaboration Meeting Rooms from Jabber, where they can see the participant list, change the video layout, lock and record the meeting, mute, unmute, and remove participants, and assign host privileges. Jabber supports using PIN numbers to access video device-enabled Webex meetings.

Feature Improvements

Offline Message Support For Jabber and Webex Teams—We have improved the messaging experience for Webex Messenger users who are enabled for interoperability between Cisco Jabber and Cisco Webex Teams. Now when users who have been using Cisco Webex Teams sign back in to Jabber after a period being offline, they will no longer get an alert telling them that new messages are available in Webex Teams, with a link to the Webex Teams web client. Instead, they will receive their new messages in Jabber for their missed one-to-one conversations.

To enable this feature, see how to Set Up Interoperability for Cisco Webex Teams and Jabber.

ActiveControl Support Over the MRA Expressway—ActiveControl is only accessible to users who are outside of the corporate network by using the Expressway for Mobile and Remote Access (MRA). Using ActiveControl over MRA is done using SIP oAuth or CAPF enrollment. For environments without secure phones, users can now authenticate to the network using their username and password when moving onto MRA.

For information about setting up ActiveControl, see Feature Configuration for Cisco Jabber 12.6.

Hide Persistent Chat Room Members—Jabber now supports a setting in Cisco Unified Communications Manager that lets you decide whether members and administrators of a persistent chat room are listed in the room even when they don't have the chat window open. Changes to this setting apply only to restricted rooms that are created after the change has been made. For more information, see the Persistent Chat Rooms section in Feature Configuration for Cisco Jabber 12.6.

Support for Special Characters—Jabber now supports special characters in usernames during login.

UDS Failover—In the event that your Cisco Unified Communications Manager User Data Service - UDS1(UCM1) - server becomes unavailable, Jabber can now dynamically failover to the UDS2(UCM2) server for contact resolution and search. For more information, see the Planning Guide for Cisco Jabber.

SIP-URI Display—It is now possible to display SIP-URI details for all users, even those in the same domain.

Disable EULA Embedded Browser Navigation—To comply with industry guidelines, the social media links in pages such as the End User License Agreement and Privacy Policy, are now disabled.

Accessories and Devices

Cisco Headset Support—We've added the Cisco 561 and 562 headset models to the list of supported Bluetooth headset devices.

Android Device and OS Support—We've upgraded the minimum version of Android OS from 4.4 to 5.0.

We also added support for the following devices:

- Google Nexus Pixel 3 - Android OS 8.0 or later

- Google Nexus Pixel 3 XL - Android OS 8.0 or later

- Honeywell Dolphin CT40 - Android OS 7.1.1 or later

- Huawei Mate20 - Android OS 8.0 or later

- Huawei Mate20 Pro - Android OS 8.0 or later

- OnePlus 6 - Android OS 9.0 or later

- OnePlus 6T - Android OS 9.0 or later

- Sonim XP8 - Android OS 7.1.1 or later

- Sony Xperia XZ3 - Android OS 9.0 or later

- Xiaomi Mi8 - Android OS 8.0 or later

- Xiaomi Pocophone - Android OS 8.0 or later

- Zebra TC75X - Android OS 6.0 or later

For a full list of supported Android devices, see Hardware Requirements for Cisco Jabber for Android in the Planning Guide for Cisco Jabber 12.6.

Requirements

- Cisco Jabber Requirements

- Operating Systems for Cisco Jabber for Android

- Hardware Requirements for Cisco Jabber for Android

- Requirements to Support IPv6 in Android

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

If Cisco Jabber is installed on Android 6.0 Marshmallow OS or later, and if it is kept idle:

- The network connection to Cisco Jabber is disabled.

- The users do not receive any calls or messages.

Tap Change Settings and ignore battery optimization to receive calls and messages.

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 now supports Full UC mode in the following new devices with respective version of Operating System provided in the table:

Supported Devices

Device

Device Model

Minimum Android Operating System version

Notes

BlackBerry

Priv

5.1

Blackberry Priv device limitation: If Jabber is removed from the recently viewed apps list, and the device is kept idle for some time, then Jabber becomes inactive.

Fujitsu

Arrows M357

6.0.1

Google Nexus

4

5.1.1

5

5.0

5X

6.0

6

5.0.2

6P

6.0

If you have a Google Nexus 6P device with Android OS version 6.x or 7.0, then contact your administrator to set your Jabber phone service as a secure phone service. Otherwise, your device might not respond. However, if your Android OS version is 7.1 or later, no action is required.

7

5.0

9

5.0.2

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 mobile device to a headset, then there might be some issues with the auido for few seconds.

Pixel 2 XL

8.0

During a Jabber call if the user switches audio from mobile device to a headset, then there might be some issues with the auido for few seconds.

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

CT40

7.1.1

CT50

5.0

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

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

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 MC40 device. Cisco Jabber does not support launching Webex Meetings from MC40 device.

Moto G

5.0

Moto X

5.0

Moto Z Droid

6.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 24kHz.

Samsung

All

5.0

- In the Samsung devices with Android OS 5.x or later, the auto-run option for Jabber must be enabled.

For Android OS 5.x, you can find the auto-run option under Settings and Device Manager.

For Android OS 6.x and later, you can find the auto-run option under App Smart Manager.

- Jabber delays the incoming call notification pop-up on Samsung Galaxy Tab Pro 8.4(Model T320UEU1AOC1) for Canada.

- Jabber delays reconnecting to the network on a Samsung Xcover 3 when it loses Wi-Fi connectivity.

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, you can disable your self-video for a video call or make a voice call only.

Z4 TAB

5.0

Z5 Premium and Z5

5.0.2

ZR/A

5.0

There is a limitation that Sony devices with Android OS 6.0 cannot play voicemail in Jabber.

Xiaomi

4C

5.1

MAX

5.1

Mi 4

5.0

Mi 5

6.0

Mi 5s

7.0

Mi 6

7.0

Mi 8

8.0

Pocophone

8.0

Mi Note

5.0

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

Zebra

TC51

6.0

TC70

5.0

TC70 devices might sometimes have issues connecting to Wi-Fi network configured over DHCP.

In TC70, the default value of Keep wifi on during sleep is Off, you must set it to Always On to use Jabber.

TC75X

6.0

Jabber Supports Samsung Knox Version 2.6

Cisco Jabber for Android supports Samsung Knox Version 2.6 on these devices:

Samsung Galaxy Device Model

Operating System

Note 10.1 (2014 Edition)

Android OS 5.0 or later

Note 4

Android OS 5.0 or later

Note 5

Android OS 5.1.1 or later

Note Edge

Android OS 5.0 or later

S5

Android OS 5.0 or later

S6

Android OS 5.1.1 or later

S6 Edge

Android OS 5.1.1 or later

S6 Edge Plus

Android OS 5.1.1 or later

S7

Android OS 6.0.1 or later

S7 Edge

Android OS 6.0.1 or later

Tab S 8.4 and 10.5

Android OS 5.0 or later

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 cannot 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 a Sony device's android OS is 5.0.2 or later and kernel version is 3.10.49 or later, then the device can support non-secure 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)

Honeywell Dolphin CT50

Android OS 5.0 or later

Supported Bluetooth Devices

Bluetooth Devices

Dependencies

Cisco 562

Cisco 561

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 cannot hear Audio. This limitation is applicable for Smartphones with versions earlier to Android 5.0 OS.

- In Sony Z4 / LG G4 /Devices with OS Android 6.0, when a user makes a Cisco Jabber call and connects the Bluetooth headset, then the users on that call might not hear audio. The workaround for this issue is to switch audio output device to speaker, then switch back to Bluetooth. Or connect Bluetooth headset before making a Cisco Jabber call.

Supported Android Wear

Cisco Jabber is supported on all Android wear devices with Android OS 5.0 or later and Google service 8.3 or later. Cisco Jabber is tested 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

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 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

- Restrictions

Limitations

The following limitations apply to all devices:

- Jabber always displays notifications for invalid certificates on Android 7.0 and later, even for installed custom CA-signed certificates on the Android OS. Apps that target Android 7.0 only trust system-provided certificates and no longer trust user-added Certificate Authorities.

- Jabber for Android can't start video calls from your Chromebook if another app is using the camera.

- Because of a limitation of Cisco Unity Connection, the voicemail server cannot display the URI for a missed call. This issue occurs if you decline an incoming Cisco Jabber call that was placed from a URI, and then that caller is diverted to voicemail. If the caller's contact information 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.

- If you play music with a third-party application in the background, and make or receive a Cisco Jabber for Android video call, the music does not pause or resume after the video call ends. To work around this issue, you can open the third-party application to pause or 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.

- 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.

- Notifications are not supported on Android Wear devices in Jabber team messaging mode.

- 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'll only see 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 are creating devices for users in Cisco Unified Communications Manager 11.0, you can now specify a key order as RSA Only, EC Only, EC Preferred, or RSA Backup. However, the EC Only option is not currently supported by Cisco Jabber, 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 is an interval of 120 seconds between sending connection requests. This is to prevent multiple requests to the server from multiple clients. During this 120-seconds interval, even if your network connection is active, Jabber remains inactive.

- There is 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

- In Samsung devices, when you install Jabber for the first time, Jabber is put in the unmonitored apps list automatically, which means it won't be put to sleep while running in the background. However, if you upgrade your Samsung OS from a version without unmonitored apps list, then 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, you need to 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.

Caveats

Caveats describe unexpected behavior. The following sections describe how to obtain the latest information.

- Bug Severity Levels

- Search for Bugs

- Open Caveats in Release 12.6(1)

- Resolved Caveats in Release 12.6(1)

- Open Caveats in Release 12.6

- Resolved Caveats in Release 12.6

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.

Open Caveats in Release 12.6(1)

There are no open caveats for this maintenance release.

Resolved Caveats in Release 12.6(1)

Identifier

Severity

Headline

CSCvp72487

3

Jabber 12.6 continiously consuming around 30MB/hour with Video Call using Logitech Camera

CSCvq04985

4

Jabber login fails from LTE network but works from external WiFi network

CSCvp24501

3

Call from different IP phones to J4A, both sides for 4-5 seconds can't hear nothing.

CSCvq04907

4

Jabber usage of expired access_tokens for UDS requests causes 401 errors in CUCM

Open Caveats in Release 12.6

Identifier

Severity

Headline

CSCvp24501

3

Call from different IP phones to J4A, both sides for 4-5 seconds can't hear nothing.

Resolved Caveats in Release 12.6

Identifier

Severity

Headline

CSCvn52634

3

One way audio issue for Android devices.

CSCvk73830

3

Self view upside down on Sonim device.

CSCvn52979

3

Hunt Pilot display name is not localized on Jabber Android client for an incoming call.

CSCvo28565

3

Custom Tabs on Jabber for Android not replacing =${UserID} when manually configured.

CSCvo50334

3

Jabber for android window minimizes after answering an incoming call.

CSCvn58562

4

Phone registration not successful at the 1st login after jabber reset.

Notices