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.
When a cluster is enabled for push notifications, Cisco Unified CM and Cisco Unified Communication IM&P use the Cisco Push REST service in the Cisco cloud to send push notifications to either the Apple Push Notification Service (APNS) or the Google Firebase Cloud Messaging (FCM) Push Notification service, which send push notifications to compatible Cisco Jabber (for messaging and calling) or Cisco Webex App clients (for calling) that run on Apple iOS or Android devices. Push notifications allow the system to communicate with the client, even after it has entered into background mode (also known as suspended mode). On March 29, 2024, Cisco will migrate the Cisco Push REST service from one data center to another.
Cisco customers who use Cisco Unified Communications Manager (Unified CM) or Cisco Unified Communication IM & Presence Service (IM&P) to manage push notifications may experience a failure of push notifications on or after March 29, 2024, for the following clients:
● Cisco Jabber
● Cisco Webex applications
● Apple Push Notifications Service (APNS)
● Google Firebase Cloud Messaging (FCM)
This issue is due to the migration of the data center hosting the Cisco Push REST service.
The recommended method of configuration is as stated in Push Notifications Prerequisites to add fos-a.wbx2.com, push.webexconnect.com, and idbroker.webex.com to the SSL Decryption Exclusion list in the firewall.
There is no action necessary for customers who use the above recommended method of configuration.
For customers who have configured IP address in their Firewall ACL it is recommended to use the Fully Qualified Domain Name (FQDN) as stated above.
For customers who have stringent firewall policies that are based on the IP address requirements, please contact Cisco Technical Assistance Center (TAC) before March 29, 2024, which is the production cutover date.
For more information, see the Push Notifications (On-Premises Deployments) chapter of the Push Notifications Deployment Guide
Push notifications that are sent from Cisco Unified CM and Cisco Unified Communication IM&P may fail to reach Cisco Jabber as well as Cisco Webex Application for Apple iOS and Android mobile clients on or after March 29, 2024.
For further assistance or for more information about this Service Bulletin, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:
● Open a service request on Cisco.com