Deployment details for Messaging overview

Last Updated : Feb 17, 2026 |

Before commencing the installation process for Messaging, you must first have the following details:

Cloud Provider

A cloud provider account must be created for each customer to enable the delivery of messages to or from the end-user device. It acts as a gateway for messaging events.

The Avaya DevOps team provisions the cloud provider account with the following information:

  • App ID

  • Cloud Provider Key

  • Cloud Security Key (Secret)

Avaya Oceana® details

You must have the following details specific to Avaya Oceana®:

  • FQDN/IP address of Avaya Oceana® Cluster 3 where CustomerControllerService is installed

  • System Manager Certificate Authority (CA)

  • Avaya Oceana® Cluster Identity Certificate

  • Credentials of a valid Avaya Breeze® user for file transfer

Avaya Common Services (Common Services) Cluster

Messaging is installed on the Avaya Common Services cluster. When you install Common Services, it creates and FQDN/IP address for inbound traffic into the cluster. You must obtain this FQDN/IP address to allow the cloud provider to send customer Messaging requests to the Async tool and Avaya Oceana®, so that the requests can be replied.

Based on your hardware configuration, you might also have an external load balancer that maps to the FQDN/IP address.

Note:

This Messaging deployment is applicable for customers who deploy Avaya Analytics™ and Messaging on the same platform. This deployment does not apply to the non-HA/Lab deployment of Avaya Analytics™.