Campaign Director High Availability

Last Updated : Jul 03, 2025 |

In a multi-server deployment of POM, the Campaign Director service runs in the master or dormant mode within a single data center.

Campaign Director consists of the following components:

Component

Description

Common Campaign Director

Common Campaign Director manages all common tasks across zones, such as scheduling, filtering campaign data, creating historical data, and exporting campaign data. The master Campaign Director is the Common Campaign Director.

Zone Director

Each zone has a Zone Director within a Campaign Director. A single Campaign Director can handle multiple zones. You can assign multiple zones to a Campaign Director.

If the master Campaign Director process fails gracefully, the other Campaign Director immediately becomes master and all operations, except purging, are resumed. If the master Campaign Director process fails ungracefully, another Campaign Director becomes the master after 2 minutes and 20 seconds of the failover time.

For information about NFS mounting requirement to support contact-list import for HA, see Implementing Avaya Proactive Outreach Manager.





Impact of the Common Campaign Director failure

Function

Impact

Job state

The jobs that are started from the user interface remain in the queued state.

The campaign does not get completed even when the system dials all contacts or the finish criteria is met. Such campaigns finish when the Campaign Director is functional again.

Pausing and resuming campaigns based on user action

The job state remains unchanged until the dormant Campaign Director takes over.

Triggering campaigns and data imports at scheduled date and time

The scheduled imports and campaign schedules do not work for the time for which the connection is unavailable.

Export

The export function stops. When the Campaign Director is functional again, the export function resumes from where it stopped.

Purging

The purging function stops during the purge operation if the Campaign Director becomes non-functional. When the Campaign Director is functional again, the purging does not resume. The purging starts at the next scheduled date and time.

Campaign Post Processing

The campaign post processing function stops. When the Campaign Director becomes functional again, the campaign post processing function resumes from where it stopped.

The completion code trend report might show stale data for the time for which the Campaign Director is non-functional.

Terminating campaigns if the finish criteria specified are met

Campaign Director does not perform periodic checks for the finish criteria, and the campaign does not stop dialing until the dormant Campaign Director takes over the failed server.

Trend calculation

Trend calculation, Campaign progress chart, and multiple campaign summary on Supervisor Dashboard show stale data for the time for which the Campaign Director is non-functional.

Report

The completion code trend report might show stale data for the time for which the Campaign Director is non-functional.

Nuisance rate and alarm generation

Nuisance call rate calculation and alarm generation stop until the Campaign Director is functional again.

Job allocation

When the master Campaign Director and Campaign Manager simultaneously fail, then the job handled by that Campaign Manager is not allocated to any other Campaign Manager until the Campaign Director is functional again.

Impact of the Zone Director failure

Function

Impact

Data import

The running import jobs resume after any other Zone Director process inside the Campaign Director takes over. However. the status on the user interface reflects as Running.

The import function stops. When the Campaign Director is functional again, the import function resumes from where it stopped.

Reconfiguration of a zone

When the failed Campaign Director becomes operational again, it acts as the dormant server. However, it takes back the zone responsibility allocated to it before the failover.