Guest

Cisco Jabber for Android

Cisco Jabber for Android 10.5 Release Notes

  • Viewing Options

  • PDF (1.3 MB)
  • Feedback
Release Notes

Release Notes

Cisco Jabber for Android is a unified communications app that lets you communicate with your work contacts from anywhere. Cisco Jabber for Android offers instant messaging, presence, audio and video calling, voicemail, and conferencing.

Important Upgrade Notes

Cisco Jabber Voice for Android users who would like to upgrade to Cisco Jabber for Android must upgrade manually. You will receive a notification when you start Cisco Jabber for Android to uninstall Cisco Jabber Voice for Android if it is installed.

Customers using the Single Sign On (SSO) functionality of Cisco WebEx Messenger and deploying Client Certificate-based Authentication to Android devices through a Mobile Device Managerment (MDM) solution may need to deploy or upgrade to Cisco Jabber for Android 10.5 using the URL configuration option using the following procedure:

    1. Users upgrading to Cisco Jabber for Android 10.5 should first clear application data through the Android OS application manager after upgrading the application.
    2. Users deploying Cisco Jabber for Android for the first time with Release 10.5 should install the application but not launch it immediately.
  1. Create a configuration URL with the parameter ForceLaunchBrowser=true. For example: ciscojabber://provision?ForceLaunchBrowser=true.

    Note


    See the sections Create Configuration URL and Provide Users with Configuration URL in the Deployment and Installation Guide for more information on how to construct a configuration URL and use it to configure the client.


  2. Distribute the configuration URL to your users and instruct them to use it to initially launch the client.

New and Changed Features

Device and Android OS

Expanded Device Support

The number of supported devices has been expanded. See Device Requirements for Cisco Jabber for Android for a list of supported devices.

Tablet UI Adoption

Certain Android tablets are now supported. See Device Requirements for Cisco Jabber for Android for a list of supported devices.

Android Runtime (ART) Support

Cisco Jabber for Android is now able to run under the Android Runtime in Android OS 4.4.

Design

Visual Design

Cisco Jabber for Android offers a new and modern design to align with the visual identity of Cisco's Collaboration portfolio and to improve user experience.

Interaction Design

New design changes improve ease of use, such as audio output device switching, application notifications, and tab management.

Improved User Experience during Jabber Startup

Welcome page and sign-in page are optimized.

User Management

Single Sign On

Single Sign On allows Cisco Jabber users to securely access all services without being prompted to log into each of them separately. Cisco Jabber utilizes authentication performed by a corporate Identity Provider. The Identity Provider controls the authentication experience for Cisco Jabber users. For example, the Identity Provider controls the experience by prompting the user for their Enterprise username and password once when Cisco Jabber is first run and by specifying the length of time a user is authorized to use Cisco Jabber services.

Cisco Jabber uses the Security Assertion Markup Language (SAML), an XML-based open standard data format that enables access to a defined set of Cisco services seamlessly after verifying credentials with an Identity Provider. SAML Single Sign On can be enabled for Cisco WebEx Messenger Services, Cisco Unified Communications Manager, and Cisco Unity Connection. Single Sign On is deployed for use with Cisco Jabber clients using Service Discovery.

Cisco Jabber for Android supports the HTTP form, HTTP basic, and NT LAN Manager (NTLM) authentication methods.

For more information about SAML SSO, see the chapter on Single Sign-On (SSO) Deployments in the Deployment and Installation Guide.


Note


Cisco Expressway 8.2 and lower does not support Single Sign On. Users will require Cisco AnyConnect for access to on premise Cisco Jabber services from outside the corporate firewall when deploying Single Sign On in such an environment.


Telemetrics

The client is enabled in this release to help improve your Cisco Jabber experience by sending anonymous telemetry data to Cisco on elements such as product performance, feature usage and call quality. Administrator and Client options are provided to enable or disable this capability.

Calling Features

Receive Hunt Groups
Cisco Jabber for Android supports receiving a call from a Hunt Group on your Android phone and tablet. The Hunt Group number is displayed in the incoming call toast of the call.
Self-view

Users can move and hide the self-view window on video calls.

Hold and Resume on a Shared Line

The application can switch active calls between shared lines using the Hold and Resume features on your Android phone and tablet.

Phone-only Mode

