I think we need a bit more information regarding the overall setup.
You refer to a "PBX" in relation to the location a couple of times. Do you really mean a PBX that sits in a location, and is integrated with PureCloud, or are you thinking of the Edge as a PBX (which is not a good analogy, as PureCloud overall is the PBX in the cloud, as it were)?
Agent status is stored/tracked/updated in the cloud, so the Edges need an Internet connection to PureCloud to be fully functional (otherwise they run on cached information for menus and Architect flows, ACD routing), but they have no knowledge of current agent status when disconnected from the cloud.
Do you have multiple Edge Groups and a single Organization? What is the overall architecture? (Or, are you trying to figure out what to design for a new deployment/implementation?)
------------------------------
George Ganahl
Principal Program Manager
Genesys
------------------------------
Original Message:
Sent: 10-18-2018 09:08
From: Mike Pigeon
Subject: Architecture for "follow-the-sun" support
Could you please help me understand how follow-the-Sun works with PureCloud? See questions below
- With follow the sun for a global deployment with distributed Edge servers, the edge servers need a network connection between each other to be aware of agent availability(?)
- If a call gets redirected from one location to the other (ie if after hours in the UK and the call goes to an available agent in the US), this requires a routing the call to the US pbx – is this a sip redirect or is there a connection nailed up between the ingress edge/pbx and the destination pbx/edge?
------------------------------
Mike Pigeon
------------------------------