Guest

Cisco Jabber for Android

Cisco Jabber for Android 10.6.x Release Notes

  • Viewing Options

  • PDF (607.6 KB)
  • EPUB (138.8 KB)
  • MOBI (232.1 KB)
  • Feedback
Release Notes

First Published: January 27, 2015

Last Updated: March 16, 2015


Release Notes

Introduction

These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Android Release 10.6. These release notes are updated for every maintenance release but not for patches or hot fixes. Note that each maintenance release includes the features, requirements, restrictions, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Android, we recommend that you review this document for information about issues that may affect your system.

New and Changed Features in Release 10.6.1

IM and Presence

Support for Instant Messaging in Landscape mode — Cisco Jabber for Android allows you to chat with others in Landscape mode on Android smartphones.

Stability

Stability Improvement — See Resolved Caveats in Release 10.6.1 for more information.

New and Changed Features in Release 10.6

User Management

  • Remote and mobile access deployments with single sign on — Expressway version 8.5 can act as a service provider in a single sign on environment. Jabber can be deployed with single sign on so that users can securely access all Jabber services without being prompted to log into each of them separately whether they are using Jabber in the office on the corporate network, or working remotely.

  • Add contact group — You can now create a contact group in your contact list.

  • Edit profile — You can now edit the avatar and profile information.

IM and Presence

  • File transfer — Jabber for Android supports file transfer via instant messaging. You can send and receive a file in both the 1:1 chat and the group chat. Compliance and policy control are supported and you can set up rules for file transfer such as, limiting the size and the type of the files.

  • Receive screen capture — You can receive a screen capture sent from a Cisco Jabber desktop client and you can preview a screen capture before sending it.

Calling Features

  • Call park — You can park an active call and pick it up on other devices by the parked number. The EnableCallPark parameter controls call park.

  • Video desktop share — Binary Floor Control Protocol (BFCP) provides video desktop sharing capabilities for collaboration sessions across dedicated video endpoints, mobile devices, and personal computers running collaboration software. Jabber for Android officially supports receive BFCP video sharing on TAB devices (normally used for Android Tablets without native calling capability).

    The Jabber for Android 10.6 release enters a beta trial on receiving BFCP video sharing on BOT devices (normally used for Android smartphones and phablets).

    The EnableBFCPVideoDesktopShare parameter controls BFCP video desktop sharing on the client , the default value is true. For more information, see the Deployment and Installation Guide for Cisco Jabber.

  • High definition (HD) video — We now support receiving HD video (1280*720) call on qualifying devices:
    • Google Nexus 5, 7, and 10

    • HTC One Max and M8

    • LG G3

    • Samsung Galaxy Note3 and Note4

    • Samsung Galaxy S5

    • Samsung Galaxy Tab 4, Tab PRO, Tab S and NotePro

    • Sony Xperia Z2 Tablet and Z3


    Note


    Not all models of the Android devices listed above are able to receive HD video.


  • Administrative control to the default value of starting call with video — You configure the StartCallWithVideo parameter to specify how calls start when you place a call. You can configure calls to start with audio only or audio and video.

Telephony

  • Call statistics — You can now view real-time statistics when on a call. You can view audio and video statistics, and copy the statistics into the clipboard or send to others via email. The EnableMediaStatistics parameter controls the ability of viewing the audio and video statistics when on a call.

  • Survivable remote site telephony — You can use survivable remote site telephony (SRST) to retain basic telephony services for your remote Cisco Jabber users. Using this feature, if connectivity is lost, Cisco Jabber fails over to the local router at the remote site.

Deployment

  • Flexible Jabber ID — When setting up Jabber, the Jabber ID can be mapped to the Directory URI field on Cisco Unified Communications Manager. This allows Jabber to identify the user by their AD mail attribute, or their AD msRTCSIP-primaryuseraddress attribute. A user can log into Jabber with their sAMAccountName attribute when the Jabber ID is mapped to the Directory URI field.

  • Multiple presence domains — Jabber can be deployed into an infrastructure where users are organized into more than one domain, or into domains with subdomains.

  • Group configuration files — We now support setting up a specific configuration for a group of users. To do this, you need to specify the name of the group configuration files in the Cisco Support Field on the device configuration in Cisco Unified Communications Manager.

    Group configuration files apply to subsets of users. Global configuration files apply to all users. Group configuration files take priority over global configuration files, see the Deployment and Installation Guide for Cisco Jabber.

