How can you reduce cost and improve productivity when your organization spans the globe, has an assortment of manufacturers telephone switches, has need for a federation of multiple distributed and redundant unified messaging systems, which need to operate independent of each-other yet also must act in concert with each-other, such that a User can send a voice or fax message to anyone anywhere within the organization as if they were all on the same local system?
In this example, we’ll show how a combination of Callegra.UC technologies that can answer this broad question.
In the graphic above, direct your attention to Callegra.UC DataCenter Node 1 in the top left. In this example, there are two locations connected to a single Callegra.UC DataCenter database through the use of Scalable and Multi PBX/VoIP Integrations with two Callegra.UC Telephony Services servers. These two Base PBX systems could be located in the same building, separate buildings, or even separate locations. They may have the same or different telephone switches and different telephone handsets as well.
Direct your attention to Callegra.UC DataCenter Node 2 in the bottom left.
This site is similar in needs to Node 1, except that at the first location, they have more simultaneous Users than can be facilitated through a single Callegra.UC Telephony Services server. To provide scale at this location, Callegra.UC’s distributed architecture is utilized to facilitate the larger User population by adding another Callegra.UC Telephony Services server into the configuration with all integrated to the same PBX. This example demonstrates how Scalable and Multi PBX/VoIP Integrations can serve multiple locations at the same site and also spread across a combination of sites.
Direct your attention to Callegra.UC DataCenter Node 5 in the bottom right.
At this location, real-time redundancy of information is mission critical. To facilitate this, we add in CallegraRECOVERY to synchronize data to a standby DataCenter server in the case that a hardware failure or other disaster strikes the primary DataCenter node. This warm site CallegraRECOVERY server could be at the same location, or located on a different continent.
Direct your attention to Callegra.UC DataCenter Nodes 3 & 4 in the top right.
This location expands the capabilities shown in node 5 by having each Callegra.UC DataCenter node replicate data in real time through CallegraRECOVERY to the other CallegraRECOVERY DataCenter server that is also supporting its own Callegra.UC Telephony Services servers. In this example, if disaster strikes at Node 3, Node 4 can assume all of the functions assigned to the primary Callegra.UC system at Node 3. This example improves scale while also leveraging the fullest potential of each Callegra.UC DataCenter server.
In the center of the graphic above, notice the Global Messaging Network, which facilitates the information transport associated with the CallegraCOMMUNITY Global Address Book.
The above configurations represent key capabilities of CallegraCOMMUNITY that enables these 4 distinct Callegra.UC DataCenter databases to be unified into one global messaging network. The CallegraCOMMUNITY Global Address Book receives information from each of the distinct Callegra.UC DataCenter databases and informs each Callegra.UC system at each site how it can connect to its peers in the federated network. These sites may be located in different physical locations or even located in large scale mobile facilities.
The above example reflects the extreme scalability, flexibility, and redundancy of Callegra.UC’s distributed architecture. It demonstrates how a combination of offerings from Callware can be deployed to overcome, leverage, and unify a wide assortment of existing technology across an organizational footprint that may span the globe.