Use your WAN not the Carrier for your Remote Site

Replace your Carrier Remote or Mini Carrier Remote with an Avaya Survivable Media Gateway (SMG). The SMG connects to your main PBX through the corporate WAN. Furthermore, the SMG will operate in survival mode during a WAN failure. During a network failure, the SMG will support phone operation by engaging its own CPU. This is something your Carrier Remote cannot do. In addition, the SMG is IP based which means it will register with your main-site PBX. Therefore, if you are paying a T1 carrier in order to support your Carrier Remote or Mini Carrier Remote Cabinet, upgrade your main site to Avaya release 7.6 and install a Survivable Media Gateway.

“Survivable Media Gateway enhances the reliability of Avaya Communication Server 1000E (Avaya CS 1000E) systems by allowing the provisioning of up to 50 geographically remote Secondary Call Servers to a Primary Call Server. You can configure each Secondary Call Server as Alternate Call Server 1 or Alternate Call Server 2 for the devices assigned to it. Survivable Media Gateway provides two levels of redundancy. If the Primary Call Server fails, local and remote resources register with the Secondary Call Server configured as Alternate Call Server 1. If the Primary and Secondary Call Servers both fail, or the WAN fails, local resources register with the Secondary Call Server that is installed at the local site and configured as Alternate Call Server 2.”

Reference: NN43001-507_06_01_System_Redundancy_Fundamentals



Enabling AACC Shadowing After 24 Hours

If your standby server has been out of synchronization for more than 24 hours, you will need to complete the following process to restart AACC 6.4 shadowing. Otherwise, the standby server will fail to synchronize with the active AACC server. Execute one restore at a time; i.e. ADMIN, CCMS, and CCT.

The procedure listed below avoids corrupting the standby server’s Backup Locations Directory by restoring one database at a time:

  • Make sure you have a recent backup from your active server; preferable located somewhere off the active and standby servers.
  • Map the active AACC server backup database folder onto the standby server.
  • On the active AACC server, run a full database backup.
  • Copy the UNC backup path on the active server into the standby server’s restore UNC path (\\Computer Name (or IP address) \ Backup Location).
  • Navigate to the standby server’s Database Utility / Database Maintenance window.*** Do not attempt to restore all three “ADMIN, CCMS, and CCT databases at the same time. This can cause corruption within the standby server’s Backup Locations directory. ***
  • Restore the standby server by first running the ADMIN database only.
  • Once the ADMIN restore is complete, verify the UNC path is correct. Adjust as necessary.
  • Restore the CCMS database. Note: the CCMS database is the largest out of three restores.
  • *** The CCMS database will restore the active server’s AACC name and IP information into your standby server. However, it will not change the actual IP address in the standby server’s network properties located in the control panel. ***
  • Open the standby server’s “Server Configuration” window located in Manger Server.
  • Adjust the standby server’s local settings to the correct name and IP addressing. *** Do Not Restart the Standby Server. ***
  • Click on the Licensing tab to correct the location of your license file on the standby server. . *** Do Not Restart the Standby Server. ***
  • Finally yet importantly, run the CCT database restore on the standby server.
  • Do not restart server.

You can now open the High Availability window on the standby server, double click System Control, select Shadowing, click start, and save. The log file will now show actively shadowing from the active server. You will notice a continuous flash on both servers if your server’s NIC cards contain LED lights.

Reference: Aura Contact Center




If additional assistance is required, please call 301.873.0080 or email at