Administration operations requiring manual synchronization

Last Updated : Mar 19, 2024 |
Prolog information
You cannot synchronize the following operations between the two CMS servers using the backup and restore process. Instead, you must do these operations manually on each CMS server.

Agent administration

  • Agent trace administration
  • Activate agent trace

Administration (other)

  • Agent exceptions
  • Split/Skill exceptions
  • Trunk group exceptions
  • VDN exceptions
  • Vector exceptions

UNIX administration

  • Administering passwords

Scripting and Timetables

  • Create Supervisor scripts (from a supervisor login)
  • Scheduling of time tables
Note:
The timetable window includes the following run options:
This timetable will run on this or another CMS server
< > Run only on this CMS server*
< > Run on this or another CMS server*
In some cases, running timetables on both servers is not desirable. For example, when a timetable specifies printing of very large reports, running the timetables on both servers would result in duplicate printings. If an administered timetable should be run only on the current server, select the Run only on this CMS server* option. However, be aware that any timetables set up to run only on the primary server must be manually revised before they will run on the secondary server.

System setup

  • Changing the CMS state
  • Data storage allocation
  • External application state
  • External Call History state
  • Load Pseudo ACD data
  • Pseudo ACD setup
  • Storage intervals
  • Turning data collection on and off

Maintenance

  • Data summarizing
  • Call center administration
  • Call work codes

User permissions

  • Removing CMS users

Call center administration

  • VDN Call Profile
  • Call Work Codes
  • Split/Skill Call Profile