Altigen MaxACD Administrator, Manual, Page: 211 / 261

Requirements
MaxACD Administrator Manual 201
Requirements
Some system components must be installed on separate servers. This section discusses
Voice recording and external applications.
Voice Recording
The target directory of recorded files should be in a server other than the primary and
secondary Softswitch.
External Applications
CDR Logger and Database – An External CDR Logger and external CDR database are
required in a Redundancy configuration. The active Softswitch will write a CDR to the
external logger.
The primary and secondary Softswitches synchronize the next session ID, so that when
the secondary Softswitch takes over, its session ID does not duplicate the primary's.
When a Softswitch becomes the active server, it connects with the External CDR Logger.
The External CDR Logger drops the original connection when it accepts this new one. The
Softswitch has a local buffer where it keeps CDR records when the External Logger
connection is unavailable. When the connection with the External CDR Logger is
established, these buffered records are written into the external CDR database.
Other Applications – Other applications can be either installed locally on each
Softswitch system or run as external applications on a separate machine from the
primary and secondary Softswitch. Examples of these external applications include
MaxCommunicator, MaxAgent, MaxSupervisor, MaxReports, VRManager, and so on.
All of them have a keep alive connection with the Softswitch. When switchover occurs,
each application detects that the connection has broken, and tries to reconnect with the
active switching server.
Configuring Redundancy
To set up redundancy, you will follow this general process:
1. Install the Redundancy Moderator; see “Step 1: Install the Redundancy Moderator”
on page 202.
2. Configure one server as the primary server; see “Step 2: Configure the Primary
Server” on page 203.
3. Configure the other server as the secondary server, adjusting its settings to match
those of the primary server. See “Step 3: Configure the Secondary Server” on page
203.
4. Reboot the servers; see “Step 5: Reboot Servers and Restart Services” on page 205.
5. Set the secondary server to take control when appropriate; see “Step 6: Set the
Secondary Server to Assume Control” on page 206.
6. Configure the DNS name in your DNS server; see “Step 7: Configure the DNS Name”
on page 206.
7. Set up switchover notifications (optional); see “Step 8: Configure Switchover Alerts”
on page 207.