Administrator's Guide

6-44
Cisco Unified Attendant Console Administration and Installation Guide
OL-27293-02
Chapter 6 Configuring and Licensing Cisco Unified Attendant Console Advanced Server
User Configuration Menu
Step 3 Click the appropriate check boxes on the left or use the Select All (on page) or Select All In Search
(including any other pages of results) to select the template(s) to delete.
Step 4 Click Delete Selected.
Editing Out of Hours Routing Templates
To edit an out of hours routing template, do the following:
Step 1 Choose User Configuration > Templates > Out of Hours Routing.
The Out of Hours Routing Template page appears.
Step 2 If necessary, Find the template(s) to edit.
Step 3 Click Select next to the template to edit.
Step 4 If you want to change the name of the template, under General, type the new Template name, and then
click Update.
Step 5 Do the following as required:
• To add a new time period configuration (Specific Dates or Days of the Week) follow the instructions
in Creating Out of Hours Routing Templates From Scratch, page 6-41.
• To edit an existing time period configuration, click Select alongside, change the configuration, and
then click Save.
• To remove time period configurations from your template, select the corresponding check boxes on
the left, and then click Delete Selected.
Cisco Unified Replication
Cisco Unified Attendant Console Advanced server resilience is partly provided by server replication. For
more information on resilience, see Server Resilience, page 1-2.
Cisco Unified Attendant Console Advanced contains two databases:
• Configuration database—contains all user configurations and the contacts directory
• Logging database—responsible for logging
The Configuration database is synchronized between the Publisher and Subscriber server using SQL
Server replication and the synchronization of database objects across multiple database servers. The
configuration database can be updated only on the Publisher server. The copy on the Subscriber server
is read-only.
The Logging database is synchronized between Publisher and Subscriber using Microsoft DTC. Log
information is replicated both ways between the SQL databases on the servers, with the log on each
containing a full record of call transactions on both servers. The copy on the Subscriber server allows
limited adding, amending and deleting of user/call-related real-time activities when the Publisher
logging database is unavailable.