PDF(13.8 KB) View with Adobe Reader on a variety of devices
ePub(86.1 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(73.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:March 31, 2021
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.
After March 31st 2021 the Notification Push Server (NPS) must use an HTTP/2 interface to communicate with the Apple Push Notification service (APNS). The HTTP/2 interface is available on BroadWorks Release 22.0 via the patch ap354313 and Release 23.0 supports only HTTP/2.
If running BroadWorks Release 22.0, HTTP/2 can be configured using the following instructions after applying ap354313. If upgrading to 23.0 or later the following steps will be needed to configure HTTP/2 for APNS.
You must be on 22.0+ or 23.0 XSP. A 22.0/23.0 XSP is compatible to run in parallel with an 21.sp1 stack if the XSP ONLY runs NPS and the AS is 21.sp1. See the BroadWorks Compatibility Matrix for more information.
You will need to know what clients are currently in use as the Auth Key ID, TeamID and Auth Key will be required to configure HTTP/2. The apps configured on 21.sp1 can be found here:
Any iOS apps Non-Cisco/BroadSoft apps must be configured to use the HTTP/2 APNS protocol.
Collaborate or SaaS BroadWorks apps need to be migrated too HTTP/2.
For SaaS clients, login to the BAM portal → Configuration → BroadWorks, scroll down to section: Notification Push Server, select the proper release in the drop-down, then follow the instructions.
For Connect Eval Clients open a ticket with TAC to request the Auth Keys, Auth Key ID, and TeamID. Note that the App Id, Auth Key Id and Team Id listed below are for the unbranded client, if using a branded client, this information will need to be obtained for your clients from Apple.
Required tokens for other clients can be obtained from the Apple Developer portal, see the Apple documentation here:
The above settings may need to be tuned for your specific system. The above example and following recommendations may provide a starting point.
The 'ConnectionPoolSize' is the number of concurrent connections NPS can make to APNS servers. This will help throughput of NPS and may not directly help timeout issues. The ConnectionPoolSize should be increased above 2, note that without ap377409 the NPS may not properly register a value above 2.
It is recommended to set the connectionTimeout to a value above 1000.
Configure the Auth Keys
_CLI/Applications/NotificationPushServer/APNS/AuthKey> add UTHPSAD667 Y2V5KSH586 /export/home/bwadmin/EVAL_Team-Y2V5KSH586-APNsAuthKey_ID-UTHPSAD667.p8
Auth Key Id Team Id Auth Key
64D9E5NY4S D775LZJG9V ******** <- SaaS
L44B3C998K 698ZB8543V ******** <- Connect Dev
UTHPSAD667 Y2V5KSH586 ******** <- Connect Eval
3 entry found.
Add Tokens for Production and Development Environments
_CLI/Applications/NotificationPushServer/APNS/Production/Tokens> add com.broadsoft.connect.eval authKeyId UTHPSAD667
App Id Auth Key Id
com.broadsoft.uc-one 64D9E5NY4S <- SaaS
com.broadsoft.connect.eval UTHPSAD667 <- Connect Eval
2 entries found.
Enable HTTP/2 if using XSP 22.0
XSP_CLI/Applications/NotificationPushServer/APNS/GeneralSettings> set HTTP2Enabled true
Note: If on 23.0 or ADP this step is not required as HTTP/2 cannot be disabled.
The response to the HTTP/2 POST is processed by the Notification Push Server. A response code of “200” from the APNs means that the notification was successfully received by the APNs and it will try to push the notification to the device. Detailed error messages are captured in the Notification Push Server logs.
If Apple returns an error code the Apple error codes can be found in the Apple documentation here:
Please note that ap354313 exists for platform as well as for the AS, EMS, HZS, PS, NS, NFM, UMS, and XSP in order to update Java to 8.0_102b, this is a requirement for the XSP on 22.0 to work with HTTP/2, it does not mean that the UMS must also be on 22.0.