Cisco Cisco Jabber Voice for Android Release Notes

Page of 12
 
6
Release Notes for Cisco Jabber for Android, Release 8.6.2
  Limitations and restrictions
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 
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.