Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats 12.7(1) section for a list of caveats fixed in this release.

• Apple has new requirements for trusted certificates in iOS 13 (see https://support.apple.com/en-us/HT210176). Ensure that the certificates on the Unified Communications Mananger, IM & Presence, and Expressway servers meet these requirements. If your certificates don't meet these requirements, Jabber prompts users to accept the certificates for each session.

• Webex site disclaimers don't appear when you join Webex meetings from Jabber. This limitation applies whether joining from the meeting reminder popup, or by selecting Join in Webex in Jabber.

• If you make a Cisco Jabber for iPhone and iPad call using Expressway for Mobile and Remote Access over a 2G, 3G, or 4G network, you may experience audio quality issues from network instability.

• Applies to Cisco TelePresence Video Communication Server Control (VCS) versions earlier than 8.10.X.

  Configure the editable inbound rules to enable single number reach for those who use Cisco Jabber over Mobile and Remote Access. For more information, see Limitations in Enable Single Number Reach section from the Feature Configuration Guide for Cisco Jabber 12.0.

• Cisco Jabber for mobile clients don't show the Favorite icon for users with Phone Only account.

• Without Apple Push Notifications (APNs), when Cisco Jabber receives an incoming call or chat, the iOS doesn't wake Cisco Jabber. The call or instant message appears on the device after several minutes or when you bring Cisco Jabber the foreground. As a workaround, reset the network settings for your iOS device by going to Settings > General > Reset > Reset Network Settings.

• Users can no longer edit their Phone Services servers manually, except when they are in hybrid cloud mode. In hybrid deployments, administrators can configure the Phone Services servers to be editable.

• The first usage of Secure Phone functionality must be on the corporate network or VPN to ensure proper certificate installation.

• Voice recognition for voicemail PIN is highly sensitive to background noise. The system may interpret background noise as user input, even when the user doesn't input anything. See System Administration Guide for Cisco Unity Connection to disable this function. https://www.cisco.com/c/en/us/support/unified-communications/unity-connection/products-maintenance-guides-list.html

• Certificate validation windows pop up when the certificate on Cisco Unified Communications Manager is issued by an intermediate certificate authority. Use a certificate that is signing with the root rather than an intermediate certificate authority.

• From Release 10.5 onward, all the Cisco Jabber account related files, including Configuration, Contacts, Credentials, History, Logs, Photo and so on, aren't backed up on the iCloud and iTunes due to privacy reasons.

• Creating and Configuring Devices for Users in Cisco Unified Communications Manager 11.0—If you are creating devices for users in Cisco Unified Communications Manager 11.0, you can now specify a key order as RSA Only, EC Only, EC Preferred, or RSA Backup. However, the EC Only option is not currently supported by Cisco Jabber, and if you select it, the client fails to connect to the server.

• With Jabber running in the background, if users try moving between networks; for example, from WiFi to 3G, the client disconnects from the servers. It can take up to 11 minutes to reconnect and can lead to missed calls. To avoid missed calls, it is recommended to enable Apple Push Notification service.

• There is a known issue with signing into Cisco Jabber for some users who have migrated to Common Identity. If users receive an Incorrect user name or password error message when entering their username and password, see the following knowledge base article, https://cisco-support.webex.com/guest/articles/en_US/Troubleshooting/WBX000019555/myr=false.

• CallKit functionality is deactivated in China due to government regulations.

iPhone

• Due to some limitations when Cisco Jabber for iPhone and iPad is running on iOS, Configure the Single Number Reach (SNR) feature within Cisco Unified Communications Manager for users that require 100% reliability in call notifications. The limitations include:

  • iOS may shut down Cisco Jabber and other applications that are running in the background to preserve resources. While the client attempts to relaunch, there is a possibility that calls may be missed. To minimize the impact, it is recommended to enable Apple Push Notification service.

  • Without Apple Push Notifications (APNs), the device sometimes switches connection from the Wi-Fi data network to the mobile voice network while the device is in Sleep mode. Incoming calls may be missed due to this issue. To prevent this issue, go to the iPhone Settings and turn off Cellular Data or alternatively turn on SNR.

  • The VPN can disconnect when Connect-On-Demand is enabled and the user changes networks. Cisco Jabber for iPhone and iPad may take up to 11 minutes to reconnect through the VPN. This issue can lead to missing incoming calls. This occurs when the Wi-Fi signal is not stable or sometimes the mobile network takes priority and it switches between Wi-Fi and mobile network, while Jabber is unable to quickly connect to phone services during the handover. After Cisco Jabber for iPhone and iPad reconnects, users who have voicemail enabled in their account receive voicemail notifications for any missed calls that went to voicemail. To minimize the time to reconnect, users can bring the app to the foreground after changing connection environments. It is also recommended to enable Apple Push Notification service.

• Cisco Webex Meetings— If the meeting siteType is ORION, then Cisco Jabber for iPhone and iPad cannot start Webex Meetings over Expressway for Mobile and Remote Access network.

• If Cisco Jabber on iPhone is unable to reach the primary subscriber due to packet loss, it does not failover to secondary CM node. For more information, see CSCux83785.

• If you are setting up Dial via Office - Reverse (DVO-R) on Cisco Unified Communications Manager consider the following:

  • The feature only applies to iPhone; it is not supported on iPad or iPod Touch devices because it requires that the device can access a mobile network.

  • You can make DvO-R calls over Expressway for Mobile and Remote Access when you are outside corporate network. DVO-R is supported over Cisco Expressway X8.7 and Cisco Unified Communications Manager 11.0(1a)SU1.

  • DVO enabled devices may encounter issues registering with Cisco Unified Communications Manager 8.6 and above. Resetting the device from the Cisco Unified Communications Manager administrative interface fixes this issue.

  • The feature requires Cisco Unified Communications Manager Release 8.6.2 SU4, 9.1.2, or 10.x.

  • The feature cannot be used in conjunction with the Secure Call feature. Secure calls cannot be established if DVO-R is enabled.

  • 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.

• If the user is on a Cisco Unified Communications Manager call and receives an incoming mobile call, iPhone starts ringing and prompts the user to answer or decline the mobile call. At the same time, the Cisco Unified Communications Manager call on Cisco Jabber goes on hold automatically.

• To ensure that you do not miss incoming Cisco Jabber chats and calls, go to iOS Settings > Notification Center and check that the Cisco Jabber sound setting is turned on.

• If you receive a Cisco Unified Communication Manager call, while placing a VoIP call, Cisco Jabber for iPhone and iPad sends the incoming call to voicemail. If you do not have voicemail, Cisco Jabber for iPhone and iPad ignores the call.

• The maximum number of participants for ad-hoc conferences is limited to three; this is the maximum number of calls for TCT devices. The maximum participants for ad-hoc conference is configured on Cisco Unified Communication Manager in Service Parameter Configuration > Clusterwide Parameters > Maximum Ad Hoc Conference Required.

• Voice and video quality over non-corporate Wi-Fi or mobile data networks cannot be guaranteed.

• The quality of video calls varies depending on the network connection. Cisco Technical Assistance Center (TAC) cannot troubleshoot video quality when you use 3G or 4G networks to connect Cisco Jabber for iPhone and iPad with Cisco AnyConnect Secure Mobility Client or another VPN client.

• 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 incoming call, your Cisco Jabber for iPhone and iPad Cisco Unified Communications Manager 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 and then tap Resume so that your current caller can hear you again. If your device is locked, quickly press the On/Off Sleep/Wake button twice to decline the call, and then tap Resume.

• SIP Digest Authentication is not supported.

• Cisco Unified Communications Manager as a directory source is capable of scaling to 50% of the device capacity that a Cisco Unified Communications Manager node can handle.

• When the device is in Do Not Disturb (DND) mode and locked, then it vibrates upon receiving a Cisco Jabber call.

• With iOS versions 10 and 11 with Cisco Jabber 12.0, you cannot receive call notifications on Apple Watch because CallKit can’t work with Apple Watch. This is an Apple iOS limitation.

• When in the background for a few hours, Jabber relaunches without notification.

iPad

• When users transition between networks, their availability status may not be accurate.

• Cisco Jabber for iPhone and iPad supports interoperability and optimal video quality with Cisco TelePresence System (CTS) devices if you use a TelePresence or video bridge to connect the devices. The number of devices that you can use for joining a video call will be determined by the Multipoint Control Unit (MCU) and settings defined for the conference bridge.

  Required versions and settings for CTS interoperability
  VCS call control environment: All CTS devices must be using 1.9.1(68) or a later firmware version.
  Cisco Unified Communications Manager call control environment: All CTS devices must be using 1.9.1(68) or a later firmware version. Create Media Regions for iPad and CTS by following these steps: Provision two media regions with the first region for CTS using a maximum video call bit rate of 32000 Kbps and second region for iPad using a maximum video call bit rate of 768 Kbps. Create a region relationship from the CTS region to the iPad region, described in step 1, using a maximum video call bit rate of 512 Kbps.
  To verify your VCS firmware and hardware codec versions, check the Device information screen in the Cisco TelePresence System Administration.

  Consult the Cisco Unified Communications Manager Administration documentation for details about setup.

• You cannot block contacts who are within your own organization.

• If you delete a group of contacts on another device other than an iPad, they may still appear in Cisco Jabber for iPhone and iPad. Sign out and then sign in again for the changes to take effect.

• If you start an action, such as signing in or tapping Webex Meeting to start a meeting, and then bring Cisco Jabber for iPhone and iPad to the background before the action completes, you can't successfully complete the action.

• If you tap Webex Meeting to start a meeting, the system sends a meeting invitation when either the meeting starts or 60 seconds has elapsed.

• When on a Cisco Jabber call and you put Cisco Jabber to the background, sometimes the call indicator shows Cisco Jabber recording, depending on the iOS versions.

Apple Watch

Notifications aren't supported on Apple Watch in Jabber team messaging mode.

Multiple Resource Login

When a user signs in to multiple instances of the client at the same time, the chat feature behaves as follows:

• The first incoming chat message is sent to all the clients.

• The first client to reply to the incoming chat message gets all the subsequent messages. The other clients do not get these subsequent incoming messages.

• If the client does not use the chat feature for 5 minutes, the next incoming message is sent to all the clients again.

Contact Resolution for Enterprise Groups

Jabber resolves contacts in enterprise groups individually rather than all at once. As a result, when you add an enterprise group to your users' contact lists—or if they clear their local cache—they'll only see the username and domain for each person until they hover over or interact with them.

Caveats describe unexpected behavior. The following sections describe how to obtain the latest information.