The client can now be used in phone-only mode without the Instant Messaging and Presence service on your Android phone and tablet. Cisco Jabber for Android turns your Android phone and tablet into a full-featured Cisco Unified IP Phone with video capability in this mode.

Contact

Active Directory Lightweight Directory Service (AD LDS) Integration

Support for AD LDS as a contact source has been added in this release. See the section on AD LDS Integration in the Deployment and Installation Guide for more information.

MinimumCharacterQuery Field Support

Support for MinimumCharacterQuery field has been added in this release. This sets the minimum number of characters that must be in a contact name before an LDAP query is performed. See the section on Directory Integration parameters in the Deployment and Installation Guide for more information.

Reset Cisco Jabber

The Reset Jabber option is used to return Cisco Jabber to an initial installation state. All information associated with the current user and configuration is deleted. This includes, but is not limited to, the following:

  • Cached system configuration
  • User specific configuration
  • Chat history
  • Phone configuration
  • Voicemails
  • Contacts
  • Meetings information

Information cannot be recovered or reinstated once the option has been selected.

Changes to Cisco Jabber for Android Documentation

Cisco Jabber for Android 10.5 introduces a new document, the Cisco Jabber Deployment and Installation Guide. This new guide contains deployment, configuration, and installation information for all Cisco Jabber clients; Cisco Jabber for Windows, Cisco Jabber for Mac, Cisco Jabber for iPhone and iPad, and Cisco Jabber for Android. This new document consolidates information that was previously published in the Installation and Configuration Guide, Server Setup Guide, and DNS Configuration Guide.

Related Information

Documentation Resources

The following documents are available for Cisco Jabber for Android.

Release Notes

Provide administrators with a summary of information about the release, which include feature enhancements, requirements, limitations and restrictions of the software, and caveats overview.

Deployment and Installation Guide
Provides administrators with information for all Jabber clients in one guide. It contains end-to-end client deployment procedures, comprising requirements, deployment scenarios and workflows, infrastructure configuration of services, and client configuration and installation.
Licensing Information

This Licensing Information document provides information on the open source libraries used by the application.

Quick Start Guide

Instructions to help navigate end users around Cisco Jabber for Windows for the first time and use a few key features.

User Guide

Provides an overview of task-based information about end user operation of the client.

Requirements

Device Requirements for Cisco Jabber for Android

Device Support

Cisco Jabber for Android is available from the Google Play Store.

Cisco specifically supports Cisco Jabber for Android on audio and video for the following Android device and operating system combinations:

  • Samsung Galaxy SII (Android OS 4.1.2 to Android OS 4.4 latest)
  • Samsung Galaxy SIII (Android OS 4.1.2 to Android OS 4.4 latest)
  • Samsung Galaxy S4 (Android OS 4.2.2 to Android OS 4.4 latest)
  • Samsung Galaxy S4 mini (Android OS 4.2.2 to Android OS 4.4 latest)
  • Samsung Galaxy S5 (Android OS 4.4.x)
  • Samsung Galaxy Note II (Android OS 4.2 to Android OS 4.4 latest)
  • Samsung Galaxy Note III (Android OS 4.3 to Android OS 4.4 latest)
  • Samsung Galaxy Rugby Pro (Android OS 4.2.2 to Android OS 4.4 latest)
  • Samsung Galaxy Note Pro 12.2 (Android OS 4.4.x)
  • Google Nexus 5 (Android OS 4.4.x)
  • Google Nexus 10 (Android OS 4.4.x)
  • Sony Xperia Z1 (Android OS 4.2 to Android OS 4.4 latest)
  • Sony Xperia ZR/A (Android OS 4.1.2 to Android OS 4.4 latest)
  • Sony Xperia Z2 (Android OS 4.4.x)
  • Sony Xperia M2 (Android OS 4.3)
  • LG G2 (Android OS 4.2.2 to Android OS 4.4 latest)
  • Motorola Moto G (Android OS 4.4.x)

Note


Cisco will support Cisco Jabber for Android using IM only mode on all Android devices which meet the following minimum specifications:

  • Android OS 4.1.2 or higher to Android OS 4.4.x
  • 1.5 GHz dual-core or higher (quad-core recommended)
  • Display 320 x 480 or higher
  • Cisco Jabber for Android does not support the Tegra 2 chipset


Note


