Edge redundancy


Genesys recommends that you deploy Edges in an N+1 configuration, where N is the number of Edges required to meet the expected maximum concurrent call load. This N+1 configuration ensures that you are able to place and receive both ACD and non-ACD calls if the active Edge fails or goes offline for routine maintenance.

In an N+1 configuration, managed phones register with both a primary and a secondary Edge. To spread out the load, PureCloud randomizes each phone’s assignment of a primary and secondary Edge between the available Edges.

For example, suppose that you have two Edges and 10 phones. If so, then PureCloud randomizes each phone’s primary and secondary registration between the two Edges, as illustrated in this diagram. In this case, each Edge has five primary registrations and five secondary registrations. 

If the primary Edge is unreachable or offline, the phone switches to the secondary Edge to place and receive calls. The switch between the primary and secondary occurs almost immediately. However, it can take up to 15 seconds to place or receive calls with the PureCloud user interface. This small time lag is due to the timing window required for the Edge-to-cloud heartbeat messages to resume.

To function correctly, Edge redundancy requires that you only combine Edges in a site that have a similar call capacity. For more information, see Concurrent call capacity for Edge models.

  • You can combine any of the Edge Standards (v1, v2, and v3) with each other. 
  • You can only combine the Edge Micro with other Edge Micros.
  • You can only combine the Edge Mini with other Edge Minis.

This diagram shows the acceptable and well as unacceptable combinations. 

Note: This diagram shows three Edges in each site only for illustrative purposes. Edge redundancy only requires two Edges to function correctly.