Guest

Cisco Jabber for Android

Cisco Jabber for Android 9.6(1) Release Notes

  • Viewing Options

  • PDF (1.2 MB)
  • EPUB (132.5 KB)
  • Feedback
Introduction

Introduction

Cisco Jabber for Android Release 9.6(1) 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. The app also includes simplified provisioning and VPN-less access to your collaboration tools when you are outside the office.


Note


Cisco Jabber for Android is a unified communications app. This product is different than Cisco Jabber Voice for Android, which is a voice-only version of the app that offers audio calling and voicemail.

Important Upgrade Notes

At a minimum, you must provision Cisco Jabber for Android users with instant messaging and presence capabilities.

If you already set up a previous version of Cisco Jabber Voice for Android and you do not want to set up a presence server, Cisco recommends that you continue to use Cisco Jabber Voice for Android for voice-only configurations. For information about Cisco Jabber Voice for Android, see the Release Notes.

Cisco Jabber IM for Android users receive an automatic upgrade notification from the Google Play Store to upgrade to Cisco Jabber for Android. Cisco Jabber Voice for Android users who would like to upgrade to Cisco Jabber for Android must upgrade manually.

For information about upgrading previous versions of Cisco Jabber IM for Android to Cisco Jabber for Android, see the following guides:

Documentation

Documentation Resources

The following documents are available for Cisco Jabber for Android.

Installation and Configuration Guide

The Installation and Configuration Guide provides information on deployment planning, client configuration, upgrade requirements, and troubleshooting.

Server Setup Guide

The Server Setup Guide provides task-based information to help configure client services such as directory integration, instant messaging and presence, audio and video calling, voicemail, and conferencing.

DNS SRV Configuration Guide
The Cisco Jabber DNS Configuration Guide provides information on how to set up a domain name server for Cisco Jabber clients. Cisco Jabber uses domain name servers to do the following:
  • Automatically discover on-premises servers inside the corporate network.
  • Determine whether the client is inside or outside the corporate network.
Licensing Information

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

Quick Start Guide

The Quick Start Guide provides instructions to help users sign in to Cisco Jabber for Android for the first time and use a few key features.

User Guide

The User Guide provides task-based information about end user operation of the application.

What's New

Cisco Jabber for Android Release 9.6(1) introduces the following changes:
  • The ability to show personal availability status in the Notification Center when Cisco Jabber runs in the background.
  • User experience improvements, including improved in-product notification to help users transition from legacy clients (Cisco Jabber IM for Android and Cisco Jabber Voice for Android) to Cisco Jabber for Android.
  • Stability improvements. For information about bug fixes, see Release 9.6(1).

Note


Cisco Jabber for Android Release 9.6(1) does not support:
  • ART runtime for Android OS 4.4
  • Downloading the app from Google Play with the following devices:
    • Android tablets
    • Android phones with Intel chipsets
    • Android phones with screen resolution that is lower than 320 x 480

Cisco Jabber for Android Release 9.6(1) uses the same device COP file, administration guides, and user guides as Release 9.6.


Requirements

Device Requirements

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 or later)
  • Samsung Galaxy SIII (Android OS 4.1.2 or later)
  • Samsung Galaxy S4 (Android OS 4.1.2 or later)
  • Samsung Galaxy Note II (Android OS 4.1.2 or later)
  • Google Nexus 5 (Android OS 4.4)
  • Sony Xperia Z1 (Android OS 4.1.2 or later)
  • Sony Xperia ZR/A (Android OS 4.1.2 or later)

The device must be able to access the corporate network in order to use audio and video capabilities.


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
Minimum requirements for two-way video
  • Android OS 4.1.2 or higher
  • 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

Important:
  • 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 or later)
      • Samsung Galaxy SIII (Android OS 4.1.2 or later)
      • Samsung Galaxy S4 (Android OS 4.1.2 or later)
      • Samsung Galaxy Note II (Android OS 4.1.2 or later)
      • Google Nexus 5 (Android OS 4.4)
    • 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.1.2 or later)
      • Sony Xperia ZR/A (Android OS 4.1.2 or later)

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 a successful deployment, you must ensure that your environment meets the Cisco Jabber for Android software requirements.

On-Premises Servers

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 Presence
  • Cisco Unified Presence Release 8.6(1)
  • Cisco Unified Presence Release 8.6(2)
Cisco Unified Communications Manager IM and Presence

Note


