SIP HA is possible with Avaya Breeze® platform by administering a cluster of Avaya Breeze® platform servers and connecting each member of the cluster to each Session Manager. You can then route users of a service to the cluster rather than to a specific Avaya Breeze® platform server so it is likely that at least one will be available.

When you administer an Avaya Breeze® platform cluster, each Avaya Breeze® platform server is entered in a table of local host names, along with a priority and weight for each.

When the cluster database is enabled with three or more servers, assign weights to servers for load balancing in the recommended percentages.

The cluster load balancer is only used for HTTP, not for SIP. Session Manager acts as the load balancer for SIP traffic. To enable Session Manager to fulfill this function, an FQDN must be populated in the Local Host Name Resolution table, and each Avaya Breeze® platform security IP address must be associated with this FQDN. This FQDN must be used when creating the FQDN SIP entity.