Telemetry

  • Controlling Telemetry over a mobile data network — The TelemetryEnabledOverCellularData parameter controls turning on or off the transmission of telemetry data when you are on a mobile data network.

URI Cross Launch

  • URL cross launching improvement — Adds an ability for the application user to decide whether or not to launch back to the original third party application after a Jabber call.

Android Device Support

  • Additional Android smartphones and tablets support — Jabber for Android has more Android smartphones and tablets support in this release. For more information, see the Device Requirements section.

  • Cisco DX device support — Jabber for Android supports Cisco DX650, DX70 and DX80 running on their 10.2.x version. You can only download Cisco Jabber for Android 10.6 from cisco.com and manually install it on DX devices.

UE Improvement

  • Keep a Jabber VoIP call when there is an incoming Global Subscriber Manager call.

  • Mark unread IMs as read.

  • Notification for an invalid certificate when the app is running in the background.

  • Add or Remove Jabber account in Android OS setting.

Changes to Documentation

  • Administrator — This set of guides includes a Planning Guide and a Deployment and Installation Guide. The Planning Guide contains introductory and reference sections that in past releases were in the Deployment and Installation Guide. The intended use of the new Planning Guide is to aid in planning your Cisco Jabber installation. The Deployment and Installation Guide is largely task focused, closely following the installation processes.

  • End user — The Quick Start and User guides have been shortened. The User Guide includes advanced topics, accessibility information, and troubleshooting information. The Quick Start Guide contains basic information to get started with Jabber for Android.

Requirements and Support

Device Requirements

Supported Devices

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

  • Cisco DX650 ( version)

  • Cisco DX70 (10.2.x version)

  • Cisco DX80 (10.2.x version)

  • Google Nexus 5 (Android OS 4.4.x and Android OS 5.0)

  • Google Nexus 7 (Android OS 4.4.x and Android OS 5.0)

  • Google Nexus 10 (Android OS 4.4.x and Android OS 5.1)

  • HTC One M8 (Android OS 4.4.x)

  • HTC One M7 (Android OS 4.4.x)

  • HTC One Max (Android OS 4.4.x)

  • LG G2 (Android OS 4.2.2 to Android OS 5.0.x)

  • LG G3 (Android OS 4.4.x to Android OS 5.0.x)

  • Motorola Moto G (Android OS 4.4.x)

  • Samsung Galaxy Note II (Android OS 4.2 to Android OS 4.4.x)

  • Samsung Galaxy Note III (Android OS 4.3 to Android OS 4.4.x)

  • Samsung Galaxy Note IV (Android OS 4.4.x)

  • Samsung Galaxy Note Pro 12.2-inch (Android OS 4.4.x)

  • Samsung Galaxy Rugby Pro (Android OS 4.2.2 to Android OS 4.4.x)

  • Samsung Galaxy SII (Android OS 4.1.2 to Android OS 4.4.x)

  • Samsung Galaxy SIII (Android OS 4.1.2 to Android OS 4.4.x)

  • Samsung Galaxy S4 (Android OS 4.2.2 to Android OS 4.4.x)

  • Samsung Galaxy S4 mini (Android OS 4.2.2 to Android OS 4.4.x)

  • Samsung Galaxy S5 (Android OS 4.4.x)

  • Samsung Galaxy S5 mini (Android OS 4.4.x)

  • Samsung Galaxy Tab 3 8-inch (Android OS 4.4.x)

  • Samsung Galaxy Tab 4 7-inch, 8-inch, and 10.1-inch (Android OS 4.4.x)

  • Samsung Galaxy Tab PRO 8.4-inch and 10.1-inch (Android OS 4.4.x)

  • Samsung Galaxy Tab S 8.4-inch & 10.5-inch (Android OS 4.4.x)

  • Sony Xperia M2 (Android OS 4.3)

  • Sony Xperia Z1 (Android OS 4.2 to Android OS 4.4.x)

  • Sony Xperia ZR/A (Android OS 4.1.2 to Android OS 4.4.x)

  • Sony Xperia Z2 (Android OS 4.4.x)

  • Sony Xperia Z2 tablet (Android OS 4.4.x)

  • Sony Xperia Z3 (Android OS 4.4.x)


