Knowledgebase
DrVoIP Support > DrVoIP Network, VoIP, Security & AWS Cloud! > Knowledgebase

Communicator points to HQ or DVM? Best Practice

Solution Our Best Practice recommendation is to always point the Communicator client to the Headquarters server. Then the first time the clients connect they will be automatically redirected to their “Home Server”, which is the server that manages the switch that manages their user extension. Communicator will cache that server’s IP/name and use it to connect directly for future logins, if the server is available. Let me try a simple diagram: HQ Site with HQ-Server HQ-Switch1 HQ Phones -London Site with London-DVS Lndn-Switch1 Lndn Phones -Tokyo Site with Tokyo-DVS Tkyo-Switch1 Tkyo Phones Every rational installer will have the HQ Switches managed by the HQ-Server, and the London switches managed by the London-DVS, and the Tokyo switches managed by the Tokyo-DVS. Thus, the Home Server for the users at each location to be their local server. Having said all that, THE REASON we recommend entering the HQ server’s IP or FQDN in the Communicator startup wizard is that it adds a measure of redundancy and recoverability to the users in the event of a server outage. Let’s look at some cases where different servers go down for whatever reason. (I’m assuming here that the WAN connection is still good, only the server is down.) If HQ –Server is out of service: All of the London and Tokyo users will continue to connect and login to their local servers. There will still be some functional impact, especially if the clients can’t reach the Database, but if there are local trunks available the users will still have Communicator available for many operations. If London-DVS is out of service: The London users will try to access their down local London server first, but if they were “pointed” to the HQ server during setup, they will soon give up and try to reach HQ to see if there is a change to their Home Server. At first the HQ server will try to redirect them back to London-DVS, their home server. However at this point the Administrator, seeing that his London-DVS is down, can go into Director and re-assign the Lndn-Switch1 to be managed by either the HQ-Server or the Tokyo-DVS. This changes the Home Server assignment for all those Londoners, so they will authenticate CMWin via their new server and go on their merry way. For users that are pointed to the London-DVS, the Admin will have to manually go into each Communicator’s Telephony settings and change the server destination to HQ, one workstation at a time. As you can see, it’s not a huge benefit, but it does allow the Administrator to better manage the system from a central point in the event of a prolonged failure, rather than have to visit each workstation or ask the end users to make the change themselves.
 
Was this article helpful? yes / no
Article details
Article ID: 42
Category: ShoreTel
Rating (Votes): Article rated 3.0/5.0 (18)

 
« Go back