Difference between revisions of "Redundant AlphaCom integration"
Jump to navigation
Jump to search
(→AlphaPro Configuration) |
|||
| Line 22: | Line 22: | ||
== AlphaPro Configuration == | == AlphaPro Configuration == | ||
Basic configuration on the AlphaCom contains two steps: | Basic configuration on the AlphaCom contains two steps: | ||
| − | * Define and map IP addresses to the Exigo | + | * Define and map IP addresses to the two Exigo Nodes (the two controllers). |
* Define and set up the group which Exigo should call. | * Define and set up the group which Exigo should call. | ||
| Line 30: | Line 30: | ||
| − | === Step 2. Define and set up the group which Exigo should call === | + | === Step 2. Define and set up the group which Exigo should call === |
| − | |||
| − | |||
== EMT Configuration == | == EMT Configuration == | ||
Revision as of 15:15, 1 February 2017
This article explains how to setup and configure redundant AlphaCom integration on an Exigo A-B system.
The solution may also be used for Exigo system with hot-standby controller.
Contents
Configuration Overview
Exigo Management Tool (EMT) is used for setting up the integration from Exigo.
AlphaPro is used for setting up the integration from AlphaCom.
From Exigo there is two types of actions defined:
- Action Calls - from AlphaCom to Exigo.
- AlphaCom features - from Exigo to AlphaCom.
Exigo will use numbers from 98001 and upwards to start activities in Exigo on incoming activities. Outgoing from Exigo can define any number.
AlphaPro Configuration
Basic configuration on the AlphaCom contains two steps:
- Define and map IP addresses to the two Exigo Nodes (the two controllers).
- Define and set up the group which Exigo should call.
Step 1. Define and map IP addresses to the Exigo Node
Step 2. Define and set up the group which Exigo should call
EMT Configuration
(This featur is available from Exigo 1.3.2.7)
