Deploying and configuring Avaya Breeze® platform

Last Updated : Jan 13, 2023 |
Use the following procedure to deploy and configure Avaya Breeze® platform.
Note:
For every Avaya Breeze® platform server running Avaya Device Adapter Snap-in, an additional SIP Entity of the Endpoint Concentrator type must be defined. A number of Entity links between the SIP Entity and one or more Avaya Aura® Session Managers must also be defined. The Entity links must have a Connection Policy set to Endpoint Concentrator. An Avaya Aura® Session Manager Communication Profile must also be defined for every user or endpoint.
  1. Install and configure the required number of Avaya Breeze® platform servers.
    ADDITIONAL INFORMATION:
    Note:
    See the Deploying Avaya Breeze® platform and Administering Avaya Breeze® platform guides for information and procedures related to this task.
  2. Set the disk size of each server to 100GB or greater.
    ADDITIONAL INFORMATION:
    Note:
    See Avaya Breeze platform hardware requirements for additional server information.
  3. Configure SIP entities and Entity Links for all servers as per Avaya Breeze® platform deployment requirements.
    ADDITIONAL INFORMATION:
    Note:
    If you intend to deploy the Breeze server in a single node cluster, consider using the previous CS 1000 Node IP as the value of the IP Address field of the SIP Entity. This will enable performing a migration that will move all endpoints in one step. Do not do this if you are performing a phased migration or if you are deploying a multi-node cluster.
    Note:
    See Deploying Avaya Breeze® platform for information and procedures related to this task.
  4. Configure additional SIP entity and Entity Links for all servers as per Device Adapter deployment requirements.
    ADDITIONAL INFORMATION:
    Note:
    See Configuring additional SIP Entity and Entity Links for Avaya Breeze platform servers running Avaya Device Adapter Snap-in.
  5. Select Elements Avaya Breeze Server Administration New to configure the required number of Avaya Breeze® platform servers. Use the previously administered SIP entities.
  6. Configure an Avaya Breeze® platform cluster.
    1. Use the procedure Configuring a single node Avaya Breeze platform cluster to configure a single node cluster or Configuring a multiple node Avaya Breeze platform cluster to configure a multiple node cluster.
    2. Ensure the cluster is in Deny Service mode.
      ADDITIONAL INFORMATION:
      Note:
      The Deny Service mode should not allow new registration and should not affect available registered IP sets and MGCs (For example, the IP set stays functional on S1 and does not get registered to S2 or any other alternative).
      New registration or IP set/MGC reboot while Avaya Breeze® is in deny service triggers registration to S2.
  7. Load and apply Avaya Device Adapter Snap-in using the information and procedures in the Snap-in deployment checklist.
  8. Configure Avaya Device Adapter Snap-in service attributes with the information in Service attributes.
  9. Configure PPM for Personal Directory data.
    ADDITIONAL INFORMATION:
    Note:
    See the Maintaining and Troubleshooting Avaya Breeze® platform guide for information and procedures related to this task.
Related links
Supported TDM hardwareFiber Remote IPE and Carrier Remote IPE