Given that Workgroups is not a distributed service, if the HQ server goes down, you will not have Workgroups anyway. Horus factsĪdditionally, the Personal Call Managers will not work for any extensions on switches managed by the down server. This means you will have no functioning Workgroup Agents and not ability to monitor those Agents. We need to remember that if a server goes down, the switches managed by that server will lose all the TAPI information for the phones that it controls. It makes sense to put the users at a remote site on the DVM at that site, but does it really make sense to have the switches at that site managed by the DVM at that site? This usually provokes a heady discussion, but here is our reasoning. If you lose the HQ server, you will lose these services for all sites, even if they have a DVM installed at that site! As it relates to low cost business continuity options, we like to install a DVM at the HQ site, but we want all switches at all sites to be managed by the HQ server. These services are known as Workgroups, Route Points and Account codes. Does it have any impact on resiliency not redundancy as it relates to business continuity in the event of server failures? Installing a DVM at the same level, or in the same site as the HQ server, provides a high degree of resiliency at comparatively low cost.
What exactly is the value of a Distributed Voice Mail Server e.
