Field Notice: FN - 72036 - Apple Push Notification Service Update - Software Upgrade Recommended

Notice

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.

Revision History

Revision	Publish Date	Comments
1.0	08-Feb-21	Initial Release

Products Affected

Affected OS Type	Affected Software Product	Affected Release	Affected Release Number	Comments
NON-IOS	Application Patches	22.0	22.0.2020.08, 22.0.2020.09, 22.0.2020.10
NON-IOS	Application Patches	23.0	23.0.2020.08, 23.0.2020.09, 23.0.2020.10

Defect Information

Defect ID	Headline
CSCvf34445	There were no defects filed with this field notice at the time of publication.

Problem Description

Apple introduced the HTTP/2 interface to the Apple Push Notification service (APNs) as a replacement of the previous binary APNs interface.

BroadSoft implemented support in Notification Push Server (NPS) for the HTTP/2 interface in 2017 and published the migration steps in the Feature Description document.

Apple announced that the legacy binary interface to APNs will not be supported after 2021-03-31. See Updated APNs provider API deadline for more information.

In order to comply with this requirement, all service providers must ensure that the NPS used to send push notifications to iOS devices using APNs is updated with the latest patches and is configured to use the new HTTP/2 interface for APNs to avoid service outage.

This configuration needs to be implemented before 2021-04-01.

Background

Note: This field notice was originally posted in the BroadSoft Xchange portal and has been moved over to Cisco.com as-is for historical purposes.

Problem Symptom

Failure to migrate to the new Apple HTTP/2 interface will result in incoming calls and message failures for all client iOS devices.

Workaround/Solution

BroadWorks patches can now be downloaded through the Cisco Software Download Center after logging in with your Cisco.com (CCO) account.

The version of BroadWorks that is currently deployed as well as the patches currently activated can be checked by executing the get versions all command from the CLI. More information on how to check the patch level can be found in the Cisco BroadWorks Maintenance Guide.

Workaround

N/A

Patch

In order to comply with these requirements, service providers need to ensure that they have deployed this NPS feature available for BroadWorks Release 22 and later:

• Add HTTP/2 Support to Notification Push Server for APNs

These are the feature patches:

• AP.platform.22.0.1123.ap354313
• AP.ps.22.0.1123.ap354313
• AP.ns.22.0.1123.ap354313
• AP.as.22.0.1123.ap354313
• AP.hzs.22.0.1123.ap354313
• AP.xsp.22.0.1123.ap354313
• AP.ems.22.0.1123.ap354313
• AP.nfm.22.0.1123.ap354313
• AP.ums.22.0.1123.ap354313

For BroadWorks Release 22 and later, the feature patches can be deployed on the existing NPS.

For BroadWorks Release 21, the service provider has two options:

• Upgrade BroadWorks to Release 22 or later.
• Deploy a dedicated Application Delivery Platform (ADP) server to host the NPS in the existing BroadWorks Release 21 deployment.

Note: Clients are not affected by this update, therefore no client update is required. This update is for NPS and APNs.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email or telephone

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.