Cisco supports Cisco Jabber for Android with tested Android devices. Although other devices are not officially supported, you may be able to use Cisco Jabber for Android with other devices.

In general, you should be able to run Cisco Jabber for Android on any Android device that meets the following minimum specifications.
Minimum requirements for IM and Presence
  • Android OS 4.1.2 or higher to Android OS 4.4.x
  • 1.5 GHz dual-core or higher (quad-core recommended)
  • Display 320 x 480 or higher
  • Cisco Jabber for Android does not support the Tegra 2 chipset
Minimum requirements for two-way video
  • Android OS 4.1.2 or higher to Android OS 4.4.x
  • 1.5 GHz dual-core or higher (quad-core recommended)
  • Display 480 x 800 or higher
  • Cisco Jabber for Android does not support the Tegra 2 chipset


Note


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 the latest version. This solution applies to the following supported devices:
    • Samsung Galaxy SII (Android OS 4.1.2 to Android OS 4.4 latest)
    • Samsung Galaxy SIII (Android OS 4.1.2 to Android OS 4.4 latest)
    • Samsung Galaxy S4 (Android OS 4.2.2 to Android OS 4.4 latest)
    • Samsung Galaxy S4 mini (Android OS 4.2.2 to Android OS 4.4 latest)
    • Samsung Galaxy S5 (Android OS 4.4.x)
    • Samsung Galaxy Note II (Android OS 4.2 to Android OS 4.4 latest)
    • Samsung Galaxy Note III (Android OS 4.3 to Android OS 4.4 latest)
    • Samsung Galaxy Rugby Pro (Android OS 4.2.2 to Android OS 4.4 latest)
    • Samsung Galaxy Note Pro 12.2 (Android OS 4.4.x)
    • Google Nexus 5 (Android OS 4.4.x)
    • Google Nexus 10 (Android OS 4.4.x)
    • LG G2 (Android OS 4.2.2 to Android OS 4.4 latest)
    • Motorola Moto G (Android OS 4.4.x)
  • 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:
    • Sony Xperia Z1 (Android OS 4.2 to Android OS 4.4 latest)
    • Sony Xperia ZR/A (Android OS 4.1.2 to Android OS 4.4 latest)
    • Sony Xperia Z2 (Android OS 4.4.x)
    • Sony Xperia M2 (Android OS 4.3)

Bluetooth Device Support

Cisco specifically tested and supports the following Bluetooth devices with Cisco Jabber for Android:
  • Jabra Motion
  • Jawbone ICON for Cisco Bluetooth Headset
  • Plantronics BackBeat 903+
  • Jabra Wave+
  • Jabra Easygo

Note


Cisco supports Cisco Jabber for Android with tested Bluetooth devices. Although other Bluetooth devices are not officially supported, you may be able to use Cisco Jabber for Android with other devices.


Important:

Using a Bluetooth device on a Samsung Galaxy SIII may cause distorted ringtone and distorted call audio.

If you use a Samsung Galaxy S4 with either Jawbone ICON for Cisco Bluetooth Headset or Plantronics BackBeat 903+, you may experience problems due to compatibility issues between these devices.

Remote Access


Note


Administrators can configure remote access using either a VPN or Expressway for Mobile and Remote Access. If administrators configure Expressway for Mobile and Remote Access, there is no need to configure VPN access.
Cisco AnyConnect Secure Mobility Client
To connect with VPN, users can use the latest version of Cisco AnyConnect Secure Mobility Client, which is available from the Google Play Store.

Software Requirements for Cisco Jabber for Android

For a successful deployment, you must ensure that your environment meets the Cisco Jabber for Android software requirements.

On-Premises Servers for Cisco Jabber for Android

Cisco Jabber for Android supports the following on-premises servers:

Cisco Unified Communications Manager
  • Cisco Unified Communications Manager Release 8.6(1)
  • Cisco Unified Communications Manager Release 8.6(2)
  • Cisco Unified Communications Manager Release 9.1(1)
  • Cisco Unified Communications Manager Release 9.1(2)
  • Cisco Unified Communications Manager Release 10.0(1)
  • Cisco Unified Communications Manager Release 10.5(1)
Cisco Unified Presence
  • Cisco Unified Presence Release 8.6(1)
  • Cisco Unified Presence Release 8.6(2)