Note


We 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


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


IM and Presence Service

In general, you can run Cisco Jabber for Android on any Android device that meets 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


Note


  • Cisco Jabber for Android does not support the Tegra 2 chipset

  • Due to an Android kernel issue, Cisco Jabber cannot register to the Cisco Unified Communications Manager on some Android devices. If this problem occurs, see the Troubleshooting chapter of the Cisco Jabber for Android User Guide.


Two-Way Video

The minimum requirements for two-way video are:
  • 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

Bluetooth Device Support

  • Plantronics BackBeat 903+

  • Jabra Biz 2400

  • Jabra Easygo

  • Jawbone ICON for Cisco Bluetooth Headset

  • Jabra Motion

  • Jabra PRO 9470

  • Jabra Speak 510

  • Jabra Supreme UC

  • Jabra Wave+

Remote Access

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

  • Samsung AnyConnect — For Samsung devices running Android OS 4.4.x, use Samsung AnyConnect version 4.0.01128 or later.

Software Requirements

Services
Install the COP file cmterm-android-install-141122.cop.sgn for Android phones and the COP file cmterm-jabbertablet-install-141122.cop.sgn for Android tablet, if you support the following services:
  • Secure Phone (Mixed Mode Security) — On Cisco Unified Communications Manager up to Release 9.1(2).

  • Share Line and Graceful Registration under DvO — On Cisco Unified Communications Manager up to Release 10.5(1).

  • Group Configuration (Cisco Supported Field) — On Cisco Unified Communications Manager up to Release 10.5(2).

On-Premises Servers

Cisco Jabber for Android supports the following on-premises nodes and 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 Communications Manager Release 10.5(2)

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)

  • Cisco Unified Communications Manager IM and Presence Service Release 10.5(2)

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 Unity Connection Release 10.5(2)

Cisco WebEx Meetings Server
  • Cisco WebEx Meetings Server Version 2.0

  • Cisco WebEx Meetings Server Version 2.5

  • Cisco WebEx Meetings Server client versions 4.5 to 6.5

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

  • Cisco Expressway Version 8.2.1

  • Cisco Expressway Version 8.5

If you currently deploy a Cisco TelePresence Video Communications 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 (Adaptive Security Appliance) 5500 Series, 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 versions T28 and T29

  • Cisco WebEx Meeting Center DeLorean R2

Directory Servers
  • 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 directory servers — 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 releases:
    • Cisco Unified Communications Manager, Release 9.1(2): Install the COP file cmterm-cucm-uds-912-5.cop.sgn.

    • Cisco Unified Communications Manager, Release 10.0(1): No COP file is required.

    • Cisco UDS Contact Service 10.5(1)

    • Cisco UDS Contact Service 10.5(2)

Accessibility
Screen Readers

Cisco Jabber for Android is compatible with the TalkBack screen reader.

Assistive Touch

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

Supported Codecs

Supported Audio Codecs
  • G.711 mu-law

  • G.711 a-law

  • G.722.1

  • G.729a

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

  • You can turn Low Bandwidth mode on and off in the client settings.

  • 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, you can access your voice messages using G.729 and the Call Voicemail feature.


