Configuring the Avaya push notification provider on Avaya Aura Session Manager

Last Updated : Mar 17, 2025 |

About this task

In this task, you generate authorization data and export this data to your Avaya Cloud account to use the Avaya Push Notification provider. You cannot edit other configuration data, such as the name or address of the Avaya Push Notification provider.

Before you begin

  • Create and configure an Avaya Cloud account.

  • Install the public certificate of the push notification provider on Session Manager. For more information, see Configuring the use of CA certificates for Avaya push notifications provider.

  • Ensure that all core Session Manager instances are on software release 8.1.3 or later.

  • From R10.2.1.1 and later, Avaya recommends using the HTTP Proxy Configuration page instead of the Global Settings Page to configure the HTTP proxies. Configuration values from the HTTP Proxy Configuration page override the values of the Global Settings page.

  • To use forward proxy configuration, ensure the HTTPS Proxy Host and HTTPS Proxy port fields are configured on the Global Settings page.

Procedure

  1. On the System Manager web console, click Elements > Session Manager > Network Configuration > Push Notification > Notification Provider.
  2. Select the check box corresponding to the Avaya Provider in the Provider Name column and click Edit.
  3. In Company Domain, enter your company domain.

    Enter the same company domain provided in your Avaya Cloud account.

  4. Optional Select the Use Forward Proxy option to use the forward proxy configuration for push notifications.
  5. Click Generate Keys.

    The Session Manager generates a public and private key pair and an identifier. This data is required to authorize Avaya Aura® Session Manager on the push notification provider. The Session Manager also updates the following values:

    • System Id: A unique identifier for your system.

    • Public Key: A public key.

    • Key to Export: Authorization key in JSON format for your Avaya Cloud account.

    Important:

    • Do not close the Provider Settings page on the System Manager administration portal until you finish exporting authorization data to your Avaya Cloud account.

    • Do not save the data you provided on the Provider Settings page of the System Manager administration portal until you export authorization data to your Avaya Cloud account. Otherwise, the push notification service might not work as expected.

  6. Copy the authorization data, including the surrounding curly brackets, and save it in a file on your computer.
  7. In a new browser tab, log in to your Avaya Cloud account and navigate to Manage Companies.
  8. Select the required company and navigate to the Apps tab.
  9. From App, select Avaya Mobile Push Notification Service.
  10. In Data Configuration, select the JSON check box.
  11. Replace the content in Public Settings with the content of the file created in step 5 and save your changes.

    Ensure that the authorization data you enter in Public Settings is a valid JSON formatted key. If the data uses an invalid format, the Avaya Cloud account displays a warning message, but still allows you to save changes.

    The Avaya Cloud account stores authorization data internally. Public Settings only displays the previously provisioned authorization data. You do not lose any previously entered authorization data if you overwrite existing content with the new authorization data.

  12. Return to the Provider Settings page on the System Manager administration portal.
  13. Select the Session Manager from the Session Manager to Verify Settings list, to test the notification provider connection.
  14. Click Verify Settings to verify that Session Manager can connect and authenticate with the push notification provider.
  15. Do one of the following:

    • If the verification is successful, click Commit.

    • If the verification fails, fix the issue as described in Avaya Aura® Session Manager cannot connect to a push notification provider section of Troubleshooting Avaya Aura® Session Manager and re-run the connectivity test.

      If the problem persists, contact Avaya support personnel.

Example

The following is an example of the authorization key that you export to the Avaya Cloud account:

{
	"systemId": "9bf8f4ab-99b1-452b-9b7f-e75aacf31d19.mycompany.com",
	"publicKey": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE9rtz4fuYhGm2JlvnI6lZmate8eEX\na4wvmklSdHGYZHos7y8xNBNCEj9wc3klayOKHYIVIeL0ryVFgM16Ud5FDQ==\n-----END PUBLIC KEY-----",
	"alg": "ES256"
	"description": "Avaya Aura Session Manager",
}
Related information
Registering an Avaya Cloud account