Cisco Unified Communications Manager IM and Presence Service

Note


Cisco Unified Communications Manager IM and Presence Service is formerly known as Cisco Unified Presence.
  • Cisco Unified Communications Manager IM and Presence Service Release 9.1(1)
  • Cisco Unified Communications Manager IM and Presence Service Release 9.1(2)
  • Cisco Unified Communications Manager IM and Presence Service Release 10.0(1)
  • Cisco Unified Communications Manager IM and Presence Service Release 10.5(1)
Video Conferencing Bridge
  • Cisco TelePresence MCU 5310
  • Cisco TelePresence Server 7010
  • Cisco TelePresence Server MSE 8710
  • Cisco Integrated Services Router (with PVDM3)

    Note


    Expressway for Mobile and Remote Access is not supported with Cisco Integrated Services Router (with PVDM3).


Cisco Unity Connection
  • Cisco Unity Connection Release 8.5
  • Cisco Unity Connection Release 8.6(1)
  • Cisco Unity Connection Release 8.6(2)
  • Cisco Unity Connection Release 9.1(1)
  • Cisco Unity Connection Release 9.1(2)
  • Cisco Unity Connection Release 10.0(1)
  • Cisco Unity Connection Release 10.5(1)
Cisco WebEx Meetings Server
  • Cisco WebEx Meetings Server Version 2.0
  • Cisco WebEx Meetings Server Version 2.5
  • Cisco WebEx Meetings client Version 4.5 or later
Cisco Expressway Series for Cisco Unified Communications Manager (Optional)

Use the following servers to set up mobile and remote access for the client. Note that the Expressway servers do not provide call control for Cisco Jabber. The client uses Cisco Unified Communications Manager for call control.

  • Cisco Expressway-E Version 8.1.1
  • Cisco Expressway-C Version 8.1.1
  • Cisco Expressway 8.2
  • Cisco Expressway 8.2.1

* If you currently deploy a Cisco TelePresence Video Communication Server (VCS) environment, you can set up Expressway for Mobile and Remote Access. A VCS environment requires Cisco VCS Expressway Version 8.1.1 and Cisco VCS Control Version 8.1.1.

Cisco Adaptive Security Appliance (Optional)
Cisco AnyConnect Secure Mobility Client Integration (Optional)
  • Android devices must run the latest version of Cisco AnyConnect Secure Mobility Client, which is available from the Google Play Store
  • Cisco ASA 5500 Series Adaptive Security Appliance (ASA) Version 8.4(1) or later
  • Cisco Adaptive Security Device Manager (ASDM) Version 6.4 or later
  • ASA license requirements: Use one of the following combinations:
    • AnyConnect Essentials and AnyConnect Mobile licenses
    • AnyConnect Premium and AnyConnect Mobile licenses
  • Certificate Authority (CA) if using certificate-based authentication: Cisco IOS Certificate Server, Microsoft Windows Server 2008 Enterprise Certificate Authority, or Microsoft Windows Server 2003 Enterprise Certificate Authority

Cloud-Based Servers

Cisco Jabber for Android supports the following cloud-based servers:
  • Cisco WebEx Messenger Release 7.5 or later
  • Cisco WebEx Meeting Center as follows:
    • Version T28
    • Version T29

Directory Servers

You can use the following directory servers with Cisco Jabber for Android.
LDAP
Use one of the following sources for Lightweight Directory Access Protocol (LDAP):
  • Microsoft Active Directory 2008
  • Microsoft Active Directory 2003
  • OpenLDAP 2.4
  • Active Directory Lightweight Directory Service (AD LDS)
Cloud-based

Cisco WebEx Connect Contact Service 7.5 or later

Cisco Unified Communications Manager
User Data Service (UDS) is supported with the following Cisco Unified Communications Manager versions:
  • Cisco Unified Communications Manager 9.1(2) or later with the following COP file: cmterm-cucm-uds-912-5.cop.
  • Cisco Unified Communications Manager 10.0(1). No COP file is required.
  • Cisco UDS Contact Service 10.5(1)

Accessibility for Cisco Jabber for Android

Screen Readers

Cisco Jabber for Android is compatible with the TalkBack screen reader. Users who require screen readers should always use the most recent version to ensure the best possible user experience.

Assistive Touch

