THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Affected Software Product | Affected Release | Affected Release Number | Comments |
---|---|---|---|
Unified Communications Manager | 11 | 11.5(1) | All versions |
Unified Communications Manager IM & Presence Service | 11 | 11.5(1) | All versions |
Unified Communications Manager | 12 | 12.5(1) | All versions |
Unified Communications Manager IM & Presence Service | 12 | 12.5(1) | All versions |
Unified Communications Manager | 14 | 14 | All versions |
Unified Communications Manager IM & Presence Service | 14 | 14 | All versions |
Unified Communications Manager | 15 | 15 | All versions |
Unified Communications Manager IM & Presence Service | 15 | 15 | All versions |
Defect ID | Headline |
CSCwi16238 | Push notifications will not work due to an IP address change with the Cisco Push REST service |
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:
This issue is due to the migration of the data center that hosts the Cisco-hosted Push REST service.
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 the client 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.
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.
Solution
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. For customers who use this recommended method of configuration, no action is necessary.
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 IP address requirements, 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.
Version | Description | Section | Date |
1.0 | Initial Release | — | 2023-DEC-19 |
For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:
To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications
Unleash the Power of TAC's Virtual Assistance