Feedback

  • Contents
 

Configurations stored on the CCS

To configure Dialer settings using Interaction Administrator, Dialer Administrators logon to an Outbound Dialer Server. The administrator of any Outbound Dialer Server (ODS) can modify settings for other ODS servers managed by the Central Campaign server (CCS).

Interaction Dialer configurations (campaigns, schedules, rule sets, and so on) for each ODS are stored centrally on the CCS in an XML file named dialer_config.xml. Information in this file is updated when an administrator runs Interaction Dialer Manager and saves a configuration change.  The dialer_config.xml contains all of the campaign, time zone, policy, and rule configurations for all Outbound Dialer Servers coordinated by the CCS.

Dialer_config.xml is stored in a directory on the Central Campaign Server. The default path is C:\i3\ic\Server\Resources.

Do not manually edit dialer_config.xml. The Central Campaign server updates this file when Dialer configuration settings are modified in Interaction Administrator.  Outbound Dialers don't directly update the configuration file. Instead, they use Notifier Services connections to send configuration data to the Central Campaign server. The CCS watches for editing conflicts, and updates dialer_config.xml as needed. This allows configuration data to be updated by any Outbound Dialer server that is under control of the Central Campaign server.

As a best practice, backup dialer_config.xml frequently (daily if possible). This file contains critical configuration data that you might need to restore in an emergency.

Automatic backup of last loaded configuration

CampaignServer saves a backup copy of dialer_config.xml at startup, if it successfully loads configuration data from dialer_config.xml, it saves a backup copy of dialer_config.xml to a file named dialer_backup.xml. This backup contains the last good configuration, from the last time that the CampaignServer process was started. In the event that dialer_config.xml becomes corrupted (due to insufficient disk space, insufficient access rights, a power outage, and so on), an administrator can replace dialer_config.xml with the contents of the backup file.

To create the backup, the system first saves dialer_config.xml to a file named dialer_temp.xml. This ensures that enough disk space is available. Next, it deletes dialer_backup.xml and renames dialer_temp.xml to dialer_backup.xml. If any of these backup steps fail, the error is accurately traced and sent to the event log before CampaignServer exits. CampaignServer does not try to replace a bad file with its internally maintained backup.

Conflict Notification Alerts

If two administrators edit the same object concurrently, information is saved for the first person that applies a change, and Interaction Dialer sends a notification message to the second user:

"One or more properties for this campaign were changed by another user. Any current changes will need to be reapplied."

The conflict notification alert indicates that edits need to be recreated, since another user updated the record, overwriting the changes that were in progress.