Session Manager can be used to achieve geo-redundancy for SIP signaling across Avaya Breeze® platform clusters. Similarly, an external HTTP load balancer or Application Gateway can be used. Multiple Avaya Breeze® platform clusters are configured exactly the same and deployed in different regions. An FQDN is defined for each region. The external load balancer is configured with both of these FQDNs. Each FQDN includes the cluster IP address for both Breeze clusters, but in a different preferential order. Each FQDN prefers the local cluster’s IP address, with the other cluster’s IP address being the second choice.

Browsers or other clients that access Avaya Breeze® platform HTTP services can use the FQDN associated with their local Avaya Breeze® platform cluster. When the load balancer receives this request, the load balancer routes the request to the local Avaya Breeze® platform cluster if available. If the local cluster is not available, the load balancer routes to the remote cluster. In either case, the local Avaya Breeze® platform load balancer distributes the request to one of the Avaya Breeze® platform machines in the cluster.

Some Avaya Breeze® platform snap-ins use a Avaya Breeze® platform-specific affinity mechanism that is not supported by external load balancers. Therefore, this configuration is not a supported configuration to use an external HTTP load balancer to distribute HTTP requests to individual Avaya Breeze® platform servers in the cluster as opposed to addressing the cluster IP address.