Table Of Contents
Release Notes for Cisco Jabber for Android, Release 8.6.2
Contents
Introduction
System requirements
User features and benefits
Finding documentation
Tips for searching Cisco documentation
New and Changed Information
Installation notes
Limitations and restrictions
Supported languages
Caveats
Using Bug Toolkit
Release 8.6.2
Open caveats
Resolved caveats
Release 8.6.1
Open caveats
Resolved caveats
Release 8.6
Open caveats
Troubleshooting
Documentation updates
Release Notes for Cisco Jabber for Android, Release 8.6.2
Published: July 13, 2012
This document contains release information for Cisco Jabber for Android, Release 8.6.2.
To obtain the latest Cisco Jabber for Android client software, visit the Google Android Market and search for Jabber. Your device must run either Android operating system (OS) 2.2 or 2.3 to access and use the Cisco Jabber application.
Contents
•
Introduction
•System requirements
•User features and benefits
•Finding documentation
•New and Changed Information
•Installation notes
•Limitations and restrictions
•Supported languages
•Caveats
•Troubleshooting
•Documentation updates
Introduction
Cisco Jabber 8.6.2 for Android provides Android users with Enterprise voice over IP (VoIP) calling and access to the corporate directory while users are connected to the corporate network.
Cisco Jabber client software works in conjunction with Cisco Unified Communications Manager to extend Cisco enterprise communications applications and services to Android devices.
System requirements
Network requirements
The Android device must be able to connect to the corporate network. Users can connect to the corporate Wi-Fi directly when in the office. When away from the office, users can use the secure connect feature to connect to the corporate network from another Wi-Fi or mobile data network.
For optimal user experience when using Cisco Jabber for Android over your corporate Wi-Fi, we recommend that:
•Wi-Fi networks should be designed to minimize occurrences of layer 3 roams where IP addresses change; resulting in long latency or roam times, dropped calls, or dropped voice packets.
•All access points have the same Service Set Identifier (SSID). Roaming can be slow if the SSIDs do not match.
•Access points should broadcast their SSID (otherwise Cisco Jabber may disconnect from the Wi-Fi network when roaming to the next access point and interrupt calls).
•Gaps in coverage should be eliminated 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:
•The "VoWLAN Design Recommendations" section in the Enterprise Mobility 4.1 Design Guide at: http://www.cisco.com/en/US/netsol/ns820/networking_solutions_design_guidances_list.html.
•The Cisco Unified Wireless IP Phone 7925G Deployment Guide at: http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7925g/7_0/english/deployment/guide/7925dply.pdf.
•The Capacity Coverage & Deployment Considerations for IEEE 802.11g white paper at: http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_white_paper09186a00801d61a3.shtml.
•The Solutions Reference Network Design (SRND) for your Cisco Unified Communications Manager release at: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html.
Voice quality depends on connection quality and cannot be guaranteed.
Cisco Unified Communications Manager requirements
Cisco Jabber for Android 8.6.2 is supported on the following Cisco Unified Communications Manager releases:
•7.1.5
•8.0.3
•8.5
•8.6
Voicemail requirements (optional)
Cisco Unity Connection Version 7.1, 8.0, 8.5, and 8.6.1.
Required codecs for calls
•G.711u
•G.729a
•G.729b
Requirements for integration with corporate directory (optional)
Lightweight Directory Access Protocol (LDAP) - Microsoft Active Directory 2003 and 2008, or Open LDAP. Required only to support corporate directory search.
Requirements for integration with secure connect (optional)
Cisco Adaptive Security Appliance (ASA):
•For certificate-based authentication: ASA Version 8.4.1 or later
•For AAA Authentication: ASA Version 8.0 or later
Certificate Authority (CA) if using certificate-based authentication: Cisco IOS Certificate Server or Microsoft Windows Server 2008 Enterprise Certificate Authority
Requirements for users and devices
The following Android devices are supported:
•Samsung Galaxy S International (GT-I9000) with Android 2.2.1 or 2.3
•Samsung Galaxy Tab International (GT-P1000) with Android 2.2.1 or 2.3
•Samsung Galaxy S II (AT&T) with Android 2.3
Although not officially supported, Cisco Jabber for Android runs on many Android OS 2.2 or 2.3 devices with various limitations depending on the device. For information about running Cisco Jabber on unsupported devices, see the Cisco Support Forums at http://supportforums.cisco.com.
The Cisco Jabber for Android application is available through the Google Android Market. Your device must run either Android OS 2.2 or 2.3 to access the Cisco Jabber 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 can use the secure connect feature to connect to your corporate network from another Wi-Fi or mobile data network.
For desk phone integration support, see the Cisco Unified Communications Manager requirements, above.
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 Cisco Unified Communications Manager using your mobile device, while Cisco Jabber is running and connected to the corporate network.
•Securely connect to your corporate network from any remote location, using Wi-Fi or mobile data networks.
•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 Cisco Unified Communications Manager provides, including hold, transfer, and conference.
•Transfer an active Cisco Jabber VoIP call to your mobile network.
•Transfer an active Cisco Jabber VoIP call from your device to your desk phone.
•Search the corporate directory.
•See a message indicator for new voice messages that are left at the office phone number.
•Access voicemail from the home screen; or from the status bar if a new message exists.
•Receive calls to your work phone number while Cisco Jabber for Android runs in the background.
•Cisco Jabber for Android automatically registers to Cisco Unified Communications Manager when available.
Finding documentation
Documentation for administrators:
http://cisco.com/en/US/products/ps11678/prod_installation_guides_list.html
Documentation for users:
http://cisco.com/en/US/products/ps11678/products_user_guide_list.html
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:
•meetingplace 7.0 recording disk space site:cisco.com
•mobility advantage 7.0 compatibility matrix site:cisco.com
•presence 7.0 disaster recovery site:cisco.com
New and Changed Information
Cisco Jabber for Android, Release 8.6.2 introduces the following features:
•Secure connect. This feature allows Cisco Jabber for Android to securely connect to your corporate network from a remote location, using Wi-Fi or mobile data networks.
•Support for Android OS 2.3.
For information about all available features and benefits, see the data sheet for Cisco Jabber for Android at http://www.cisco.com/en/US/products/ps11678/products_data_sheets_list.html.
Installation notes
Installation and setup instructions are available for system administrators and end users in the following guides:
•System Administrators—See the Administration Guide for your release of Cisco Jabber for Android at http://cisco.com/en/US/products/ps11678/prod_installation_guides_list.html.
•Users—See the Frequently Asked Questions document for your release of Cisco Jabber for Android at http://cisco.com/en/US/products/ps11678/products_user_guide_list.html.
Note Obtain the software for this product from the Google Android Market. Your device must run either Android OS 2.2 or 2.3 to access the Cisco Jabber application.
Limitations and restrictions
The following limitations and restrictions apply to all devices:
•Cisco Jabber for Android must be provisioned within the corporate network.
•Your device must run either Android OS 2.2 or 2.3 to access the Cisco Jabber application on the Google Android Market.
•To use Cisco Jabber on the Samsung Galaxy S International device, it is important to upgrade the device OS to Android version 2.2.1 or 2.3. See the manufacturer/carrier site for more information about how to upgrade the OS on your device.
•Cisco Jabber sometimes cannot reregister to the Cisco Unified Communications Manager if the administrator resets the device from the Cisco Unified Communications Manager administration pages. You will receive a prompt directing you to restart the application. After the restart, Cisco Jabber works normally.
•When you move a call from Cisco Jabber to the mobile network and then end the call, the person on the far-end will hear music for a few seconds before the call disconnects.
•Voice quality over public Wi-Fi and mobile data network connections cannot be guaranteed.
•Voice quality over mobile data network 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:
–You may hear only one ring for incoming calls.
–If you have Mobile Connect (formerly known as Single Number Reach or SNR) set up for your device, you may not hear a ring tone, and the system sends the incoming call over your mobile voice network.
•If you have multiple Internet calling applications running on your Android device, they can conflict with each other and cause unpredictable behavior.
•Cisco Jabber displays the calling party name only when the calling number is assigned to a native contact.
•Some public Wi-Fi networks require you to authenticate before you can access the internet. After you connect your device to the public Wi-Fi network, your device displays a web page that prompts you to log on and accept the terms of usage. You must authenticate and access the internet before Cisco Jabber can use the secure connect feature to connect automatically to your corporate network.
•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 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.
•For potential unexpected behavior and issues that users may encounter, see the FAQs at http://cisco.com/en/US/products/ps11678/products_user_guide_list.html.
The following limitations and restrictions apply to Android OS 2.2.1:
•The Cisco Jabber audio volume does not change when you change the volume setting.
•When you use a wired headset, you will hear only incoming audio.
•A long beep is heard after you end an Enterprise VoIP call on the Samsung Galaxy Tab International. The beep is also heard on all calls that follow. This situation occurs intermittently. Exit and then restart the application to return to normal Cisco Jabber behavior.
•When you upgrade the Android OS from 2.2 to 2.2.1 using Samsung Kies after you configure Cisco Jabber, the configuration data might get lost when the device is restarted. We recommend that you provision Cisco Jabber only after you upgrade to 2.2.1. This is a Samsung device-specific issue on the Samsung Galaxy S International device. To resolve the issue, perform a factory reset of the device. A factory reset returns the device to the default factory settings. All customization and applications added to the device are removed.
•Due to a device limitation, when you use a Samsung Galaxy S International with Android OS 2.2.1, you may encounter issues caused by an inability to clear application data. To resolve these issues, you can either upgrade to Android OS 2.3 or perform a factory reset of the device on OS 2.2.1. A factory reset returns the device to the default factory settings. All customization and applications added to the device are removed.
The following limitations and restrictions apply to Android OS 2.3:
•When you upgrade the Android OS from 2.2.1 to 2.3 using Samsung Kies after you configure Cisco Jabber, the configuration data might get lost when the device is restarted. We recommend that you provision Cisco Jabber only after you upgrade to 2.3. This is a Samsung device-specific issue on the Samsung Galaxy S International device. To resolve the issue, perform a factory reset of the device. A factory reset returns the device to the default factory settings. All customization and applications added to the device are removed.
•When you use a Samsung Galaxy Tab International with Android OS 2.3 and a headset, and you receive an incoming call, the incoming audio goes to the speaker on the device. To move the incoming audio to the headset, toggle either the speaker button or the sleep button.
•When you use a Samsung Galaxy Tab International with Android OS 2.3 and a headset, the outgoing audio goes through the device speaker instead of the headset.
•If you are using the Samsung Galaxy Tab International with Android OS 2.3 and you move from your corporate Wi-Fi network to either another Wi-Fi network or a mobile data network, it typically takes over 4 minutes to reconnect to your corporate network using secure connect.
•Due to a limitation on the Samsung Galaxy S International and the Samsung Galaxy Tab International, when you use one of these devices with a headset, outgoing audio is sent through both the headset and the device microphone.
Supported languages
Cisco Jabber for Android, Release 8.6.2 is localized for the following languages:
•Chinese (China)
•Chinese (Taiwan)
•Dutch (Netherlands)
•English
•French
•German
•Italian
•Japanese
•Korean
•Russian
•Spanish
Caveats
•Using Bug Toolkit
•Release 8.6.2
•Release 8.6.1
•Release 8.6
Using Bug Toolkit
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:
•Internet connection
•Web browser
•Cisco.com user ID and password
Procedure
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.
For information about how to search for bugs, create saved searches, and create bug groups, click Help in the Bug Toolkit page.
Release 8.6.2
•Open caveats
•Resolved caveats
Open caveats
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.
Open caveats in Cisco Jabber 8.6.2 for Android
Identifier
|
Severity
|
Component
|
Headline
|
CSCtu17090
|
severe
|
other
|
Lost audio path in mid call
|
CSCtu36534
|
severe
|
audio
|
Audio level falls to a whisper during an active call
|
CSCtu04839
|
moderate
|
other
|
crash if launch CJ from recent used app list
|
CSCtu40187
|
moderate
|
ui
|
In-call screen does not close after end call
|
Resolved caveats
The following sections list caveats that are resolved in Cisco Jabber for Android, Release 8.6.2 but that may have been open in previous releases. Resolved minor caveats are not listed here.
Resolved caveats in Cisco Jabber 8.6.2 for Android
Identifier
|
Severity
|
Component
|
Headline
|
CSCtu03874
|
severe
|
ui
|
CJ is not able to place and receive calls
|
CSCtu28649
|
severe
|
other
|
call dropped because refresh register not sent to UCM
|
CSCto01447
|
moderate
|
other
|
Jabber can't reregister to UCM after a UCM reset
|
CSCtr94129
|
moderate
|
other
|
CUMC for Android cannot properly handle longer FQDNs
|
CSCts47541
|
moderate
|
other
|
Jabber 8.6.1 is not supported on Android OS 2.3
|
CSCts89840
|
moderate
|
other
|
Cisco Jabber needs to use / delimiter for Preset Wi-Fi Networks
|
CSCtu10369
|
moderate
|
other
|
Jabber/Android not accepting "+" sign as part of the DN
|
CSCua76084
|
moderate
|
other
|
Jabber for Android COP file missing Primary Phone field
|
Release 8.6.1
•Open caveats
•Resolved caveats
Open caveats
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.
Open caveats in Cisco Jabber 8.6.1 for Android
Identifier
|
Severity
|
Component
|
Headline
|
CSCto01442
|
severe
|
audio
|
One way audio when using headset
|
CSCto01446
|
severe
|
audio
|
Audio volume does not change even if UI says otherwise
|
CSCto01444
|
moderate
|
audio
|
Audio sounds like it is muffled or "under the water"
|
CSCto01447
|
moderate
|
other
|
Jabber can't reregister to UCM after a UCM reset
|
CSCto01448
|
moderate
|
audio
|
Very long beep is heard when you hang up a call
|
CSCto09546
|
moderate
|
other
|
User gets unprovisioned after a phone restart
|
CSCto14685
|
moderate
|
other
|
Delay in reregistration if Jabber for Android gets disconnected
|
Resolved caveats
The following sections list caveats that are resolved in Cisco Jabber for Android, Release 8.6.1 but that may have been open in previous releases. Resolved minor caveats are not listed here.
Resolved caveats in Cisco Jabber 8.6.1 for Android
Identifier
|
Severity
|
Component
|
Headline
|
CSCto62986
|
severe
|
other
|
StringIndexOutOfBoundsException in com.cisco.telephony.provider
|
CSCto63008
|
severe
|
ui
|
ActivityNotFoundException in com.cisco.telephony.provider
|
CSCto63018
|
severe
|
other
|
NullPointerException in com.cisco.telephony.provider
|
CSCto63022
|
severe
|
other
|
IllegalArgumentException in com.cisco.telephony.provider
|
CSCto15364
|
moderate
|
other
|
Jabber for Android crashes with sigsegv fault - Galaxy Tab
|
CSCtq86674
|
minor
|
ui
|
Jabber for Android call to IP phone drops after 25 seconds of ringback
|
Release 8.6
•Open caveats
Open caveats
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.
Open caveats in Cisco Jabber 8.6 for Android
Identifier
|
Severity
|
Component
|
Headline
|
CSCto01442
|
severe
|
audio
|
One way audio when using headset
|
CSCto01446
|
severe
|
audio
|
Audio volume does not change even if UI says otherwise
|
CSCto01444
|
moderate
|
audio
|
Audio sounds like it is muffled or "under the water"
|
CSCto01447
|
moderate
|
other
|
Jabber can't reregister to UCM after a UCM reset
|
CSCto01448
|
moderate
|
audio
|
Very long beep is heard when you hang up a call
|
CSCto09546
|
moderate
|
other
|
User gets unprovisioned after a phone restart
|
CSCto14685
|
moderate
|
other
|
Delay in reregistration if Jabber for Android gets disconnected
|
CSCto15511
|
moderate
|
other
|
Null pointer error in Jabber logs upon changing DN in CUCM
|
CSCto15364
|
moderate
|
other
|
Jabber for Android crashes with sigsegv fault - Galaxy Tab
|
Troubleshooting
Troubleshooting information is available for system administrators and end users in the following guides:
•System Administrators—See the Administration Guide for your release of Cisco Jabber for Android at http://cisco.com/en/US/products/ps11678/prod_installation_guides_list.html.
•Users—See the Frequently Asked Questions document for your release of Cisco Jabber for Android at http://cisco.com/en/US/products/ps11678/products_user_guide_list.html.
Documentation updates
For the latest versions of all documentation for all releases of Cisco Jabber for Android, go to http://www.cisco.com/en/US/products/ps11678/tsd_products_support_series_home.html.
This document is to be used in conjunction with the documents listed in the "Finding documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2011 Cisco Systems, Inc. All rights reserved.
Feedback