Cisco Unified Communications Manager IM and Presence is formerly known as Cisco Unified Presence.


  • Cisco Unified Communications Manager IM and Presence Release 9.1(1)
  • Cisco Unified Communications Manager IM and Presence Release 9.1(2)
  • Cisco Unified Communications Manager IM and Presence Release 10.0(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 WebEx Meetings Server

Cisco WebEx Meetings Server Version 2.0

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

* 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
    For more information about Cisco AnyConnect license requirements, see VPN License and Feature Compatibility.
  • 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
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.

Accessibility

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

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

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

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.
  • 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 or later)
      • Samsung Galaxy SIII (Android OS 4.1.2 or later)
      • Samsung Galaxy S4 (Android OS 4.1.2 or later)
      • Samsung Galaxy Note II (Android OS 4.1.2 or later)
      • Google Nexus 5 (Android OS 4.4)
    • 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.1.2 or later)
      • Sony Xperia ZR/A (Android OS 4.1.2 or later)
  • 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.
  • Cisco Jabber for Android does not support the hold and resume feature when using a shared line to make a call to a video application.
  • URI dialing is not supported if the Dial via Office - Reverse feature is enabled.
  • The Secure Phone feature is not supported if the Dial via Office - Reverse feature is enabled.
  • 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.
    • Sending problem reports.
    • 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 tablets
    • 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.
  • Cisco Jabber for Android does not support ART runtime for Android OS 4.4.

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.

Supported Languages

Cisco Jabber for Android is localized for the following languages:

