This document contains release information for Cisco Jabber for Android, Release 9.0(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 or 4.0 to access and use the Cisco Jabber for Android application.
Cisco Jabber 9.0(1) for Android provides Android users with Enterprise voice over IP (VoIP) 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:
- Place and receive VoIP calls from your corporate phone number through Unified CM using your mobile device.
- 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).
- Use many of the standard in-call features that Unified CM provides, including 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.0(1) contains a number of bug fixes. See Caveats for more information.
Cisco Jabber for Android 9.0(1) introduces the following features:
- Visual voicemail: The visual voicemail feature is an alternative to the basic voicemail service. With visual voicemail, you can see a list of your messages without having to dial in to your voice mailbox. From this list, users can play or pause messages, see a transcription of messages (if available), delete messages, call back the contact who sent the message, and add contacts.
- SIP Digest Authentication: SIP Digest Authentication is a Unified CM security feature that authenticates user identity.
- Low-bandwidth mode: Users can choose low bandwidth mode (G.729a or G.729b) to optimize the audio for low bandwidth networks, which may improve call quality.
- Unified CM caller ID: Cisco Jabber for Android obtains the caller's name (caller ID) and displays it to the user for outgoing and incoming calls. Cisco Jabber for Android does not override the name if a contact already exists in user’s native Android contact list. The caller's phone number is stored in the native Android call logs.
Due to an Android OS limitation, the name obtained from Unified CM is not stored in the native Android call logs.
Cisco Jabber for Android 9.0(1) features the following changes from the previous release:
- Removed support for the following devices on Android OS 2.21:
- Added support for the following new device and Android OS combinations:
- Added UI improvements, including tabs for Directory Search and Visual Voicemail, a badge count on the Visual Voicemail tab, a new built-in keypad within the client, and a streamlined Settings screen.
- Changed VPN support. Removed support for the secure connect feature in favor of adding support for Cisco AnyConnect Secure Mobility Client.
For existing customers who need the secure connect feature, you can continue to use Cisco Jabber for Android Release 8.6, which is available for download on Cisco.com. Cisco will provide limited support for Cisco Jabber for Android Release 8.6 until March 31, 2013. After March 31, 2013, Cisco Jabber for Android Release 8.6 will not be available for download or support.
- Changed the software design. To upgrade Cisco Jabber for Android Release 9.0(1), users must first uninstall any previous versions of the product from the Android device.
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:
Required Codecs for Calls
Minimum requirement for low-bandwidth calling: G.729a or G.729b.
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 2.5.5125, 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:
- Samsung Galaxy Nexus with Android OS 4.04
- Samsung Galaxy S II (AT&T) with Android OS 2.3
- Samsung Galaxy S II SC-02C (NTT Docomo) with Android OS 2.3
- Samsung Galaxy S i9000 (model number GT-I9000) with Android OS 2.3
- Samsung Galaxy Ace (model number GT-S5830L) with Android OS 2.3
- Samsung Galaxy Tab International (model number GT-P1000) with Android OS 2.3
Although not officially supported, Cisco Jabber for Android runs on many Android OS 2.3 or 4.0 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 or 4.0 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.
Tips for Searching Cisco Documentation
We recommend that you use the external Google Search (http://www.google.com) to find information.
Use the following formula in the search field:
<product name> <release number> <topic keywords> site:cisco.com
Examples of Google Search entries:
Installation and setup instructions are available for system administrators and end 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 or 4.0 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 or 4.0 to access the Cisco Jabber for Android application on Google Play (formerly known as Google Android Market).
- To upgrade Cisco Jabber for Android Release 9.0(1), you must first uninstall any previous versions of the client from your device.
- When using Cisco Jabber for Android to make a VoIP call or to listen to voice messages on a Samsung Galaxy S 4G device, the audio volume on either the earphone or speakerphone may not be loud enough to hear messages or prompts. Use a headset to get the best audio experience.
- 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 device limitations, older or lower-end Android devices such as the Samsung Galaxy S and Samsung Galaxy Ace may take longer than 5 seconds to register to the corporate phone system.
- 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 calls if you transition between your mobile data network and your corporate Wi-Fi network. Instead, you must either end your call or transfer it to your mobile voice network before you transition between networks.
- VPN clients re-register frequently when you transition between networks.
- For potential unexpected behavior and issues that users may encounter, see the FAQs.
The following limitations and restrictions apply to the Samsung Galaxy Ace:
- Cisco AnyConnect Secure Mobility Client is not supported on the Samsung Galaxy Ace device. Although other VPN clients are not officially supported, you may be able to use Cisco Jabber for Android with other VPN clients on a Samsung Galaxy Ace device with Android OS 2.3.
The following limitations and restrictions apply to Android OS 4.0:
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.0(1) for Android
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 CSCub44192 moderate voicemail Voicemail can't connect or reconnect even on corporate network CSCub44193 moderate crash Application "Not responding" message when exiting the app CSCub46573 moderate callcontrol Audio sent via headphones instead of speaker after hold/resume CSCub47473 moderate other Nexus: unable to launch Jabber - JNI error in log 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
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.0(1) for Android
CSCub43522 severe phoneos Nexus Galaxy - the force stop button is not enabled CSCub46183 severe voicemail User is not shown the change password screen CSCub44194 moderate callcontrol Call Failed seen when resuming a voip call after ending cell call CSCub46163 moderate voicemail VM message update for read/unread sometimes up to 5 minutes CSCub46169 moderate voicemail No notification displayed when voicemail account has been locked CSCub46170 moderate voicemail Senders extension replaced with non-associated extension in vm CSCub46175 moderate ui Jabber icon disappears after multiple exit and relaunch CSCub46178 moderate audio Audio delay at least 30 seconds on Galaxy Nexus over SSA mobile CSCub46184 moderate registration Not able to provision with hostname but ok with FQDN CSCub46186 moderate audio When switching btwn APs, if it takes > 3sec &<5 sec, one way audio CSCub46192 moderate audio When switching between APs, if it takes >5 sec, the call will be lost CSCub49385 moderate anyconnect jabber fail to receive call after device screen timeout on 3G + VPN
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.0(1) for Android
CSCtu03939 moderate audio Audio goes through speaker even when headphones are plugged in CSCtu03972 moderate other Cisco Jabber doesn't stop native music player while making VoIP call CSCtw90486 moderate protocol Intermittently no audio bothways on voip calls in WIFI CSCtw95643 moderate audio Oneway voice path on calls to 894X phones & Android Cisco Jabber CSCtx01227 moderate audio Jabber apps failed Baseline VQ testing
Troubleshooting information is available for system administrators and end 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.
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)
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.
Copyright © 2012, Cisco Systems, Inc. All rights reserved.