Cisco Jabber Voice for Android 9.1(5) Release Notes
Release Notes 2
Introduction 2
User Features and Benefits 2
What's New 3
System requirements 3
Finding Documentation 6
Installation Notes 6
Limitations and Restrictions 6
Supported Languages 9
Caveats 10
Troubleshooting 19
Documentation Updates 19
Revised: December 16, 2013,
Release Notes
This document contains release information for Cisco Jabber Voice for Android, Release 9.1(5).
Important
Cisco Jabber Voice offers audio calling and voicemail capabilities.
Cisco Jabber Voice is a separate product from the Cisco Jabber for Android application that offers chat,
presence, audio and video calling, voicemail, and conference escalations.
To obtain the latest Cisco Jabber Voice for Android client software, visit Google Play Store and search for Jabber Voice. To access
and use Cisco Jabber Voice for Android, your device must run one of the following Android operating systems: 4.1, 4.2, or 4.3.
Introduction
Cisco Jabber Voice for Android, Release 9.1(5) 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 Voice 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 Voice for Android with Cisco AnyConnect Secure Mobility Client. Although other VPN clients are not
officially supported, you may be able to use Cisco Jabber Voice for Android with other third-party clients.
Note
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 Voice
for Android with a VPN client and a mobile data network.
User Features and Benefits
With Cisco Jabber Voice 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 Voice for Android runs in the background.
• Transfer an active Cisco Jabber Voice for Android VoIP call to your mobile network.
2
• Transfer an active Cisco Jabber Voice 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.
Note
To enable Cisco Jabber Voice for Android 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 Voice for Android with Cisco AnyConnect Secure Mobility
Client. Although other VPN clients are not officially supported, you may be able to use
Cisco Jabber Voice for Android with other VPN clients.
What's New
Cisco Jabber Voice for Android Release 9.1(5) introduces the following changes:
• Added support for the following Android device and operating system combinations:
◦Samsung Galaxy S4 with Android OS 4.3
◦Motorola MC40 with Android OS 4.1.1
• Stability improvements. For information about bug fixes, see Release 9.1(5), on page 11.
Note
Cisco Jabber Voice for Android Release 9.1(5) uses the same device COP file as Release 9.1(1):
cmterm-android_9.1.1v1.cop.sgn.
Cisco Jabber Voice for Android Release 9.1(5) uses the same Administration Guide and Frequently Asked
Questions as Cisco Jabber Voice for Android Release 9.1(4).
System requirements
Network Requirements
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 Voice for Android to connect from a remote location:
1 You must set up the system to support VPN.
2 Users must set up the VPN client on the Android device.
3
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:
• Unified CM 7.1(5)
• Unified CM 8.0
• Unified CM 8.5(1)
• Unified CM 8.6(2)
• Unified CM 9.1(2)
Cisco Business Edition:
• Cisco Business Edition 5000
• Cisco Business Edition 6000
Supported Codecs for Calls
On Unified CM:
• G.711u
• G.729a or G.729b
Minimum requirement for low-bandwidth calling: G.729a or G.729b.
On client:
• Users can turn Low Bandwidth mode on and off in the client settings if they experience voice quality issues.
4
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)
• For basic voicemail: Cisco Unity Connection Release 7.1, 8.0, 8.5, 8.6.1, and 9.0
• For visual voicemail: Cisco Unity Connection Release 8.5, 8.6.1, and 9.0
Required Codec for Voicemail Recordings
G.711
Requirements for Integration with Corporate Directory (Optional)
Use one of the following for Lightweight Directory Access Protocol (LDAP):
• Microsoft Active Directory 2003
• Microsoft Active Directory 2008
• Open LDAP
Note
Cisco Jabber Voice for Android does not support the Reporting Structure feature with
Open LDAP.
Requirements for Integration with Cisco AnyConnect Secure Mobility Client (Optional)
• Android devices must run Cisco AnyConnect Secure Mobility Client Version 3.0.09156, 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
Requirements for Users and Devices
Support for Cisco Jabber Voice for Android on the following Android devices:
• Samsung Galaxy S4 with Android OS 4.2.2 and 4.3
5
• Samsung Galaxy Note II with Android OS 4.1.2
• Samsung Galaxy Nexus with Android OS 4.2.2
• Samsung Galaxy S III with Android OS 4.1.2
• Samsung Galaxy S II with Android OS 4.1.2
• Motorola MC40 with Android OS 4.1.1
Although not officially supported, Cisco Jabber Voice for Android runs on many Android OS 4.1, 4.2, and 4.3 devices with various
limitations depending on the device. For information about running Cisco Jabber Voice for Android on unsupported devices, see the
Cisco Support Forums.
The Cisco Jabber Voice for Android application is available through Google Play. Your device must run Android OS 4.1, 4.2, and
4.3 to access the Cisco Jabber Voice 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 Voice for Android.
For desk phone integration support, see the preceding Unified CM requirements.
Finding Documentation
• System administrators: Installation Guides list
• Users: End-User Guides list
Installation Notes
Installation and setup instructions are available for system administrators and users in the following guides:
• System administrators: See the Cisco Jabber Voice for Android Administration Guide for Release 9.1(4) in the Installation
Guides list.
• Users: See the Cisco Jabber Voice for Android Frequently Asked Questions (FAQs) for Release 9.1(4) in the End-User Guides
list.
Obtain the software for this product from Google Play Store. Your device must run Android OS 4.1, 4.2, or 4.3 to access the Cisco
Jabber Voice for Android application.
Limitations and Restrictions
The following limitations and restrictions apply to all devices:
• Your device must run Android OS 4.1, 4.2, or 4.3 to access the Cisco Jabber Voice for Android application on Google Play
Store.
• When two or more local contacts have the same phone number and a call is received from one of them, Cisco Jabber Voice for
Android displays the first number found.
• To upgrade from Cisco Jabber for Android Release 8.x to Cisco Jabber Voice for Android Release 9.1(5), you must first uninstall
any previous versions of the client from your device.
6
• 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 Voice for Android call and they receive a new incoming
mobile voice call to the device:
◦Cisco Jabber Voice for Android disconnects from the Cisco Unified Communication Server.
◦You temporarily lose audio.
• Cisco Jabber Voice 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 Voice 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 Voice 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:
◦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.
• Due to a limitation on certain mobile carriers, while Cisco Jabber Voice for Android is connected to a VPN, you may not be
able to resume a Cisco Jabber Voice 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 Voice 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.
7
• If you open the Deleted Voice Messages screen in Cisco Jabber Voice 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 Voice 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 Voice 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 Voice 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 Voice 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 Voice 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:
◦Called party hears poor audio quality
◦Audio path is missing in one direction
◦Audio is intermittently sent to the wrong audio channel
◦Audio for a second call goes to handset instead of wired headset
• 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:
1 the user makes a DVO-R call and presses a number on the dialpad
2 the person the user calls has a busy line and did not set up voicemail on the deskphone
• 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.
8
• 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 Voice for Android 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:
◦In the Cisco Jabber Voice for Android Settings, manually update the phone number in the DVO Callback Number field.
◦In the Cisco Jabber Voice for Android Settings, delete the current number in the DVO Callback Number field, and then
exit and restart Cisco Jabber Voice for Android.
◦Use the Android Settings to clear the application data, and then reprovision Cisco Jabber Voice for Android.
For more information about the Android Settings or the Cisco Jabber Voice for Android Settings, see the FAQs.
• Cisco Jabber Voice 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 Voice 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 Android OS 4.0 and later:
• Due to a limitation of Android OS 4.0 and later, Cisco Jabber Voice for Android 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 Voice (or another voice application) from the popup window.
3 Select Always to indicate that you always want to use Cisco Jabber Voice (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.
Supported Languages
Cisco Jabber Voice for Android is localized for the following languages:
• Chinese (China)
• Chinese (Taiwan)
• Danish
• Dutch (Netherlands)
• English (US)
• French (France)
9
• German
• Italian
• Japanese
• Korean
• Portuguese (Brazil)
• Russian
• Spanish
• Swedish
Caveats
• Release 9.1(5), on page 11
• Release 9.1(4), on page 12
• Release 9.1(3), on page 13
• Release 9.1(2), on page 15
• Release 9.1(1), on page 17
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
10
Procedure
Step 1
Step 2
Step 3
To access the Bug Toolkit, go to https://tools.cisco.com/bugsearch/search.
Sign in with your Cisco.com user ID and password.
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.1(5)
Open Caveats
There were no open caveats for Cisco Jabber Voice for Android 9.1(5) at the time of release.
Closed Caveats
There were no open caveats for Cisco Jabber Voice for Android 9.1(5) at the time of release.
See also the caveats for Cisco Unified Communications Manager for closed issues that may affect Cisco Jabber Voice for Android.
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 1: Resolved Caveats in Cisco Jabber Voice for Android 9.1(5)
Identifier
Severity
Component
Headline
CSCuj59360
severe
registration
Jabber can't establish a TCP connection to failover to primary
CCM node
CSCul24362
moderate
other
screen dim if cover proximity sensor after decline call
CSCul26958
moderate
ui
show on hold for incoming call if previous bg held call end by
far end
CSCul28749
moderate
callcontrol
can't place 2nd call if first call goes to vm and hangup
CSCul29162
moderate
callcontrol
no call waiting tone for 2nd incoming voip call
11
Release 9.1(4)
Open Caveats
There were no open caveats for Cisco Jabber Voice for Android 9.1(4) at the time of release.
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 Voice for Android.
Table 2: Closed Caveats in Cisco Jabber Voice for Android 9.1(4)
Identifier
Severity
Component
Headline
CSCuj26972
severe
documentation
Native Chooser is not displayed after selecting Always Use
Jabber
CSCud50918
moderate
performance
(MR) Memory leak over time Nexus
CSCue13574
moderate
other
No indication of callforward in Jabber android when receive
callfrwd
CSCue19552
moderate
dvo
Voicemail avoidance is not triggered if Alternate does not
match MI
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
CSCue71891
moderate
registration
Jabber stuck in Initializing loop after mobile call
CSCuh07400
moderate
callcontrol
Merge not working on CUMBE3K
CSCuh30069
moderate
callcontrol
Mobile SNR Call not getting connected when Jabber on other
call.
CSCuh32410
moderate
audio
Audio not maintained on Speaker after unplugging Headphones
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.
12
Table 3: Resolved Caveats in Cisco Jabber Voice for Android 9.1(4)
Identifier
Severity
Component
Headline
CSCud96318
moderate
other
Voltron:Ring tone doubles in volume level after the
speakerphone use
CSCue88014
moderate
callcontrol
No incoming ringtone for incoming calls: once
CSCue88286
moderate
registration
After exiting from Jabber,Jabber icon stays in notification bar
(~1 min)
CSCuf94059
moderate
crash
Crash encountered when call received in vibrate mode
CSCug83891
moderate
registration
Initialized/Initializing not connecting to CUCM
CSCuh32464
moderate
callcontrol
No vibration for incoming VoIP call when headset plugged in
Release 9.1(3)
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 Voice for Android.
Table 4: Open Caveats in Cisco Jabber 9.1(3) for Android
Identifier
Severity
Component
Headline
CSCud50918
moderate
performance
(MR) Memory leak over time Nexus
CSCud82839
moderate
protocol
(MOBILITY-867) app answer SNR call, shared line devices
show missed call
CSCud96318
moderate
other
Voltron: Ring tone doubles in volume level after the
speakerphone use
CSCue13574
moderate
other
No indication of callforward in Jabber android when receive
callfrwd
CSCue19552
moderate
dvo
Voicemail avoidance is not triggered if Alternate does not
match MI
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
CSCue34538
moderate
callcontrol
(3rdP)Loss of one way audio in VOIP call after 2nd VOIP call
is declined
13
Identifier
Severity
Component
Headline
CSCue35330
moderate
callcontrol
Issue in Jabber for Android when call is transferred from Jabber
iPhone
CSCue71891
moderate
registration
Jabber stuck in Initializing loop after mobile call
CSCue76813
moderate
registration
No prompt to enter SIP digest password
CSCue88014
moderate
callcontrol
No incoming ringtone for incoming calls: once
CSCue88286
moderate
registration
After exiting from Jabber,Jabber icon stays in notification bar
(~1 min)
CSCue90259
moderate
dvo
Not able to place additional DVOR calls after getting
Invalid/Busy error
CSCuf94059
moderate
crash
Crash encountered when call received in vibrate mode
CSCug83891
moderate
registration
Initialized/Initializing not connecting to CUCM
CSCuh07400
moderate
callcontrol
Merge not working on CUMBE
CSCuh23388
moderate
audio
Audio from this device is low, request to disable AEC & AGC
for MC40 devices
CSCuh30069
moderate
callcontrol
Mobile SNR Call not getting connected when Jabber on other
call.
CSCuh32410
moderate
audio
Audio not maintained on Speaker after unplugging Headphones
CSCuh32464
moderate
callcontrol
No vibration for incoming VoIP call when headset plugged in
CSCuh51445
moderate
callcontrol
speaker phone off when add 2nd call in an active call
CSCub44319
minor
other
No notification for an expired voicemail password
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 Voice for Android.
Table 5: Closed Caveats in Cisco Jabber 9.1(3) for Android
Identifier
Severity
Component
Headline
CSCue04869
moderate
callcontrol
Missed call log created for SNR call, when answered from
desk phone
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.
14
Table 6: Resolved Caveats in Cisco Jabber 9.1(3) for Android
Identifier
Severity
Component
Headline
CSCud88547
moderate
ui
(MR) After a call failed, screen frozen
CSCue26178
moderate
other
proximity sensor not work when voip call is keeping at
background
CSCug41885
minor
audio
there are should be no logs being generated for the digits
pressed
Release 9.1(2)
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 Voice for Android.
Table 7: Open Caveats in Cisco Jabber 9.1(2) for Android
Identifier
Severity
Component
Headline
CSCuc02212
moderate
performance
Android Jabber not indicating "call on hold"
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
CSCue04869
moderate
callcontrol
Missed call log created for SNR call, when answered from
desk phone
CSCue13574
moderate
other
No indication of callforward in J4A when receive callfrwd
CSCue19552
moderate
dvo
Voicemail avoidance is not triggered if Alternate does not
match MI
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
CSCue26178
moderate
other
proximity sensor not work when voip call is keeping at
background
CSCue26187
moderate
protocol
no announcement when DVOR to an invalid number over SIP
trunk
CSCue34538
moderate
callcontrol
(3rdP)Loss of one way audio in VOIP call after 2nd VOIP call
is declined
15
Identifier
Severity
Component
Headline
CSCue35330
moderate
callcontrol
Issue in Jabber for Android when call is transferred from Jabber
iPhone
CSCue71891
moderate
registration
Jabber stuck in Initializing loop after mobile call
CSCue76813
moderate
registration
No prompt to enter SIP digest password
CSCue88014
moderate
callcontrol
No incoming ringtone for incoming calls: once
CSCue88286
moderate
registration
After exiting from Jabber,Jabber icon stays in notification bar
(~1 min)
CSCue90259
moderate
dvo
Not able to place additional DVOR calls after getting
Invalid/Busy error
CSCub44319
minor
other
No notification for an expired voicemail password
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 Voice for Android.
Table 8: Closed Caveats in Cisco Jabber 9.1(2) for Android
Identifier
Severity
Component
Headline
CSCud89971
moderate
performance
GS3 Jellybean memory leak
CSCue21988
moderate
callcontrol
Not able to place or receive calls
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 9: Resolved Caveats in Cisco Jabber 9.1(2) for Android
Identifier
Severity
Component
Headline
CSCud67985
severe
callcontrol
No incoming call indication when user press power button
once
CSCud72905
severe
callcontrol
Incoming calls are VOIP not SNR
CSCue46732
severe
callcontrol
severe callcontrol Jabber crash upon attempted answering a
call
CSCud41937
moderate
ui
(MR) tapping on Accept did not answer call - frozen
CSCud70748
moderate
crash
Jabber Crashed searching directory for Jin on Alpha
16
Identifier
Severity
Component
Headline
CSCud70752
moderate
other
Send Logs does not work (intermittently)
CSCue26251
moderate
callcontrol
DVOR calls stopped being placed, then resumed after 10 min
CSCue26475
moderate
crash
4:34 Jabber would not respond and then crashed
CSCue31301
moderate
installation
Add zydeco phone to the exclusion list for Jabber
CSCue47086
moderate
protocol
Jabber does not ring+vibrate on incoming call
CSCue51403
moderate
protocol
native ring volume got reset, after incoming voip call
CSCue54085
moderate
callcontrol
Jabber crashed when clicked on Reconnect (directory)
CSCud42945
minor
dvo
Jabber auto exit and remain in disconnected status all the time
CSCud75878
minor
ui
call back number text description is not readable
CSCud77900
minor
ui
proximity sensor is on should prevent the back and home button
press
CSCud77995
minor
ui
missed calls should not reappear after clearing it
Release 9.1(1)
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 Voice for Android.
Table 10: 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
17
Identifier
Severity
Component
Headline
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
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 Voice for Android.
Table 11: 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
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.
18
Table 12: 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
Troubleshooting information is available for system administrators and users in the following guides:
• System administrators: See the Cisco Jabber Voice for Android Administration Guide for Release 9.1(4) in the installation
guides list.
• Users: See the Cisco Jabber Voice for Android Frequently Asked Questions (FAQs) for Release 9.1(4) in the user guides list.
Documentation Updates
For the latest versions of all documentation for all releases of Cisco Jabber Voice for Android, go to the documentation home page.
19
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)
© 2013
Cisco Systems, Inc. All rights reserved.
Americas Headquarters
Cisco Systems, Inc.
San Jose, CA 95134-1706
USA
Asia Pacific Headquarters
Cisco Systems (USA) Pte. Ltd.
Singapore
Europe Headquarters
Cisco Systems International BV
Amsterdam, The Netherlands
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the
Cisco Website at www.cisco.com/go/offices.