You can navigate Cisco Jabber for Android using Explore by Touch.

Supported Codecs for Cisco Jabber for Android

Supported Audio Codecs

  • G.711 mu-law
  • G.711 a-law
  • G.722.1
  • G.729a

Minimum requirement for low-bandwidth availability: G.729a.

Users can turn Low Bandwidth mode on and off in the client settings if they experience voice quality issues.

Normal mode supports G.711, G.722.1, and G.729a.

Low Bandwidth mode supports G.729a only.

Supported Video Codecs

H.264/AVC

Supported Voicemail Codecs

  • PCM linear
  • G.711 mu-law (default)
  • G.711 a-law
  • GSM 6.10

Note


Cisco Jabber does not support visual voicemail with G.729. However, users can access their voice messages using G.729 and the Call Voicemail feature.


Network Requirements

If you deploy Phone Services, the mobile device must be able to connect to the corporate network.

For optimal user experience when using Cisco Jabber over your corporate Wi-Fi network, Cisco recommends that you:

  • Design your Wi-Fi network to eliminate gaps in coverage as much as possible, including in areas such as elevators, stairways, and outside corridors.
  • Ensure that all access points assign the same IP address to the mobile device. Calls are dropped if the IP address changes during the call.
  • Ensure that all access points have the same SSID. Hand-off may be much slower if the SSIDs do not match.
  • Ensure that all access points broadcast their SSID. If the access points do not broadcast their SSID, the mobile device may prompt the user to join another Wi-Fi network, which interrupts the call.
Conduct a thorough site survey to minimize network problems that could affect voice quality. Cisco recommends that you:
  • Verify nonoverlapping channel configurations, access point coverage, and required data and traffic rates.
  • Eliminate rogue access points.
  • Identify and mitigate the impact of potential interference sources.

For more information, see:

  • The "VoWLAN Design Recommendations" section in the Enterprise Mobility Design Guide.
  • The Cisco Unified Wireless IP Phone 7925G Deployment Guide.
  • The Capacity Coverage & Deployment Considerations for IEEE 802.11g white paper.
  • The Solutions Reference Network Design (SRND) for your Cisco Unified Communications Manager release.

If users connect to the network remotely, the mobile device must be able to connect to the corporate network using a solid, high-bandwidth connection. Video and audio quality is dependent on connection quality and cannot be guaranteed.

Ports and Protocols for Cisco Jabber for Android

The client uses the ports and protocols listed in the following table. If you plan to deploy a firewall between the client and a server, you must configure the firewall to allow these ports and protocols.


Note


There are no TCP/IP services enabled in the client.


Port

Application Layer Protocol

Transport Layer Protocol

Description

Inbound
16384 to 32766 RTP UDP Receives Real-Time Transport Protocol (RTP) media streams for audio and video. You set these ports in Cisco Unified Communications Manager.
Outbound
69 TFTP UDP Connects to the Trivial File Transfer Protocol (TFTP) server.
6970 HTTP TCP Connects to the TFTP server to download client configuration files.
80 HTTP TCP Connects to services such as Cisco WebEx Meeting Center for meetings or Cisco Unity Connection for voicemail.
389 LDAP TCP (UDP) Connects to an LDAP directory service.
3268 LDAP TCP Connects to a Global Catalog server for contact searches.
443 HTTPS TCP Connects to services such as such as Cisco WebEx Meeting Center for meetings or Cisco Unity Connection for voicemail.
636 LDAPS TCP Connects securely to an LDAP directory service.
3269 LDAPS TCP Connects securely to the Global Catalog server.
5060 SIP TCP Provides Session Initiation Protocol (SIP) call signaling.
5061 SIP over TLS TCP Provides secure SIP call signaling.
5222 XMPP TCP Connects to Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence Service for instant messaging and presence.
5269 XMPP TCP XMPP federation.
8191 SOAP TCP Connects to the local port to provide Simple Object Access Protocol (SOAP) web services.
8443 HTTPS TCP
8443 is the port for web access to Cisco Unified Communications Manager and includes connections for the following:
  • Cisco Unified Communications Manager IP Phone (CCMCIP) server for assigned devices.
  • User Data Service (UDS) for contact resolution.
