This document contains release information for Cisco Jabber for iPhone, Release 9.1(1).
To obtain the latest Cisco Jabber for iPhone client software, use either the Apple App Store on iTunes or the App Store application on the iPhone. Your device must run iOS 6 or 6.1 to access and use the Cisco Jabber for iPhone application.
Cisco Jabber for iPhone provides iPhone users with Enterprise calling, visual voicemail, and access to the corporate directory from an iPhone or iPod Touch.
iPad users can download Cisco Jabber for iPad from the Apple App Store. For more information about Cisco Jabber for iPad, see the documentation home page.
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 iPhone with Cisco AnyConnect Secure Mobility Client. Although other VPN clients are not officially supported, you may be able to use Cisco Jabber for iPhone with other VPN clients.
The voice quality of Internet calls varies depending on the Wi-Fi or mobile data network connection. Cisco Technical Assistance Center (TAC) cannot troubleshoot voice quality when you use mobile data networks or noncorporate Wi-Fi networks to connect Cisco Jabber for iPhone with Cisco AnyConnect Secure Mobility Client or another VPN client.
User Features and Benefits
With Cisco Jabber for iPhone, 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.
- Manage Internet calls using many of the standard in-call features such as hold, transfer, and conference
- Access your work voicemail system.
- Search your corporate directory.
- Launch IM chat sessions with contacts.
- View your call history for calls managed using Cisco Jabber for iPhone.
- Move Internet calls between your desk phone and iOS device.
- Call coworkers by saying their names using Voice Dialing.
- 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 iPhone with Cisco AnyConnect Secure Mobility Client. Although other VPN clients are not officially supported, you may be able to use Cisco Jabber for iPhone with other VPN clients.
Cisco Jabber for iPhone 9.1(1) contains a number of bug fixes. See Release 9.1(1) for more information.
Cisco Jabber for iPhone 9.1(1) introduces support for iOS 6.1.
Cisco Jabber for iPhone 9.1(1) introduces the Dial via Office - Reverse (DVO-R) feature.Important:
The DVO-R feature requires:
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:
If you upgrade Cisco Jabber for iPhone 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 iPhone 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 iPhone Release 9.1(1) Administration Guide.
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 set user-controlled Voicemail Avoidance, this feature applies to both DVO-R and Mobile Connect calls.
The iPhone must be able to connect to the corporate network using voice-ready Wi-Fi.
For optimal user experience when using Cisco Jabber for iPhone over your corporate Wi-Fi network, Cisco recommends that you:
- Design your Wi-Fi network to eliminate gaps in coverage as much as possible, including in areas such as elevators, stairways, and outside corridors.
- Ensure that all access points assign the same IP address to the iPhone. Calls are dropped if the IP address changes.
- Ensure that all access points have the same SSID. Hand-off may be much slower if the SSIDs do not match.
- Ensure that all access points broadcast their SSID. If the access points do not broadcast their SSID, the iPhone may prompt the user to join another Wi-Fi network, which interrupts the call.Conduct a thorough site survey to minimize network problems that could affect voice quality. Cisco recommends that you:
For more information, see:
- The “VoWLAN Design Recommendations” section in the Enterprise Mobility 4.1 Design Guide.
- The Cisco Unified Wireless IP Phone 7925G Deployment Guide.
- The Capacity Coverage & Deployment Considerations for IEEE 802.11g white paper.
- The Solutions Reference Network Design (SRND) for your Unified CM release.
Bluetooth use can cause voice quality and connectivity issues. For more information, see Bluetooth and Network Interference.
If users connect to the network remotely, the iPhone must be able to connect to the corporate network using a solid, high-bandwidth VPN connection. Voice quality is dependent on connection quality and cannot be guaranteed.
Cisco Unified Communications Manager Requirements
- Cisco Unified Communications Manager:
- Unified CM 7.1(5), starting with 7.1(5.32900-2 ) or 7.1(5b)su3
- Unified CM 8.0(3), starting with 8.0(3.21900-8) or 8.0(3a)su1
- Unified CM 8.5(1), starting with 8.5(1.11900-21) 8.5(1)su1
- Unified CM 8.6(2), starting with 8.6(2.21008-1) or 8.6(2a)su1
- Unified CM 9.1(1)Important:
The DVO-R feature requires:
Unified CM 8.6(2.21008-1) or 8.6(2a)su1 is required to resolve the following issue: When a network change occurs, Cisco Jabber for iPhone displays the green phone icon and the “Connecting” status, even if the application is not connected to the new network (CSCtu00209 and CSCtt97001).
- Unified Communications Manager Express:
- Cisco Business Edition:
- Desk phone integration: The desk phone for each user must be CTI-controllable to ensure that users can move active calls from the desk phone to Cisco Jabber for iPhone.
Required Codecs for Calls
Minimum requirement for low-bandwidth availability: G.729a.
Users can turn Low Bandwidth mode on and off in the client settings if they experience voice quality issues.
Normal mode supports G.711 and G.729a.
Low Bandwidth mode supports G.729a only.
Requirements for Voicemail (Optional)
Requirements for Integration with Corporate Directory (Optional)
Use one of the following for Lightweight Directory Access Protocol (LDAP):
Required only to support corporate directory search and organizational chart.
Requirements for Survivable Remote Site Telephony (Optional)
Survivable Remote Site Telephony (SRST) Release 8.6 and 8.8
Requirements for Cisco AnyConnect Secure Mobility Client (Optional)
- iOS devices must run Cisco AnyConnect Secure Mobility Client Version 3.0.09097, which is available from the Apple App Store
- Cisco ASA 5500 Series Adaptive Security Appliance 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) requirements if using certificate-based authentication: Cisco IOS Certificate Server or Microsoft Windows Server 2008 Enterprise Certificate Authority.
Requirements for VPN On Demand (Optional)
The Apple iOS On-Demand VPN feature requires certificate-only authentication. If you set up the Adaptive Security Appliance (ASA) without certificate-only authentication, the user must manually initiate the AnyConnect VPN connection as needed.
The iPhone must be able to access the corporate network, servers, and telephony endpoints using a VPN client, such as Cisco AnyConnect Secure Mobility Client.
Requirements for Users and Devices
Cisco Jabber for iPhone is available from the Apple App Store.
Cisco supports Cisco Jabber for iPhone on the following iOS devices:
- iPhone model 3GS, 4, 4S, and 5
- iPod Touch third or fourth generation (third-generation iPod Touch requires an external microphone for calls)
- iOS support: iOS 6 and 6.1
Bluetooth headset support:
- iPhone: supported (optional)
- iPod Touch: not supported. iPod Touch third generation requires a wired headset. You can use iPod Touch fourth generation in speakerphone mode or with a wired headset.
The voice dialing gesture feature is supported only on devices with a proximity sensor. iPod Touch does not currently have this sensor.
The device must be able to access the corporate network using Wi-Fi or VPN.
The desk phone for each user must be CTI-controllable to ensure that users can move active calls from the desk phone to Cisco Jabber for iPhone.
Installation and setup instructions are available for system administrators and end users in the following guides:
- System Administrators: See the Administration Guide for Cisco Jabber for iPhone for your release in the installation guides list.
- Users: See the Cisco Jabber for iPhone Frequently Asked Questions (FAQs) for your release in the user guide list.
Users can obtain the software for this product from the App Store using iTunes or the App Store application on the iPhone.
Limitations and Restrictions
- If you receive an Internet call while placing an Internet call, Cisco Jabber for iPhone sends the incoming call to voicemail. If you do not have voicemail, Cisco Jabber for iPhone ignores the call.
- Unified CM 8.6(2.21008-1) or 8.6(2a)su1 is required to resolve the following issue: When a network change occurs, Cisco Jabber for iPhone displays the green phone icon and the “Connecting” status, even if the application is not connected to the new network (CSCtu00209 and CSCtt97001).
- Due to an Apple iOS issue, the device sometimes drops from the Wi-Fi data network to the mobile voice network while the device is in sleep mode (CSCub14854). This issue can lead to missed incoming calls. To prevent this issue, turn off Cellular Data in the native Settings app.
- Due to an Apple iOS issue, when a user leaves and then re-enters the Wi-Fi network and Cisco Jabber for iPhone is in background, the app can take up to 11 minutes to reconnect. This issue can lead to missing incoming calls. After Cisco Jabber reconnects, users who have voicemail enabled will receive voicemail notifications for any missed calls that went to voicemail. To minimize the reconnection time, users can bring the app to the foreground after changing connection environments.
- Due to an Apple iOS issue, the VPN can disconnect when Connect-On-Demand is enabled and the user changes networks. Cisco Jabber for iPhone may take up to 11 minutes to reconnect through the VPN. This issue can lead to missing incoming calls. After Cisco Jabber reconnects, users who have voicemail enabled will receive voicemail notifications for any missed calls that went to voicemail. To minimize the reconnection time, users can bring the app to the foreground after changing connection environments.
- Voice quality over noncorporate Wi-Fi or mobile data networks cannot be guaranteed.
- For voice quality and connectivity issues inherent in Bluetooth use, see Bluetooth and Network Interference.
- Ringtone audio is not sent through some Bluetooth headsets.
- If you use a Bluetooth headset while on a Cisco Jabber for iPhone call, the call control buttons on the headset are not active.
- If you use Unified CM to set up Cisco Dual Mode for iPhone devices to automatically pass LDAP passwords to the client, the Unified CM TFTP server stores and sends these passwords in clear text. If you have security concerns, tell users to manually enter these passwords.
- If you set up the Org chart feature, for managers who have more than 25 direct reports, Cisco Jabber for iPhone displays only the first 25 reports.
- If you receive an incoming call on your iPhone, the iPhone automatically disables the microphone for all other applications, and there is no time to inform your current caller that you need to take another call. If you accept the new call, your Cisco Jabber Internet call is automatically placed on hold, and you cannot return to it until you end the iPhone call. To work around this issue, decline the call so that your current caller can hear you again. If your device is locked, press the On/Off Sleep/Wake button twice quickly to decline the call.
- The DVO-R feature requires:
- Due to a limitation with Cisco Unified Communications Manager, if the user places a Dial via Office - Reverse call to an invalid phone number over a SIP trunk, the user he user hears several seconds of silence instead of an audio message stating the number was invalid.
- If the administrator updates an existing destination number in the Mobility Identity for a Cisco Dual Mode for iPhone 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 iPhone Settings or the Cisco Jabber for iPhone Settings, see the FAQs.
- In the Cisco Jabber for iPhone Settings, manually update the phone number in the DVO Callback Number field.
- In the Cisco Jabber for iPhone Settings, delete the current number in the DVO Callback Number field, and then exit and restart Cisco Jabber for iPhone.
- The following options appear in the Product-Specific Configuration Layout section on the device configuration page in Unified CM, but are not supported in this release:
- For potential unexpected behavior and issues that users may encounter, see the FAQs.
- SIP Digest Authentication is not supported with Cisco Jabber for iPhone, Release 9.1.1.
iOS Version Support Policy for Cisco Jabber for iPhone
Cisco supports Cisco Jabber releases only on the latest major iOS release. Apple maintains iOS, provides free iOS updates, and actively encourages users to upgrade to new iOS releases. To help enterprise customers transition to new major iOS updates, Cisco supports the last dot release of the previous major release for three months after a new release is introduced.
Cisco Jabber for iPhone Release 9.1(1) is supported on Apple iOS 6.0 or later running on an Apple iPhone 3GS, 4, 4S or 5 or an Apple iPod touch third or fourth generation.
Upgrade from Cisco Mobile to Cisco Jabber for iPhone
Follow these instructions to upgrade users from Cisco Mobile Release 8.0 to Cisco Jabber for iPhone Release 9.1(1).
Cisco Jabber for iPhone replaces Cisco Mobile 8.1. For users upgrading from Cisco Mobile Release 8.1 to Cisco Jabber for iPhone Release 9.1(1), have users download the Cisco Jabber for iPhone application from the App Store. For Administrators, see Administration Guide for Cisco Jabber for iPhone for your release in the installation guides list.
- To support multitasking, make the following changes in Cisco Unified Communications Manager:
- Create a dedicated SIP Profile with required settings. For more information, see Administration Guide for Cisco Jabber for iPhone for your release in the installation guides list.
- Assign this dedicated SIP Profile on the Cisco Dual Mode for iPhone device page for each user of Cisco Jabber for iPhone.
- Send users their provisioning information for Cisco Jabber for iPhone. See the “User Instruction” section in the Administration Guide for Cisco Jabber for iPhone for your release, as applicable to your deployment.
- Send users instructions to:
- Download and install Cisco Jabber for iPhone Release 9.1(1) from the App Store.
- Restart the phone.
- Perform other required steps for a new installation in your environment, as described in the “User Instruction” section in the Administration Guide for Cisco Jabber for iPhone for your release.
Bluetooth and Network Interference
Bluetooth headsets use the same 2.4 GHz frequency as 802.11b, -g, and -n Wi-Fi networks and many other devices, such as microwave ovens and cordless phones. For this reason, interference is likely to impact Bluetooth transmissions, and Bluetooth headsets may interfere with the Wi-Fi connection to the iPhone. This issue is not specific to Cisco Jabber for iPhone but can result in dropped or interrupted calls and voice quality issues.
To minimize interference from Bluetooth headsets on the Wi-Fi network, ensure that a strong Wi-Fi signal is available throughout the coverage area, as described in the Network Requirements.
Also see the following Apple articles:
- AirPort and Bluetooth: Potential sources of wireless interference
- Bluetooth: Static heard on Bluetooth headset
Cisco TAC cannot troubleshoot these issues.
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 time of shipping.
See also the caveats for Cisco Unified Communications Manager for open issues that may affect Cisco Jabber for iPhone.
Table 1 Open Caveats in Cisco Jabber 9.1(1) for iPhone
Identifier Severity Component Headline CSCty88527 moderate core (MR)Spurious NumberOfRegisteredPhonesDropped Alerts seen in alpha CSCub14854 moderate voip Phone drops from wifi to 3G if standby awhile causing app to miss calls CSCuc72723 moderate core DVO - VMA not working when dial rule prefix added to MI/callback numbers CSCuc92921 moderate core DVO - if dvo enabled.app can't register without enabling CUMC CSCud27521 moderate core Hissing/Squeeky noise when on speakerphone and volume is set max CSCud37472 moderate other DVO - user control - press digit 0 doesn't connect the dvo call CSCud46689 moderate core App gets stuck connecting to UCM, but vm and directory are okay (SIPCC) CSCud60607 moderate core No announcement when DVOR to an invalid number over SIP trunk CSCud70366 moderate documentation (Doc)app Doc need clarification on LDAP attribute replication to GC CSCud83767 moderate core When making DVO call, app doesn't look up caller id from server CSCud97264 moderate core No indication of call-forward when received w Jabber for IPhone CSCue13486 moderate core DVO-callback alert still shows after dismiss callback error CSCue16877 moderate documentation Documentation for CFUR for Cisco Jabber need to be updated CSCue17449 moderate ui No change in Jabber IPhone while giving Reset in CME CSCue26189 moderate voip Not able to place or receive calls CSCue27246 moderate voip Issue with Jabber-on-iphone while it is in a conference call CSCue27276 moderate voip Issue when Jabber-on-iPhone is part of a hunt list CSCue27521 moderate core (MR)app stay at connecting for 8 mins after sign in CSCue27555 moderate core DVO-if switch network when initiating dvo, it keeps failing for a while
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 iPhone.
Table 2 Closed Caveats in Cisco Jabber 9.1(1) for iPhone
Identifier Severity Component Headline CSCts23172 moderate voip Not able to receive call in background when using AnyConnect (iPod) CSCua34948 moderate ui Jabber client not resetting when CUCM 7.1.5 admin applies config CSCub27773 moderate core back/forth wifi to no wifi, app can't pull up anyconnect CSCub58485 moderate ui Jabber stuck while changing voicemail account data CSCub82101 moderate voip Cisco jabber client DTMF responses unrecognized by CME CSCuc35027 moderate other Jabber for iPhone Notification-'Close' option is not shown in Japanese. CSCuc38121 moderate core wifi+anyconnect, app is disconnected if lock screen in iPod CSCuc95478 moderate other If silent mode and background, app could not play ringtone CSCuc98231 moderate core DVO - when dvo enabled, can't sign in with different em profile CSCud01547 moderate core DVO - when dvo enabled, can't provision app with sip digest CSCud03182 moderate core DVO - VMA does not work to alternate callback# (UCM feature request) CSCud19386 moderate documentation Cisco Jabber IPhone goes On Hold when Native calls comes in GSM Network CSCud23785 moderate other Proximity sensor not work when voip call is keeping at background CSCud34050 moderate other DVO call fails if interrupt by another gsm call when calling CSCud42236 moderate other Can provision from wizard but later never registers if no MI and 3g+vpn CSCud52550 moderate core After handoff-DN on iPhone4 w VPN, subsequent VoIP calls sometimes fail CSCud61535 moderate core From corp wifi to 3G+anyconnect, ap got stuck in reconnecting state CSCud67614 moderate voip iPhone 5 wired headset outgoing volume is to low CSCue13104 moderate voip (MR)sometimes call isn't auto resume and red bar disappear if use siri
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 iPhone
Identifier Severity Component Headline CSCue22113 severe core Call leak for DVO call CSCub44744 moderate core app lists more participants than actually attending for conference CSCub78606 moderate ui Scrolling in status bar displayed choppy after msg changed CSCub82101 moderate voip Cisco jabber client DTMF responses unrecognized by CME CSCuc09759 moderate voip HandOFF DN Number works 10% of the time CSCuc29846 moderate core app does not save new pic and item label for existed contact
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 iPhone, 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 © 2013, Cisco Systems, Inc. All rights reserved.