64-Bit Android Support

Cisco Jabber for Android now comes 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. If you install or update Jabber from Google Play Store, you will automatically get the version that is best suited for your device.

Start Cellular Calls with Video

Administrators can control the default value of whether Jabber calls over cellular networks start with video with the new StartCallsWithVideoOverCellular parameter. When set to false (the default), calls over a cellular network start without video. When set to true, the calls start with video. For details, see the Parameters Reference Guide for Cisco Jabber.

Users may change this setting in Settings > Call options > Call capability over cellular network.

Application Rating Behavior

If they install the Jabber wrapped apk file, users won't get notifications asking them to rate the application after they make calls in Jabber.

Single Number Reach Settings

It's now easier for you to set up Single Number Reach, which allows calls that are made to different devices to all reach you at a single number. You can find the Single Number Reach option directly in Settings.

Chromebook Notification Support

Jabber for Android 12.7 with Webex Messenger or Cisco Unified Communications Manager IM and Presence Service now supports incoming chat notifications on Chromebook. The IM notification window appears in the bottom-right corner of the Chromebook screen and offers several default reply buttons that you can tap. You can also tap Reply to open a chat window with the sender.

Modern Input Box Style

We improved how you send messages on your mobile devices. The options to add files, videos, or photos have moved to the bottom of the screen, beside the emoticons.

Updated Navigation

We moved the navigation options to the bottom of the screen.

Save PRT Logs Locally

If your organization does not allow users to send emails from their mobile phone, you need another method to capture PRT logs. You can allow users to save the logs locally with EnableSaveLogsToLocal. The parameter defaults to allowing users to save PRT logs in local storage.

Configure Clients Through Cisco Webex Control Hub

You can run Jabber Team Messaging Mode in IM-Only Mode which doesn't need Cisco Unified Communications Manager and its calling capabilities. To replace Unified CM as the deployment site for the Jabber configuration file, you can upload your Jabber configuration file to the Control Hub. You can upload one configuration file for each organization.

Go to Services, then select the Message card, and choose Settings. Then, select Upload Configuration File. The file must be in .xml format.

If you have Jabber configuration files in both the Control Hub and Unified CM, the value of a parameter from the Unified CM takes precedence.

People Insights

People Insights provides Jabber Team Message Mode users with professional profiles of their contacts. Anywhere a contact card appears, user can access People Insights: contact lists, in conversations, from the call history, and voicemail history.

The feature only displays publicly available information in profiles, and internal company directory information to users in the same company. This internal directory information is not visible to users outside the company. Users can edit their own profiles to add more data. For more information, see What Is People Insights.

To enable People Insights, go to the Control Hub, and select Settings > Directory Synchronization and People Insights and turn on the Show People Insights toggle.

Do Not Disturb Setting

We changed the intervals in the Do Not Disturb setting to 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, and 24 hours.

Messaging Service Status

You can check your connection to the messaging service from the Settings > Messaging menu. A Service Impacted label appears when some messaging services in the Webex platform are not working.

Enterprise Content Management (ECM) Support

You can view, send, and receive ECM files. Upload ECM files from OneDrive or SharePoint Online, and send them via chat to other Jabber users who are authorized to view them. When users send attachments, they can choose to upload files from their computer or ECM account. Users can choose to send the files to other people in their organization, or to specific people who have access to the file. When the recipient gets the message with the ECM attachment, they'll need to be logged in to that ECM service before they can view or open the file.

For more information, see https://help.webex.com/en-us/nfia8at/Configure-Enterprise-Content-Management-Settings-in-Cisco-Webex-Control-Hub and https://help.webex.com/en-us/nuvy9lb/Enterprise-Content-Management-in-Cisco-Webex-Control-Hub.

Quote Message

You can add context to a message by quoting another message in the same space. To quote a message, touch and hold the message that you want to quote and choose Quote message from the list that appears. After you send the message, the quoted message appears above your message in the space.

BOT Support

BOTs now appear in your search results, and you can add them to spaces and to an existing conversation, and create a new conversion with a BOT . To find a BOT, go to the search bar and type the first few letters of its name. BOTs appear in their own category underneath results from your contacts and directory.

Jabber Team Messaging Mode users can search for and use BOTs that are deployed as part of the Webex Platform Service. You can find these BOTs on the Cisco Webex App Hub or develop your own for your users. BOTs from the Cisco Jabber BOT SDK work only for on-premises and Webex Messenger deployments.

Space Details

In users' spaces in team messaging mode, we replaced the information icon with a drop-down arrow. It expands to show options for the space, such as adding participants, adding the space to your favorites, muting notifications, and other details about the space.

Updates to Collaboration Meeting Room Controls

Users on Jabber mobile clients can now use several meeting room controls that were previously only available to desktop users.

Hosts can make another participant the host. The new host is moved to the top of the participant list. They can also mute/unmute everyone; and pause and resume the meeting recording.

A host can choose to either end a meeting or leave it after selecting another participant to host.

Auto-Login to Meetings

If SSO is enabled using the same IDP on Cisco Unified Communications Manager and Webex meeting, Jabber automatically connects.

Call Pickup

Users can now use Call Pickup on their mobile devices. Call Pickup allows users to pick up others' incoming calls in various answer groups. You configure answer groups on the server side. You configure this feature in Jabber using the following existing parameters: EnableCallPickup (default: false), EnableOtherGroupPickup (default: false), and EnableGroupCallPickup (default: false). For more information about how call pickup works, see the Feature Configuration for Cisco Jabber guide.

Updated Sign-Out Behavior

If users sign out of Jabber, they must now re-authenticate when they next sign in.

Users do not have to re-authenticate in these cases:

• A configuration change requires them to sign out.

• They kill the Jabber app and restart it. (For desktop users, this includes when you choose Exit Jabber.)

• Mobile Jabber users with touch, fingerprint, or face ID enabled.

OAuth Handling of Refresh Tokens

If you have OAuth enabled in your deployment, Jabber now checks, by default, for expired refresh tokens when users sign in. If a refresh token has expired, the user must re-authenticate. If the refresh token expires while a user is signed in, Jabber signs them out with a message that their session expired.

The LegacyOAuthLogout parameter controls this behavior. The default value of false checks for expired refresh tokens. If you set the value to true, Jabber never checks for expired refresh tokens. For details, see the Parameters Reference Guide for Cisco Jabber.

Samsung Knox Support

Samsung Knox consists of a highly secure platform that is built into Samsung devices and provides a set of solutions that leverage this platform. For more information about Knox, see www.samsungknox.com

Support for Customized Certificate Authority

Starting with Release 12.7, you can use a customized certificate authority (CA) on Android devices.

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

Minimum requirements for Android devices:

Cisco Jabber for Android supports Full UC mode in the devices with these OS versions:

Jabber Support for Samsung Knox

Cisco Jabber for Android supports Samsung Knox as follows:

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:

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

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.

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