Resilience using Avaya Communicator

[spooktheblackcat]

Hi All,

We have a customer with a Primary and Secondary server onsite. They require full resilience should any failures occur. Most of their handsets are Jxxx models which fail over and restore with no issues. They have a Call Centre team of around 40 users who use only Communicator. During failover testing they register fine with the Secondary server and restore OK when the Primary is reconnected. Where the issue occurs is when the system is failed over and a Call Centre user tries to log in with Communicator. Because only the Primary server is listed within the settings of these users, it cannot register.
Is there any way round this other than manually altering the server settings within Communicator to the Secondary server IP?
Or is there a way to enter more than one server on Communicator?
Cheers

 

[biv343]

I don't know that it's possible with Communicator (maybe via FQDN but I haven't tried it), but it is supposed to be supported with Avaya Workplace. That said, I've never tried it in the scenario you describe with the primary completely offline at time of registration.

Page 44 of the below:

https://ipofficekb.avaya.com/busine...stall/IP Office Resilience Overview_en-us.pdf

For all Avaya Vantage™ and Avaya Workplace Client, the address supplied for the failover server
will either be the failover system's FQDN or it's IP address.
• If the failover server FQDN address System > LAN > VoIP is set, that address is provided to
the clients as the failover address. This requires that the failover server's FQDN is resolvable
through the customer's network back to the IP address of the system in order for resiliency to
work.
• If the failover FQDN is not set, then the system's IP address is provided to the clients as their
failover server address.