Network

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, we recommend 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. We recommend that you:
    • Verify channel configurations do not overlap, 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:
    • "VoWLAN Design Recommendations" section in the Enterprise Mobility Design Guide.
    • Cisco Unified Wireless IP Phone 7925G Deployment Guide.
    • Capacity Coverage & Deployment Considerations for IEEE 802.11g white paper.
    • Solutions Reference Network Design (SRND) for your Cisco Unified Communications Manager release.
  • Bluetooth use can cause voice quality and connectivity issues.

  • If you 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

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 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 Cisco Expressway for Mobile and Remote Access, see Cisco Expressway IP Port Usage for Firewall Traversal.

Supported Languages

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

Limitations

  • The following limitations apply to all devices:
    • 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.

    • If you use Cisco Samsung AnyConnect Secure Mobility Client, use a version later than 4.0.01128. Earlier versions may cause connection problems.

  • The following limitations apply to Android OS 4.0 and later:
    • Because of 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.

    • Because of 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 dialog box.

      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 dialog box that allows you to select another voice application. Instead, you can only make calls through the native Android Phone application.

  • Bluetooth limitations:

    • Because of 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.

    • Because of 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.

    • Because of 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.

    • We support 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.

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

  • Phone Services mode users with more than 2,000 local contacts may experience performance issues when loading contacts from the native address book.

Restrictions