16384 to 32766 RTP UDP Sends RTP media streams for audio and video.
53 DNS UDP Provides hostname resolution.
3804 CAPF TCP Issues Locally Significant Certificates (LSC) to IP phones. This is the listening port for Cisco Unified Communications Manager Certificate Authority Proxy Function (CAPF) enrollment.

For information about port usage for Expressway for Mobile and Remote Access, see Cisco Expressway IP Port Usage for Firewall Traversal.

Supported Languages for Cisco Jabber for Android

Cisco Jabber for Android is localized for the following languages:

  • Arabic
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Croatian
  • Danish
  • Dutch
  • English
  • French
  • German
  • Hungarian
  • Italian
  • Japanese
  • Korean
  • Polish
  • Portuguese (Brazil)
  • Romanian
  • Russian
  • Slovak
  • Spanish
  • Swedish
  • Turkish

Limitations and Restrictions

The following limitations and restrictions apply to all devices:
  • USE OF THE JABBER SOFTPHONE DURING AN EMERGENCY IS AT YOUR OWN RISK. The softphone technology may not provide sufficient voice quality or location data for 911 emergency calls. Calls may be misdirected to the wrong emergency response center or the emergency response center may make errors when determining your location.
  • Customers using the Single Sign On (SSO) functionality of Cisco WebEx Messenger and deploying Client Certificate-based Authentication to Android devices through a Mobile Device Managerment (MDM) solution may need to deploy or upgrade to Cisco Jabber for Android 10.5 using the URL configuration option using the following procedure:
      1. Users upgrading to Cisco Jabber for Android 10.5 should first clear application data through the Android OS application manager after upgrading the application.
      2. Users deploying Cisco Jabber for Android for the first time with Release 10.5 should install the application but not launch it immediately.
    1. Create a configuration URL with the parameter ForceLaunchBrowser=true. For example: ciscojabber://provision?ForceLaunchBrowser=true.

      Note


      See the sections Create Configuration URL and Provide Users with Configuration URL in the Deployment and Installation Guide for more information on how to construct a configuration URL and use it to configure the client.


    2. Distribute the configuration URL to your users and instruct them to use it to initially launch the client.
  • 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 the latest version. This solution applies to the following supported devices:
      • Samsung Galaxy SII (Android OS 4.1.2 to Android OS 4.4 latest)
      • Samsung Galaxy SIII (Android OS 4.1.2 to Android OS 4.4 latest)
      • Samsung Galaxy S4 (Android OS 4.2.2 to Android OS 4.4 latest)
      • Samsung Galaxy S4 mini (Android OS 4.2.2 to Android OS 4.4 latest)
      • Samsung Galaxy S5 (Android OS 4.4.x)
      • Samsung Galaxy Note II (Android OS 4.2 to Android OS 4.4 latest)
      • Samsung Galaxy Note III (Android OS 4.3 to Android OS 4.4 latest)
      • Samsung Galaxy Rugby Pro (Android OS 4.2.2 to Android OS 4.4 latest)
      • Samsung Galaxy Note Pro 12.2 (Android OS 4.4.x)
      • Google Nexus 5 (Android OS 4.4.x)
      • Google Nexus 10 (Android OS 4.4.x)
      • LG G2 (Android OS 4.2.2 to Android OS 4.4 latest)
      • Motorola Moto G (Android OS 4.4.x)
    • 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 list. This solution applies to the following supported devices:
      • Sony Xperia Z1 (Android OS 4.2 to Android OS 4.4 latest)
      • Sony Xperia ZR/A (Android OS 4.1.2 to Android OS 4.4 latest)
      • Sony Xperia Z2 (Android OS 4.4.x)
      • Sony Xperia M2 (Android OS 4.3)
  • Due to the large number of third-party applications that support the tel:// URI feature, Cisco cannot guarantee interoperability of this feature on all third-party applications. In some third-party applications, this feature allows you to click on a tel:// link and select Cisco Jabber for Android to place the call.
  • Due to 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.
  • When a Cisco Jabber client calls another Cisco Jabber client, Cisco MediaSense call recording is currently not supported. This impacts Built-in Bridge (BiB) and silent record, as G.722 codec is used by default. This media protocol is not supported by Cisco MediaSense.
  • 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.
  • In most cases, users can sign in to the client for the first time using Expressway for Mobile and Remote Access to connect to services from outside the corporate firewall. In the following cases, however, users must perform initial sign in while on the corporate network:
    • If the voice services domain is different from the services domain. In this case, users must be inside the corporate network to get the correct voice services domain from the jabber-config.xml file.
    • If Cisco Jabber needs to complete the CAPF enrollment process, which is required when using a secure or mixed mode cluster.
  • When using Expressway for Mobile and Remote Access to connect to services from outside the corporate firewall, the client does not support:
    • LDAP for contact resolution. Instead, the client must use UDS for contact resolution.
    • Dial via Office - Reverse calls.
    • Session persistency. The client cannot recover from disruptions caused by network transitions. For example, if a users start a Cisco Jabber call inside their office and then they walk outside their building and lose Wi-Fi connectivity, the call drops as the client switches to use Expressway for Mobile and Remote Access. Likewise, the call drops if the client switches from Expressway for Mobile and Remote Access to the office Wi-Fi network.
    • Cisco WebEx Meetings Server. The client cannot access the Cisco WebEx Meetings Server server, or join or start on-premises Cisco WebEx meetings.
    • CAPF enrollment.
    • Early Media. Early Media allows the client to exchange data between endpoints before a connection is established. For example, if a user makes a call to a party that is not part of the same organization, and the other party declines or does not answer the call, Early Media ensures that the user hears the busy tone or is sent to voicemail. When using Expressway for Mobile and Remote Access, the user does not hear a busy tone if the other party declines or does not answer the call. Instead, the user hears approximately one minute of silence before the call is terminated.
    • End-to-end media encryption. Media is not encrypted on the call path between the Cisco Expressway-C and devices that are registered locally to Cisco Unified Communications Manager. The Device Security Mode must be set to Authenticated. The client does not support media encryption with Expressway for Mobile and Remote Access when you set the Device Security Mode to Encrypted.
  • If you make a Cisco Jabber for Android call using Expressway for Mobile and Remote Access over a 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.
  • Bluetooth limitations:
    • Due to a limitation with certain mobile carriers, if a user resumes an active Cisco Jabber VoIP call that was interrupted by an incoming mobile voice call to the device, and then the user tries to power on and use a Bluetooth audio device, the Bluetooth device cannot receive audio.
    • Switching between Bluetooth and other audio devices such as the device speaker, earphones, or a headset is supported only on Android OS 4.2.2 and above.
    • Due to a limitation of the Android OS, Cisco Jabber for Android does not support answering or ending calls with the Talk button on a Bluetooth headset. To work around this issue, answer and end your Cisco Jabber for Android calls using the Cisco Jabber user interface.
    • Due to a limitation of the Android OS, incoming call ringtone cannot be played to both the device speaker and a Bluetooth audio device.
    • If you use a Samsung Galaxy S4 with either Jawbone ICON for Cisco Bluetooth Headset or Plantronics BackBeat 903+, you may experience problems due to compatibility issues between these devices.
    • Using a Bluetooth device on a Samsung Galaxy SIII may cause distorted ringtone and distorted call audio.
  • Cisco Jabber for Android does not support downloading the app from Google Play with the following devices:
    • Android phones with Intel chipsets
    • Android phones with screen resolution that is lower than 320 x 480
  • The following limitations and restrictions apply to Android OS 4.0 and later:
    • Due to a limitation of Android OS 4.0 and later, Cisco Jabber cannot register to Cisco Unified Communications Manager on some devices. Cisco is working with select device manufacturers to resolve this issue at the Android OS level.
    • Due to a limitation with Android OS 4.1.2 and later on some devices, you may experience issues if you perform the following steps:
      1. Make a call from the native Android phone application.
      2. Select Jabber (or another voice application) from the popup window.
      3. Select Always to indicate that you always want to use Cisco Jabber (or another voice application) to make calls.
      After you complete these steps, the native Android phone application no longer shows you the popup window that allows you to select another voice application. Instead, you can only make calls through the native Android Phone application. There is no workaround for this issue.
  • Phone Services mode users with more than 2,000 local contacts may experience performance issues when loading contacts from the native address book .
  • Application users may have the following issues using HTTP basic SAML SSO authentication:
    • Login will fail when switching users with the Reset Jabber functionality. Reset Jabber, Force Quit the application fully in Android OS, and try again.
    • Login may fail after entering incorrect credentials even when entering the correct credentials.
    • Login will fail if you select the Sign In button without entering credentials.

