 Feedback
|
Contents
- Release Notes
- Introduction
- User Features and Benefits
- What's New
- System Requirements
- Finding Documentation
- Tips for Searching Cisco Documentation
- Installation Notes
- Limitations and Restrictions
- Supported Languages
- Important Notes
- Upgrade from Cisco Mobile to Cisco Jabber for iPhone
- Bluetooth and Network Interference
- Caveats
- Bug Toolkit
- Release 9.0(2)
- Release 9.0(1)
- Troubleshooting
- Documentation Updates
Release Notes
This document contains release information for Cisco Jabber for iPhone, Release 9.0(2).
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 one of the following iOS releases to access and use the Cisco Jabber for iPhone application:
Introduction
Cisco Jabber for iPhone provides iPhone users with VoIP 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.
NoteThe voice quality of 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 and receive calls using your work number.
- Use advanced calling features such as conference calls, call transfer, and call park.
- 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 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.
NoteTo 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.
What's New
Cisco Jabber for iPhone 9.0(2) now supports IOS 6. This release also contains bug fixes. See Release 9.0(2) for more information.
System Requirements
Network Requirements
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.0(1)
NoteUnified 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 Unified Communications Manager 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 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 2.5.5130, 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, and 4S
- iPod Touch third or fourth generation (third-generation iPod Touch requires an external microphone for calls)
- iOS support:
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.
Finding Documentation
Documentation for administrators: See the installation guides list.
Documentation for users: See the user guides list.
Tips for Searching Cisco Documentation
We recommend that you use the external Google Search (http://www.google.com) to find information.
Use the following formula in the search field:
<product name> <release number> <topic keywords> site:cisco.com
Examples of Google Search entries:
Installation Notes
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.
NoteUsers 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 a call while placing a 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.
- 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 reporting structure feature, for managers who have more than 25 direct reports, Cisco Jabber for iPhone displays only the first 25 reports.
- 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.
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.0(2) is supported on:
Important Notes
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.0(2).
NoteCisco Jabber for iPhone replaces Cisco Mobile 8.1. For users upgrading from Cisco Mobile Release 8.1 to Cisco Jabber for iPhone Release 9.0(2), 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.0(2) 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.
Caveats
Bug Toolkit
ProcedureKnown 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 NextFor information about how to search for bugs, create saved searches, and create bug groups, click Help on the Bug Toolkit page.
Release 9.0(2)
Open Caveats
The following bugs 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.0(2) 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 CSCub44744 moderate core app lists more participants than actually attending for conference CSCub58485 moderate ui Jabber stuck while changing voicemail account data 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 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 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 for iPhone.
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 3 Resolved Caveats in Cisco Jabber 9.0(2) for iPhone Identifier
Severity
Component
Headline
CSCub18051 severe core iOS6: sometimes app crash if voip is interrupted by gsm call CSCub94293 severe core iOS6: sometimes app crash if call interrupted by native alarm CSCuc25326 severe core app crash if tap speaker when fail to resume held call in poor network CSCuc33944 severe voip iOS6:app can receive/place voip call over facetime call then crash CSCub17112 moderate core iOS6: ui glitches appear in app CSCub17113 moderate core iOS6: directory search button missing in contacts tab view CSCub36576 moderate core iOS6: when app in foreground and lock screen, can't play ringtone CSCub52457 moderate core jabber on iphone got hang when Call Manager is down while making a call CSCub64201 moderate core Press and Hold the 'Answer' button may cause the app to hang CSCub66943 moderate core During First time provisioning or Sign-in to EM, application may crash. CSCub89449 moderate other iOS6: the Add a contact button disappear after checking contact detail CSCuc00460 moderate core if incoming call when on notification center, app plays no ringtone CSCuc02831 moderate core ldap pwd lost after upgrade from 8.6.5 app store version CSCuc25589 moderate core after long idle, sometimes app fails to answer 1st incoming call CSCuc25717 moderate core iOS6: voip lost audio on iPhone4 after native gsm call ends interruption Release 9.0(1)
Open Caveats
The following bugs 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 4 Open Caveats in Cisco Jabber 9.0(1) for iPhone Identifier
Severity
Component
Headline
CSCua34948 moderate ui Jabber client not resetting when CUCM 7.1.5 admin applies config CSCub14854 moderate voip Phone drops from wifi to 3G if standby awhile causing app to miss calls CSCub44744 moderate core app lists more participants than actually attending for conference CSCub52457 moderate core jabber on iphone got hang when Call Manager is down while making a call CSCub58485 moderate ui Jabber stuck while changing voicemail account data CSCub64201 moderate core Press and Hold the 'Answer' button may cause the app to hang CSCub66943 moderate core During First time provisioning or Sign-in to EM, application may crash. 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 for iPhone.
Table 5 Closed Caveats in Cisco Jabber 9.0(1) for iPhone Identifier
Severity
Component
Headline
CSCtu15500 moderate voip (UCM) Call drop after user handoff call to mobile w Anyconnect (VPN) CSCtz92454 moderate voip Bluetooth connectivity drops when diverting second call CSCua06696 moderate ui vm in native notification doesn't show contact name after ldap query CSCub17695 moderate core (iOS)Phone on wifi, User sees "cellular connection disabled" message 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 6 Resolved Caveats in Cisco Jabber 9.0(1) for iPhone Identifier
Severity
Component
Headline
CSCtr99457 moderate core if add number to contact when conference, ui issue leads to call drop CSCts01981 moderate core A native saved contact name does not take priority for name resolution CSCtx19935 moderate ui deskphone integration pop-up should appear on MV when deskphone answers CSCty78686 moderate core send to mobile on UCM 9.0 call Cisco Jabber not mobile 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 iPhone in the installation guides list.
- Users: See the Frequently Asked Questions document for your release of Cisco Jabber for iPhone in the user guides list.
Documentation Updates
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 © 2012, Cisco Systems, Inc. All rights reserved.