The following 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 emergency calls. Calls may be misdirected to the wrong emergency response center or the emergency response center may make errors when determining your location.

  • If you are setting up Dial via Office - Reverse (DvO-R) on Cisco Unified Communications Manager consider the following:
    • The DvO-R feature only applies to Android phones.

    • The DVO-R feature requires Cisco Unified Communications Manager Release 8.6.2 SU4, 9.1.2, or 10.x.

    • DVO enabled devices may encounter issues registering with Cisco Unified Communications Manager. Resetting the device from the Cisco Unified Communications Manager administrative interface will fix this issue.

    • The DvO-R feature is not supported when users connect to the corporate network using Expressway for Mobile and Remote Access.

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

    • Session persistency — The client cannot recover from disruptions caused by network transitions. For example, if you start a Cisco Jabber call inside the office and then walk outside the 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 — When users use the Cisco WebEx Meetings Servers for meetings or the meeting siteType is “ORION”, the client cannot access the Cisco WebEx Meetings Server, and join or start on-premises Cisco WebEx meetings over Mobile and Remote Access (MRA).


      Note


      To use the WebEx meeting option in Cisco Jabber for Android, ensure that the meeting client is installed before installing Cisco Jabber for Android.


    • CAPF enrollment.

    • Early Media — Early Media allows the client to exchange data between endpoints before a connection is established. For example, if you make 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 you hear the busy tone or is sent to voicemail.

      When using Expressway for Mobile and Remote Access, you do not hear a busy tone if the other party declines or does not answer the call. Instead, you hear 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.

  • In most cases, you 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, you must perform initial sign in while on the corporate network:
    • If the voice services domain is different from the services domain. In this case, you 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.

  • Customers using SSO functionality of Cisco WebEx Messenger and deploying Client Certificate-based Authentication to Android devices through a Mobile Device Management (MDM) solution may need to deploy or upgrade to Cisco Jabber for Android 10.6 using the URL configuration option.

  • Edge+SSO feature support is only for Cisco Unified Communications Manager 10.5(2 )and VCS C/E version 8.5.

  • HTTP basic SAML SSO authentication — Login fails when switching users with the Reset Jabber option. Reset Jabber, quit the application fully in 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 on a tel:// link and select Cisco Jabber for Android to place the call.

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

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

    • Cisco DX series devices including DX650, DX70, and DX80. If you want to use the Jabber for Android 10.6 release on these devices, first download the Jabber for Android 10.6 application package (Jabber-10.6-release.apk) from cisco.com.

  • Jabber for Android supports graceful registration over Cisco Edge from Cisco Unified Communications Manager Release 10.5.(2) 10000-1.

  • Access Control System (ACS) 256 and TLS1.2 are only supported over corporate Wi-Fi, these are not supported over Cisco Edge.

  • When transferring a file, the filename can not 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.

  • We do not support first time login on a public network if using a secure phone via an Edge environment.

    If the configuration is for a secure profile with encrypted TFTP, then the first time login must be on-premises to allow CAPF enrolment to occur. This is not supported, and it cannot be supported without Cisco Unified Communications Manager, Edge, and Jabber enhancements.

    However we do support:
    • Encrypted TFTP, with first time login on-premises.

    • Unencrypted TFTP, with first time login via Edge or on-premises.

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.

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:

    • Google Nexus 5 (Android OS 4.4.x and Android OS 5.0)

    • Google Nexus 7 (Android OS 4.4.x and Android OS 5.0)

    • Google Nexus 10 (Android OS 4.4.x and Android OS 5.0)

    • LG G2 (Android OS 4.2.2 to Android OS 5.0.x)

    • LG G3 (Android OS 4.4.x to Android OS 5.0.x)

    • Motorola Moto G (Android OS 4.4.x)

    • Samsung Galaxy Note II (Android OS 4.2 to Android OS 4.4 x)

    • Samsung Galaxy Note III (Android OS 4.3 to Android OS 4.4 x)

    • Samsung Galaxy Note 4 (Android OS 4.4.x)

    • Samsung Galaxy Note Pro 12.2-inch (Android OS 4.4.x)

    • Samsung Galaxy Rugby Pro (Android OS 4.2.2 to Android OS 4.4 x)

    • Samsung Galaxy SII (Android OS 4.1.2 to Android OS 4.4 x)

    • Samsung Galaxy SIII (Android OS 4.1.2 to Android OS 4.4 x)

    • Samsung Galaxy S4 (Android OS 4.2.2 to Android OS 4.4 x)

    • Samsung Galaxy S4 mini (Android OS 4.2.2 to Android OS 4.4 x)

    • Samsung Galaxy S5 (Android OS 4.4.x)

    • Samsung Galaxy S5 mini (Android OS 4.4.x

    • Samsung Galaxy Tab 3 8-inch (Android OS 4.4.x)

    • Samsung Galaxy Tab 4 7-inch, 8-inch and 10.1-inch (Android OS 4.4.x)

    • Samsung Galaxy Tab S 8.4-inch and 10.5-inch (Android OS 4.4.x)

    • Samsung Galaxy Tab PRO 8.4-inch and 10.1-inch (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:

    • HTC One M8 (Android OS 4.4.x)

    • HTC One M7 (Android OS 4.4.x)

    • HTC One Max (Android OS 4.4.x)

    • Sony Xperia M2 (Android OS 4.3)

    • Sony Xperia Z1 (Android OS 4.2 to Android OS 4.4 x)

    • Sony Xperia ZR/A (Android OS 4.1.2 to Android OS 4.4 x)

    • Sony Xperia Z2 (Android OS 4.4.x)

    • Sony Xperia Z2 tablet (Android OS 4.4.x)

    • Sony Xperia Z3 (Android OS 4.4.x)

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.

Search for Bugs

To search for bugs, do the following:

Procedure
    Step 1   Go to https:/​/​tools.cisco.com/​bugsearch/​search.
    Step 2   Sign in with your Cisco.com user ID and password.
    Step 3   Enter the bug ID or specify search parameters.

    What to Do Next

    For more information, select Help on the Bug Search page.

    Open Caveats in Release 10.6.1

    There are no open caveats in this release.

    Closed Caveats in Release 10.6.1

    There are no closed caveats in this release.

    Resolved Caveats in Release 10.6.1

    Identifier

    Severity

    Component

    Headline

    CSCus33080

    Moderate

    Other

    Cisco Jabber for Android takes long time to sign out after sign in and sign out several times.

    CSCus51058

    Enhancement

    Other

    Cisco Jabber self-video appears upside down in Nexus 6.

    CSCus90166

    Severe

    Other

    Contact search does not work after upgrade to 10.6 on CUCM 8.6.

    CSCus70164

    Moderate

    Other

    Incorrect VCS DNS configuration results in Jabber SSO VCS version check failure.

    CSCus73968

    Moderate

    Other

    Cisco Jabber mobile getting registered to wrong server.

    CSCus76093

    Moderate

    Crash

    Cisco Jabber crashes on file transfer manager while no list file.

    CSCus79266

    Moderate

    Other

    Instant Webex meeting started from Jabber does not launch in Mac.

    CSCus72385

    Moderate

    Other

    Cisco Jabber cannot launch meeting client when the URL has “&”.

    CSCus64062

    Moderate

    UI

    Bluetooth audio stream is redirected when Cisco Jabber starts on a Motorola device.

    CSCus74886

    Moderate

    Phoneonly

    Jabber Android 10.6 user guide miss mixed mode security for Sony and HTC phones.

    CSCus86211

    Moderate

    Crash

    Cisco Jabber crashes sometimes when switching from background to foreground.

    CSCus73968

    Moderate

    Other

    Cisco Jabber mobile gets registered to wrong subscriber.

    CSCus05327

    Moderate

    UI

    Bluetooth headset does not work for Android Lollipop on Nexus 5 and Nexus 6.

    Open Caveats in Release 10.6

    Identifier

    Severity

    Component

    Headline

    CSCus07600

    Moderate

    Other

    Self video is muted after switch from background to foreground.

    CSCus33080

    Moderate

    Other

    Jabber for Android at times takes a long time to sign out.

    CSCus35847

    Moderate

    JCF

    IM disconnect and reconnection caused by TP error.

    CSCus64062

    Moderate

    UI

    Bluetooth audio stream redirected when Jabber for Android starts on a Moto device.

    Closed Caveats in Release 10.6

    Identifier

    Severity

    Component

    Headline

    CSCuq49509

    Moderate

    Video

    DQ: [Tab4] Displays video after call established 7-8 seconds with TP.

    CSCus18233

    Severe

    Audio

    Jabber improperly sending audio traffic.

    CSCus81758

    Moderate

    Other

    Call Park: call history shows the call park number, not the actual caller number.

    Resolved Caveats in Release 10.6

    Identifier

    Severity

    Component

    Headline

    CSCuo04100

    Moderate

    Other

    DQ:[HTC ONE M8/Max] no audio heard on Android 4.4.2.

    CSCuq54702

    Moderate

    JCF

    Jabber clients try to authenticate multiple times when using MRA.

    CSCuq89400

    Moderate

    Audio

    Cannot play media/music after the Jabber call forward to voice mail.

    CSCur17173

    Moderate

    SSO

    Jabber quit unexpectedly about null pointer of ring tone URI.

    CSCur19018

    Moderate

    SSO

    WebEx IM phone service login fails due to wrong credential sync to cloud.

    CSCur24831

    Moderate

    Other

    Jabber for Android does not retrieve contact photo from Active Directory.

    CSCur26451

    Moderate

    Other

    Jabber for Android cannot stop ringtone playing while under a shared line.

    CSCur35536

    Moderate

    UI

    Speaker phone activated when SNR call rings to voice mail.

    CSCur36362

    Moderate

    JDF

    JabberWerx not reconnecting with IM and Presence Service Edge login.

    CSCur36409

    Moderate

    Other

    Jabber for Android, importing native contacts hangs at login under phone only mode.

    CSCur63796

    Moderate

    Other

    Jabber ignores the disable the telemetry parameter in the config.xml file.

    CSCur63815

    Moderate

    Other

    Jabber ignores StartCallWithVideo parameter in the config.xml file.

    CSCur67337

    Moderate

    UI

    Anonymous number is not stored in Jabber call history.

    CSCur77817

    Moderate

    UI

    Route pattern information added in call history.

    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 Cisco Jabber clients in one guide. It contains end-to-end client deployment procedures, deployment workflows, infrastructure configuration of services, and client configuration and installation.

    Planning Guide

    This guide provides information about service discovery, encryption, contact sources (EDI and BDI), on-premises or cloud deployments, and requirements for hardware, software, network, and certificates.

    Licensing Information

    This 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 the first time.

    User Guide

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