Migrate from legacy FCM APIs to HTTP v1 for Android Push Notifications

As announced by Google, support for the legacy push method will cease in June 2024.

PortSIP released the v16.4. version to support the new push method for Android notifications. All PortSIP PBX v16.x installations need to upgrade to v16.4 and change settings to ensure the new push notifications work correctly.

If you installed the PortSIP PBX v12.x, please reference this guide: Upgrade PortSIP PBX v12.x to v12.8.7.

Please follow the below steps to update the push settings with PortSIP PBX v16.4.0.

Upgrading PortSIP PBX

Please upgrade your current PBX v16.x to v16.4 per this guide: Upgrading PortSIP PBX to New Versions.

Changing Push Settings for Android

If you’re using the PortSIP softphone app, no action is required on your part. The upgraded PBX v16.4.0 will seamlessly integrate with the PortSIP softphone app.

Obtaining a New Push Profile JSON File

  • If you’re using an Android app that PortSIP has rebranded for you, please contact us to receive the new push setting JSON file.

  • If you’re using an Android app that you’ve developed yourself, follow the steps below to obtain the new push setting JSON file. Refer to the Android Push Notifications guide and follow steps 1 through 3 (no need to follow the other steps) to download the push setting JSON file.

For the purposes of this guide, let’s assume the push setting JSON file is: prie-ffae0-c58bc735da.json.

Adjusting Settings

  • Sign in to the PortSIP PBX v16.4.0 Web portal, select the menu Advanced > Mobile Push, and double-click your app to change the settings.

  • Open the Push Profile JSON file prie-ffae0-c58bc735da.json by the text editor for example Windows Notepad, copy all of the contents and paste to the FCM Service account key JSON file and save your changes.

Please reference the below screenshot.

Last updated