Language Application User Guides
Chinese (Simplified) Yes Yes
Chinese (Traditional) Yes Yes
Croatian Yes
Danish Yes Yes
Dutch Yes Yes
English Yes Yes
French Yes Yes
German Yes Yes
Hungarian Yes
Italian Yes Yes
Japanese Yes Yes
Korean Yes Yes
Polish Yes Yes
Portuguese Yes Yes
Romanian Yes
Russian Yes Yes
Slovak Yes
Spanish Yes Yes
Swedish Yes Yes
Turkish Yes

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 9.6(1)

    Open Caveats

    The following caveats were open at time of shipping.

    Table 1 Open Caveats in Cisco Jabber for Android 9.6(1)

    Identifier

    Severity

    Component

    Headline

    CSCui41705

    moderate

    instantmessage

    Can't update group chat participant list when app is in background

    CSCul65263

    moderate

    ui

    Can't receive contact's presence change after joined in a webex meeting

    CSCum29271

    moderate

    presence

    App takes 5-30 mins to show "offline" to far-end after network disabled

    CSCun76018

    moderate

    crash

    Auto sign out to input page when tap "Sign in"

    CSCun81163

    moderate

    other

    App lose video from 9971 device after app in background for 5 minutes

    CSCun81215

    moderate

    video

    Call view is black when join in video conference in 3G+Cisco Expressway

    CSCuo64289

    moderate

    other

    [Sony Z1] audio is garbled after upgraded the Android OS 4.4

    CSCuo46661

    minor

    voicemail

    J4A 9.6 no audio on voicemail with S3(android OS 4.3)

    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 9.6(1)

    Identifier

    Severity

    Component

    Headline

    CSCun81237

    moderate

    phoneos

    Existing conference call auto ends if add call via URI dialing

    CSCun82813

    moderate

    ui

    App is auto signed out when attempt to add call

    CSCuo21668

    moderate

    crash

    Jabber RemoteServiceException in ActivityThread$H.handleMessage

    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 9.6(1)

    Identifier

    Severity

    Component

    Headline

    CSCum66824

    severe

    jcf

    Crash when turn wifi off

    CSCun38740

    severe

    jcf

    crash in getaddrinfo of MultiHttpClient when close wifi

    CSCun64058

    moderate

    registration

    Cannot reconnect phone service after Cisco Expressway fail-over

    CSCun70522

    moderate

    ui

    Phone service doesn't show certificate popup after switch 3G to Wifi

    CSCun73051

    moderate

    other

    App cancel multi-selection mode after put app to background

    CSCun73130

    moderate

    other

    No indicator for secured conference call unless switch BG/FG

    CSCun77646

    moderate

    ui

    App becomes not responsive when hold call(only happened once)

    CSCun83424

    moderate

    ui

    Can't connect phone service if switch network during url sign in

    CSCun87546

    moderate

    ui

    Active call message banner erroneously shows user as muted

    CSCuo04165

    moderate

    crash

    jabber crash while change in the network or loss of signal

    CSCuo21603

    moderate

    crash

    Null pointer exception at ServiceDiscoveryManager.printDiscoveryResult

    CSCuo26405

    moderate

    ui

    [CUP+LDAP] jabber android get wrong contact photo after sign in

    CSCuo28142

    moderate

    ui

    Webex Messenger customers utilizing Single Sign On are unable to login

    CSCuo35608

    moderate

    ui

    Enterprise group always expand by default after user login

    CSCuo56238

    moderate

    ui

    App fail to start since start button disappear for some language

    CSCum69687

    minor

    other

    [edge] should not show phone service pwd expired error after signout cup

    CSCum78645

    minor

    ui

    The decline button length is longer than Accept button length

    CSCun03850

    minor

    video

    Self video view auto disappear/appear frequently

    CSCun37891

    minor

    other

    Voicemail shown reconnect and mail list at the same times

    CSCun51676

    minor

    ui

    [UI] reconnect background different in voice message and keypad

    CSCun58082

    minor

    ui

    Keyboard not hidden after send PRT and back to Jabber

    CSCun72399

    minor

    ui

    red bar should not appear when decline call in call UI

    CSCun73072

    minor

    other

    Video switch between on and off several times after resume

    CSCun76033

    minor

    ui

    Timestamp format is not consistent with system setting

    CSCun78277

    minor

    other

    timestamp's date format not equal to system data format

    CSCun81141

    minor

    ui

    remote party video not in center of screen

    CSCun83617

    minor

    other

    should clear search results after deleting all char but keep space

    Release 9.6

    Open Caveats

    The following caveats were open at time of shipping.

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



    Table 4 Open Caveats in Cisco Jabber 9.6 for Android
    Identifier Severity Component Headline
    CSCui41705 moderate instantmessage Can't update group chat participant list when app is in background
    CSCul65263 moderate ui Can't receive contact's presence change after joined in a webex meeting
    CSCum29271 moderate presence App takes 5-30 mins to show "offline" to far-end after network disabled
    CSCun64058 moderate registration Cannot reconnect phone service after Cisco Expressway fail-over
    CSCun70522 moderate ui Phone service doesn't show certificate popup after switch 3G to Wifi
    CSCun73051 moderate other App cancel multi-selection mode after put app to background
    CSCun73130 moderate other No indicator for secured conference call unless switch BG/FG
    CSCun76018 moderate crash Auto sign out to input page when tap "Sign in"
    CSCun77646 moderate ui App becomes not responsive when hold call (only happened once)
    CSCun81163 moderate other App lose video from 9971 device after app in background for 5 minutes
    CSCun81215 moderate video Call view is black when join in video conference in 3G+Cisco Expressway
    CSCun81237 moderate phoneos Existing conference call auto ends if add call via URI dialing
    CSCun82813 moderate ui App is auto signed out when attempt to add call
    CSCun83424 moderate ui Can't connect phone service if switch network during url sign in

    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 5 Closed Caveats in Cisco Jabber 9.6 for Android
    Identifier Severity Component Headline
    CSCud92273 moderate audio International S3 and Note2 don't auto resume music play after call ended
    CSCuf48910 moderate crash Users can't register to phone service in LG Nexus4/Sony devices
    CSCug50074 moderate ui No lock icon for encrypted group chat in chat list
    CSCug59269 moderate ui In-call view show incorrect id when call between two users with same no.
    CSCuh10716 moderate ui New groups generated in app after sync group name changes from other IM
    CSCui34682 moderate callcontrol No 'complete action using' popup in some GS4 devices' keypad
    CSCuj53341 moderate ui Phone service via Cisco Expressway takes 10 min to sync after pwd update
    CSCuj79740 moderate video Call preservation can't work well when disconnecting cucm server network
    CSCul06844 moderate directorysearch Viewing contact profile can see both phone number and directory URI
    CSCul17210 moderate other No participant list for URI conference if URIs have special character
    CSCul39404 moderate ui Can't do one way video call with CTS500 and CTS1300 end points
    CSCul61941 moderate other Can't switch SSO user account without restarting browser
    CSCul67359 moderate video Call video stuck for a second or two when rotate screen
    CSCul73248 moderate video Video conference call can't show all participant's video in ucm 9.x
    CSCul99453 moderate ui App can do encrypted chat with offline buddy
    CSCum09301 moderate registration Sometimes Cisco Expressway cert warning pops up after user signs out
    CSCum11245 moderate ui Cannot get contact profile after switch from one server to another
    CSCum29447 moderate other App's log in URL is not tappable in Gmail
    CSCum29810 moderate presence When log in same im same time, can't change sync status to custom status
    CSCum31759 moderate audio Call dropped if roaming from 3g to corp wifi via Cisco Expressway
    CSCum50228 moderate other User unable to join mtg from webex app if install it after accept mtg
    CSCun09319 moderate other App presence not sync up from other resource after resign in
    CSCun10153 moderate registration Pwd update becomes effective only after reconnect for the second time
    CSCun17886 moderate callcontrol No voice hint for PSTN call failure in Cisco Expressway
    CSCue41433 minor ui No incoming call screen appear if notification bar is expanded
    CSCuh23961 minor ui Can't initiate chat from Chrome or integrated browser of Samsung
    CSCuh32432 minor ui CUP can't show multiple space in custom presence
    CSCuh35213 minor other Can't sign in SSO via integrated browser after repeatedly sign in/out
    CSCui26354 minor ui App doesn't sync user display name change from other resource
    CSCui87433 minor ui App can't show emoticons+character from J4W or J4i correctly
    CSCul06874 minor other Log in fails if certificate warning pending for around 20 min
    CSCul42732 minor voicemail Music only pause for few sec in some media players when playing app's vm
    CSCul57412 minor ui Call id shows Unkown then shows VoiceMail when calling vm number
    CSCul68811 minor ui App shows sign in view after relaunch if killing app in verifying state

     

    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)