This document contains release information for Cisco Jabber for Android, Release 9.1(1).
To obtain the latest Cisco Jabber for Android client software, visit Google Play (formerly known as Google Android Market) and search for Jabber. Your device must run either Android operating system (OS) 2.3, 4.0, or 4.1 to access and use the Cisco Jabber for Android application.
Cisco Jabber 9.1(1) for Android provides Android users with Enterprise calling, visual voicemail, and access to the corporate directory.
Cisco Jabber works in conjunction with Cisco Unified Communications Manager to extend Cisco enterprise communications applications and services to Android devices. To use Cisco Jabber for Android, the Android device must be connected to the corporate network either directly or over VPN.
To enable users to connect to your corporate Wi-Fi network from a remote location, you must set up your system to support VPN. Cisco supports Cisco Jabber for Android with Cisco AnyConnect Secure Mobility Client. Although other VPN clients are not officially supported, you may be able to use Cisco Jabber for Android with other third-party clients.
The voice quality of calls varies significantly, depending on the Wi-Fi or mobile data connection. Cisco Technical Assistance Center (TAC) cannot troubleshoot voice quality when you use Cisco Jabber for Android with a VPN client to remotely connect to your corporate network.
User Features and Benefits
With Cisco Jabber for Android, you can do the following:
- Make calls with your work number using either the Internet or your mobile voice network.
- Receive calls to your work number.
- Use the native Android phone application to place work calls from the Keypad, Logs, Favorites, or Contacts tab.
- Have up to two VoIP calls (call waiting, add new call, swap between active calls).
- Manage Internet calls using many of the standard in-call features such as hold, transfer, and conference.
- Receive calls to your work phone number while Cisco Jabber for Android runs in the background.
- Transfer an active Cisco Jabber for Android VoIP call to your mobile network.
- Transfer an active Cisco Jabber for Android VoIP call from your device to your desk phone.
- Search the corporate directory.
- Authenticate your device to Unified CM using SIP Digest Authentication.
- Access basic or visual voicemail from the home screen or from the status bar if there is a new message.
- See a message indicator for new voice messages that are left at the office phone number.
- Use a VPN connection to securely connect to your corporate network from any remote location.
To enable Cisco Jabber to connect to your corporate Wi-Fi network from a remote location, the administrator must set up the system to support VPN. Cisco supports Cisco Jabber for Android with Cisco AnyConnect Secure Mobility Client. Although other VPN clients are not officially supported, you may be able to use Cisco Jabber for Android with other VPN clients.
Cisco Jabber for Android 9.1(1) contains a number of bug fixes. See Caveats for more information.
Cisco Jabber for Android 9.1(1) introduces the following features:
- Dial via Office - Reverse: The Dial via Office - Reverse (DVO-R) feature allows users to make outgoing Cisco Jabber calls with their work number using the voice plan for the device. When the client uses DVO-R to make outgoing calls, incoming calls use Mobile Connect.Important:
The DVO-R feature requires:Important:If you deploy DVO-R, Cisco recommends that you also set user-controlled Voicemail Avoidance (available in Unified CM 9.0 and later). User-controlled Voicemail Avoidance prevents DVO-R calls from inadvertently connecting the called party with the Cisco Jabber user's mobile phone voicemail service. For more information about user-controlled Voicemail Avoidance, see the section called "Confirmed Answer and DVO VM detection" in the "New Features" chapter of the New and Changed Information for Cisco Unified Communications Manager, Release 9.0(1), which is found in the Release Notes list.
If you upgrade Cisco Jabber for Android from an earlier release to Release 9.1(1) and you plan to enable the DVO-R feature, you must:
- Perform the following bulk updates on your Unified CM:
For information about performing bulk updates, see the Bulk Administration Guide for your release of Unified CM, which is located in the maintenance guide list.
- Check the Enable Mobile Connect check box in each user's Mobility Identity.
- Check the Enable Cisco Unified Mobile Communicator check box on each device.
- Verify that each user has a Mobile Identity. For more information, see the Cisco Jabber for Android Release 9.1(1) Administration Guide.
- If your Unified CM has custom partitions and multiple calling search spaces, select a Rerouting Calling Search Space that includes the partition that applies to the mobile phone number. For more information, see the Cisco Jabber for Android Release 9.1(1) Administration Guide.
If you set user-controlled Voicemail Avoidance, this feature applies to both DVO-R and Mobile Connect calls.
- Ringtone: Added the ability to set Cisco Jabber to use only the Cisco ringtone.
- Ringtone volume: Added the ability to set a minimum ringtone volume.
You must set up the corporate network to ensure that the Android device can connect to it. When in the office, users can connect to the corporate Wi-Fi directly. When away from the office, users must establish a VPN connection to your corporate network using another Wi-Fi or mobile data network. To enable Cisco Jabber for Android to connect from a remote location:
For optimal user experience over your corporate Wi-Fi network, we recommend that you:
- Design your Wi-Fi networks to minimize occurrences of layer 3 roaming when the IP address changes, resulting in long latency or roaming times, dropped calls, or degraded voice quality.
- Ensure all access points have the same Service Set Identifier (SSID). Roaming can be slow if the SSIDs do not match.
- Ensure that access points broadcast their SSID. Otherwise, the application offers a poor user experience because it can disconnect from the Wi-Fi network when roaming to the next access point.
- Eliminate gaps in Wi-Fi coverage as much as possible, including in areas such as elevators, stairways, and outside corridors.
Conduct a thorough site survey to minimize network problems that could affect voice quality. When you conduct the survey, verify nonoverlapping channel configurations, access point coverage, and required data and traffic rates; eliminate rogue access points; and identify and mitigate the impact of potential interference sources.
For more information, see:
- “VoWLAN Design Recommendations” section in the Enterprise Mobility 4.1 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 Unified CM release.
Voice quality is highly dependent on connection quality and cannot be guaranteed.
Cisco Unified Communications Manager Requirements
Cisco Unified Communications Manager:Important:
The DVO-R feature requires:
Cisco Business Edition:
Supported Codecs for Calls
On Unified CM:
- Users can turn Low Bandwidth mode on and off in the client settings if they experience voice quality issues. Enabling Low Bandwidth mode in the client settings may resolve certain voice quality issues.
- Normal mode supports G.711u and G.729a or G.729b.
- Low Bandwidth mode supports G.729a or G.729b only.
Voicemail Requirements (Optional)
Requirements for Integration with Corporate Directory (Optional)
Use one of the following for Lightweight Directory Access Protocol (LDAP):
Requirements for Integration with Cisco AnyConnect Secure Mobility Client (Optional)
- Android devices must run Cisco AnyConnect Secure Mobility Client Version 3.0.09093, 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:
For more information about Cisco AnyConnect license requirements, see VPN License and Feature Compatibility.
- 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
Requirements for Users and Devices
Cisco supports Cisco Jabber for Android on the following Android devices:
Model Model Number Android OS Version Baseband Carrier Samsung Galaxy S III SCH-I535 4.1.1 I535VRBLI5 Verizon GT-I9300 4.1.1 I9300XXDLID International SGH-I747 4.1.1 I747UCLJ1 AT&T Samsung Galaxy Nexus Samsung Galaxy Nexus 4.1.1 I515,10 V.FF02/I515.FG02 Verizon Samsung Galaxy S II SC-02C 2.3.3 SC02COMKF2 NTT DoCoMo SGH-T989 2.3.6 T989UVLDE T-Mobile SGH-I777 2.3.6 I777UCKK6 AT&T
Although not officially supported, Cisco Jabber for Android runs on many Android OS 2.3, 4.0, and 4.1 devices with various limitations depending on the device. For information about running Cisco Jabber for Android on unsupported devices, see the Cisco Support Forums.
The Cisco Jabber for Android application is available through Google Play (formerly known as Google Android Market). Your device must run either Android OS 2.3, 4.0, or 4.1 to access the Cisco Jabber for Android application.
The device must be able to access the corporate network. In the office, you can connect to the corporate Wi-Fi network directly. Away from the office, you must establish a VPN connection to your corporate network using another Wi-Fi or mobile data network. You must set up this VPN connection before you use Cisco Jabber for Android.
For desk phone integration support, see the preceding Unified CM requirements.
Installation and setup instructions are available for system administrators and users in the following guides:
- System Administrators: See the Cisco Jabber for Android Administration Guide for your release in the installation guides list.
- Users: See the Cisco Jabber for Android Frequently Asked Questions (FAQs) for your release in the user guides list.
Obtain the software for this product from Google Play (formerly known as Google Android Market). Your device must run either Android OS 2.3, 4.0, or 4.1 to access the Cisco Jabber for Android application.
Limitations and Restrictions
The following limitations and restrictions apply to all devices:
- Your device must run either Android OS 2.3, 4.0, or 4.1 to access the Cisco Jabber for Android application on Google Play (formerly known as Google Android Market).
- To upgrade from Cisco Jabber for Android Release 8.x to Release 9.x, you must first uninstall any previous versions of the client from your device.
- If your mobile voice service provider does not support simultaneous voice and data connections on your device, you may experience the following issues if users are already on a Cisco Jabber for Android call and they receive a new incoming mobile voice call to the device:
- Cisco Jabber for Android sometimes cannot reregister to the Unified CM if the administrator resets the device from the Unified CM administration pages. You will receive a prompt directing you to restart the application. After the restart, Cisco Jabber for Android works normally.
- Due to operating system limitations, users may not be able to press Accept to answer a call when they receive an incoming work call to the native Android Phone application. To resolve this problem, ask users to lock the screen and then unlock it.
- When you move a call from Cisco Jabber for Android to the mobile network and then end the call, the person on the far-end hears music for a few seconds before the call disconnects.
- Voice quality over public Wi-Fi network connections cannot be guaranteed.
- Voice quality over mobile data networks varies depending on the quality of your mobile data network connection and cannot be guaranteed. Examples of voice quality issues you may experience when using a mobile data network include the following:
- If you are driving and listening to a voicemail message, you may have problems hearing the entire message and the audio may sound choppy or synthetic.
- If you are driving and replying to a voicemail message, the recipient may have problems hearing the entire message and your message may sound choppy or synthetic.
- If you try to access your voicemail and you enter your PIN, the time delay associated with remote access may cause prompts to play out of sync, or you may hear a message that you did not enter the PIN on time.
- When you use a mobile data network to remotely connect to your corporate network, network delays can cause issues for incoming calls, including the following:
- Due to a limitation on certain mobile carriers, while Cisco Jabber for Android is connected to a VPN, you may not be able to resume a Cisco Jabber for Android call after you accept an incoming mobile voice call and then end it quickly.
- If you have multiple Internet calling applications running on your Android device, they can conflict with each other and cause unpredictable behavior.
- If your corporate Wi-Fi network uses layer 2 roaming, and a user is on a call and roaming between access points, the person on the other end may not be able to hear your audio for a few seconds.
- Due to a limitation of the Android OS, there is no visual indicator to let you know about incoming VoIP calls if your device is idle and locked with a PIN or security pattern. However, the phone still rings or vibrates to indicate that you have an incoming VoIP call.
- When using Cisco Jabber for Android to participate in Cisco WebEx conferences, you may experience audio issues. For example, you cannot hear participants, participants cannot hear you, you hear choppy or synthetic audio, or participants hear your audio as choppy or synthetic. To resolve these issues, tap Hold and then tap Resume.
- If you open the Deleted Voice Messages screen in Cisco Jabber for Android and you decline an incoming call, you do not see the next incoming call. To resolve this issue, tap Search tab or place a Cisco Jabber for Android call.
- When you are remotely connected to your corporate network over a 3G mobile data network, directory search performance cannot be guaranteed. Cisco Jabber for Android may be slow to provide directory search results, or the application may not be able to return any results. For best results, you must connect to a better quality Wi-Fi or mobile data network.
- Cisco Jabber for Android does not support the Reporting Structure feature with Open LDAP.
- If you receive a call from someone who is not already in your contact list, the Android operating system uses a default format to display the call log entry. After the operating system applies the default format to the Cisco Jabber for Android phone numbers, some phone numbers do not display correctly in the call logs. For example, the call log displays a call received from John Doe at 8-555-1234 as an Unknown caller at 855-512-34. To resolve this issue, you can add new contacts to your contact list with the correct formatting. The call log recognizes phone numbers in your contact list and displays them using the formatting that you apply to the contact list entry.
- If you answer an incoming call over a remote connection to your corporate network, the SIP Signaling sometimes cannot reach the Unified CM because of network delays. As a result, the Unified CM sends the call to voicemail. For best results, connect to a better quality Wi-Fi or mobile data network.
- VPN clients do not maintain active Internet calls if you transition between your mobile data network and your corporate Wi-Fi network. Instead, you must either end your Internet call or transfer it to your mobile voice network before you transition between networks.
- VPN clients re-register frequently when you transition between networks.
- Due to VPN limitations, Cisco Jabber for Android can take over 2 minutes to register to the Cisco Unified Communications server after the user transitions from the corporate Wi-Fi network to the VPN.
- Cisco supports only the official headset for an Android device. When using a non-official model of headset with an Android device, users may experience the following issues:
- The DVO-R feature requires:
- Unsupported releases of Unified CM do not prevent administrators from enabling DVO-R on the device page for the user. If you enable DVO-R on an unsupported release of Unified CM, the user sees the DVO-R calling options and can attempt to make a DVO-R call, but the calls cannot connect.
- After an administrator sets the DVO-R feature from enabled to disabled on the device page for a user, the user sees the wrong text or no text under the Corporate Wi-Fi Network field on the Settings screen. To resolve this issue, ask the user to navigate away from the Settings menu and then navigate back to the Settings menu.
- Due to a limitation of the Cisco Unified Communications Manager, calls sometimes end without notification if you set up the system with DVO-R and User-Controlled Voicemail Avoidance. This problem occurs if:
- Due to a limitation on the Cisco Unified Communications Manager, you cannot enable the SIP Digest Authentication feature and the DVO-R feature at the same time.
- Due to a limitation with Cisco Unified Communications Manager, if the user places a DVO-R call to an invalid phone number over a SIP trunk, the user hears several seconds of silence instead of an audio message stating the number was invalid.
- Text that is sent from the Cisco Unified Communications Manager to Cisco Jabber is displayed exactly as it appears in the system and cannot be localized. Examples of this type of text include the park number and the voicemail name.
- If the administrator updates an existing destination number in the Mobility Identity for a Cisco Dual Mode for Android device on the Unified CM, the new number is not pushed to the client. To work around this issue, ask the user to do one of the following:
For more information about the Android Settings or the Cisco Jabber for Android Settings, see the FAQs.
- In the Cisco Jabber for Android Settings, manually update the phone number in the DVO Callback Number field.
- In the Cisco Jabber for Android Settings, delete the current number in the DVO Callback Number field, and then exit and restart Cisco Jabber for Android.
- Use the Android Settings to clear the application data, and then reprovision Cisco Jabber for Android.
- Cisco Jabber for Android does not support Multicast Music on Hold. The administrator must ensure that the Media Resource Group List that is applied to the Cisco Jabber for Android device in Unified CM does not contain multicast-enabled Media Resource Groups.
- For potential unexpected behavior and issues that users may encounter, see the FAQs.
The following limitations and restrictions apply to the Samsung Galaxy S II SGH-I777 (AT&T):
- When using a Samsung Galaxy S II SGH-I777 (AT&T) with Android OS 2.3.6 while Cisco Jabber for Android runs in the background, the app turns on silent mode on native Android phone settings. This limitation occurs if the administrator sets the device to use the Cisco ringtone and the native ringtone volume, and the user receives and incoming call to the mobile phone number. To resolve this issue, users can do the following:
The following limitations and restrictions apply to Android OS 2.3:
- Due to device limitations, when using Samsung Galaxy S II SC-02C with Android OS 2.3.3, the device does not display the "Organization" title after you add a new contact and enter information for the contact's organization.
The following limitations and restrictions apply to Android OS 4.0:
DTMF Digits in Log Files
When users enter DTMF digits in Cisco Jabber, the client writes those digits to a log file in plain text.Important:
Problem reports, or PRTs, that users submit contain the log files with DTMF digits. Cisco treats all log files with the strictest confidentiality and deletes all log files when no longer required to investigate product issues.
This issue is resolved in version 9.1(3) with defect number CSCug41885.
Known problems (bugs) are graded according to severity level. 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
You can search for problems by using the Cisco Software Bug Toolkit.
Before You Begin
To access Bug Toolkit, you need the following items:
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. Step 2 Log 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 Bug ID field, then click Go.
What to Do Next
For information about how to search for bugs, create saved searches, and create bug groups, click Help on the Bug Toolkit page.
The following caveats were open at the time of release.
See also the caveats for Cisco Unified Communications Manager for open issues that may affect Cisco Jabber for Android.
Table 1 Open Caveats in Cisco Jabber 9.1(1) for Android
Identifier Severity Component Headline CSCub79203 moderate audio VM audio through speaker if decline incoming call when playing VM CSCuc02212 moderate performance Android Jabber not indicating "call on hold" CSCud41937 moderate ui Tapping on Accept did not answer call - frozen CSCud50918 moderate performance Memory leak over time Nexus CSCud82839 moderate protocol (MOBILITY-867) app answer SNR call, shared line devices show missed call CSCud88547 moderate ui After a call failed, screen frozen CSCud89970 moderate callcontrol Admin updates the MI number, the client does not get the update CSCud89971 moderate performance GS3 Jellybean memory leak CSCue13574 moderate other No indication of callforward in J4A when receive callfrwd CSCue21988 moderate callcontrol Not able to place or receive calls CSCue26153 moderate other DVO - user control - press digit 0 doesn't connect the dvo call CSCue26170 moderate protocol when making DVO call, app doesn't look up caller id from server CSCue26187 moderate protocol no announcement when DVOR to an invalid number over SIP trunk CSCub44319 minor other No notification for an expired voicemail password
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 9.1(1) for Android
Identifier Severity Component Headline CSCuc25175 severe registration Unable to provision if SIP Digest Auth is enabled and DVO enabled CSCud78108 severe registration GS2 ICS unable to register to CUCM CSCuc97013 moderate documentation DVO should not be exposed when connecting to below CUCM 8.6.1 CSCud13552 moderate dvo Jabber unable to register after switch disable to enable dvo CSCue03139 moderate dvo Far end hears fastbusy tone after 55sec into a DVO call CSCue06331 moderate dvo After a DVO R call, Jabber took up to 3 minutes to re-register CSCue26178 moderate other proximity sensor not work when voip call is keeping at background
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 9.1(1) for Android
Identifier Severity Component Headline CSCub44000 moderate callcontrol Jabber not showing incoming call after idivert to VM for prior call CSCub44191 moderate callcontrol Not able to place a call after leaving corp wifi and coming back in CSCub46573 moderate callcontrol Audio sent via headphones instead of speaker after hold/resume CSCub51085 moderate registration Jabber icon shows RED but internet calling status shows Connected CSCub54168 moderate crash ANR - jabber stopped responding or jabber won't launch CSCub54408 moderate audio Jabber dropped call in the middle of a conversation. CSCub54798 moderate callcontrol Call drop while attending a webex meeting CSCub65149 moderate registration TFTP retries stop trying to download the config file after network switch CSCuc04799 moderate audio Error notification takes 2 minutes during provisioning
Troubleshooting information is available for system administrators and users in the following guides:
For the latest versions of all documentation for all releases of Cisco Jabber for Android, go to the documentation home page.
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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses 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)
Copyright © 2013, Cisco Systems, Inc. All rights reserved.