The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Book Contents Book ContentsPush Notifications Deployment Guide
This document describes how to configure Push Notifications on Cisco Unified Communications Manager and the IM and Presence Service for compatible Cisco Jabber and Cisco Webex clients that run on iOS or Android devices. With Push Notifications, your deployment uses Google or Apple's cloud-based Push Notification service to push voice call, video call, and instant message notifications to Cisco Jabber and Cisco Webex for iOS and Android clients that are running in the background. You must enable Push Notifications to maintain persistent communication with clients that are running in the backgound.
This document describes how to enable Push Notifications for the following deployment types:
| Note | The Webex Messenger cloud retires end of 2020. For more information, see https://blogs.cisco.com/collaboration/making-the-move-to-modern-messaging. |
In alignment with Apple's changes to the iOS notification architecture, Cisco Jabber and Cisco Webex clients on iOS are implementing Apple Push Notification support for notifications. We highly recommend that customers upgrade Cisco Unified Communications Manager , IM and Presence Service , Cisco Expressway, Cisco Jabber, and Cisco Webex as soon as possible. Failure to upgrade on time will result in loss of voice notification for Cisco Webex users using Unified Communications Manager and IM notifications for Cisco Jabber and Cisco Webex iOS users.
If Apple Push Notification Service (APNS) is enabled on the CUCM/IM and Presence clusters and if the Expressway is upgraded to a version that supports Push:3 protocol, first upgrade all CUCM/IM and Presence clusters to the version that supports push:3 protocol.
This means that if your existing CUCM/IM and Presence version is 11.5(1)SU8 or 12.5(1)SU3 or below (that supports Push:2), however you have upgraded the Expressway to 12.7 (that supports Push:3), the APNS will not work in such deployment scenario. In such case, you must upgrade your CUCM/IM and Presence cluster to a version that supports Push:3, such as 11.5(1)SU9.
Apple Push Notification Service needs HTTPS and will not work with unrestricted software.
For up to date support information that is related to Push Notifications with iOS13 and above versions, including upgrade requirements, refer to Apple Push Notification Service Updates.