Android Version Support Policy for Cisco Jabber for Android

Cisco supports the current Google Play version of Cisco Jabber for Android. Previous Google Play versions of Cisco Jabber become obsolete as new versions become available. Defects found in any Cisco Jabber release are evaluated against current versions.

Performance and Behavior Notes

Multiple Resource Login

When a user signs in to multiple instances of the client at the same time, the chat feature behaves as follows:
  • The first incoming chat message is sent to all the clients.
  • The first client to reply to the incoming chat message gets all the subsequent messages. The other clients do not get these subsequent incoming messages.
  • If the client does not use the chat feature for 5 minutes, the next incoming message is sent to all the clients again.

Caveats

Bug Severity Levels

Known problems (bugs) are graded according to severity level. The following table describes bug severity levels:

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.
These release notes contain descriptions of the following:
  • All severity level 1 or 2 bugs
  • Significant severity level 3 bugs
  • All customer-found bugs except severity level 6 enhancement requests

Search for Bugs

You can search for problems by using the Cisco Bug Search Tool.

Before You Begin
To access Bug Search Tool, you need the following items:
  • Internet connection
  • Web browser
  • Cisco.com user ID and password
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.

    What to Do Next

    For information about how to use the Bug Toolkit, select Help on the Bug Toolkit screen.

    Release 10.5

    Open Caveats

    The following caveats were open at time of release.



    Table 1 Open Caveats in Cisco Jabber for Android 10.5

    Identifier

    Severity

    Component

    Headline

    CSCup61095 moderate JCC CUCM failover and fallback cannot work while have a video call
    CSCuq26302 moderate CPVE Jabber will send wrong codec for Telemetry data
    CSCuq26363 moderate VCS Sometimes lose audio when making call via 3G+edge
    CSCuq26427 moderate JCF Can't refetch edge config if unable to register via all known paths
    CSCuq27775 moderate CUCM No ringback tone heard when Jabber calls unity connection and call back
    CSCuq27783 moderate JCC Immediately attempt a re-registration if it receives a 408 for INVITE
    CSCuq32364 moderate accesibility [ACC 50.11] Checkbox status cannot be read in some editing list
    CSCuq33158 moderate JCF [Edge] Android improperly appending domain name to HTTP TFTP Requests
    CSCuq39313 moderate JCF J4A crash frequently on Sony Experia Z1 or Z2 in edge environment

    Closed Caveats

    The following severity 1, 2, or 3 issues cannot be fixed at this time.

    See also the caveats for Cisco Unified Communications Manager for closed issues that may affect Cisco Jabber for Android.



    Table 2 Closed Caveats in Cisco Jabber for Android 10.5

    Identifier

    Severity

    Component

    Headline

    CSCum73427 moderate callcontrol incoming call view disappears if launch url call
    CSCuo75024 moderate other no call waiting tone for 2nd incoming call
    CSCuo91821 moderate callcontrol Jabber audio drops when Android phone roaming between WiFI SSIDs
    CSCup46879 moderate sso SSO-Persistent cookie mode does not work on Jabber
    CSCup73700 moderate other UCM Authentication required if delay to accept cert for webex sso on
    CSCup84538 moderate ui [DQ] NO LED notification for missed call
    CSCuq01280 moderate sso failed to login when input incorrect credential in SSO mode with Basic

    Resolved Caveats

    The following severity 1, 2, and 3 caveats were present in at least one previous release and are resolved in this release. Resolved minor caveats are not listed here.

    Table 3 Resolved Caveats in Cisco Jabber for Android 10.5

    Identifier

    Severity

    Component

    Headline

    CSCuo26405 moderate ui [CUP+LDAP] jabber android get wrong contact photo after sign in
    CSCuo33952 moderate other TFTP configuration is not download before Edge connection is established
    CSCuo35608 moderate ui Enterprise group always expand by default after user login
    CSCuo75072 moderate other Can't view contact's profile although permission is on
    CSCuo82476 moderate other J4A call failure on new Android OS 4.4 under HomeWiFi + VPN
    CSCup31358 moderate ui Jabber for android no work for find contact and photo for Tamir language

     

    THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

    THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

    The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

    NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

    IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

    Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

    Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:/​/​www.cisco.com/​go/​trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)