Centralized multisite configuration

In the centralized model, Session Manager controls Communications Manager or telephony servers at all locations. The centralized configuration is a good option if you have multiple sites and sites with fewer users than the capacity of a single application server. See the following illustration for an example. You might have 8,000 users at your Atlanta site and 2,000 users at the Boston site. If you have the telephony infrastructure in place in Boston, you can get Atlanta to handle the Boston traffic also and maximize the capacity of your servers.

Similarly, if you have many small offices with a few hundred or a thousand users at each location, each requiring only a fraction of a server, you might require fewer servers than you require for a distributed configuration. By optimum utilization of the application servers, a centralized configuration lowers your total cost of ownership (TCO). The trade-off is you have more voice traffic on WAN and no local survivability.

The image shows an example of a centralized multiple site configuration when a third-party message store is used. This configuration shows two sites: Atlanta and Boston. At site Atlanta, a cluster of application server communicates with the telephony server through Session Manager and to the third-party message storage server through AxC/Directory server.. The telephony server at site Boston communicates with the Session Manager located at site Atlanta.