Synchronization with Enterprise Survivable Server

Last Updated : Apr 04, 2024 |

Avaya Aura® Communication Manager provides Enterprise Survivable Server (ESS) and Local Survivable Processor (LSP) for failover from the main media server. ESS and LSP provide the ability for media gateways, endpoints, application servers and their applications to continue their operations without major interruption.

To enable synchronization with ESS, replace the main Communication Manager IP address with the ESS Host IP address in the Host Name or IP Address field while configuring the Avaya Communication Manager element in the Application Center Administration Element Inventory. The ESS configuration ensures that if the main Communication Manager server goes down, full manual synchronization continues from ESS.

To enable synchronization when there is a failover to ESS, you can use the following options to configure the ESS details in Application Center Administration on the Avaya Communication Manager element page:

  • Retain the main Communication Manager IP address in the Host Name or IP Address field and configure the ESS Host IP address in the Alias Host Name Or IP Address field if the Communication Manager settings on the System Manager administration portal has the main Communication Manager IP address configured in the Host Name or IP Address field.

  • Replace the main Communication Manager IP address with the ESS Host IP address in the Host Name or IP Address field if the Communication Manager settings on the System Manager administration portal has the ESS Host IP address configured in the Host Name or IP Address field.

When Communication Manager goes down, ESS receives the translations, synchronized in Application Center Administration using full manual synchronization. As the history of the actions performed on the main Communication Manager server is not synchronized to ESS, automated incremental synchronization happens only for the actions performed on ESS. The translations from ESS are not synchronized back to the main Communication Manager server. When the main Communication Manager server comes up, full manual synchronization of the main Communication Manager server deletes the users added to ESS, which was synchronized in Application Center Administration.

When Communication Manager goes down because of unplanned events, ESS stops receiving any translations after the last automated incremental synchronization from Communication Manager. Subsequently, these recent translations do not synchronize in Application Center Administration using full manual synchronization or automated incremental synchronization from ESS.