From Zenitel Wiki
The AlphaCom XE MultiModule function makes it possible to increase the capacity of analog station lines by adding up to four AlphaCom XE exchange cabinets together in a master-slave configuration. The multi-module exchange acts as one node with full integration of all features. In some documents multi-module is referred to as InterCardCage, ICC.
MultiModule or AlphaNet?
In general MultiModule is recommended when the modules are located in the same room, and the purpose with the additional modules is to extend the line capacity. A MultiModule system being a part of an AlphaNet is seen as a single node.
AlphaNet is recommended when modules are located apart from each other, in different floors, building or cities. In AlphaNet each module is a stand-alone exchange.
When modules are connected over IP, a software license is required.
Available MultiModule licenses:
- 1009640202: Multi-Module VoIP license - 2 Modules
- 1009640203: Multi-Module VoIP license - 3 Modules
- 1009640204: Multi-Module VoIP license - 4 Modules
- 1009640211: Multi-Module VoIP license, upgrade + 1 module
Filter settings (Firewall)
To be described..
The multi-module exchange supports redundancy mode. In case of master-slave communication error, the slave module will fallback to work as an individual exchange serving calls between stations connected directly to the exchange module. The AMC Master can be set to copy its content to the slave modules over a 28 hour period. In AlphaPro, Exchange & System > System > Calls & Options, set the flag "Autonom Mode: Copy NVRAM".
Audio Program feed in master
As from software AMC 10.22 and AlphaPro 10.27 there is an option to use a single audio source for program distribution in a MultiModule system, connected to the master module. See Audio Program feed in master
IP network - VoIP
When using MultiModule over IP no additional AlphaCom hardware required. Instead a license is required. There are two options:
- - A MultiModule license. Required in the Master module only.
- - A channel based MultiModule license. Required in each module.
The modules should be on the same LAN, as MultiModule uses fixed jitter buffer size of 10 ms
The modules are connected via a single Ethernet cable. Two modules can be connected back to back. A straight cat5 ethernet cable can be used. With three or four modules an ethernet switch is required.
Perform a cold start of each module separately
- - Enter the IP adress of the slave modules.
Line switched Rings
The older AGA/AE1 based ways of inter module interconnection is still supported. Requires more HW and cabling, but provides a few advantages over VoIP makes it still an option to consider.
- less delay on voice than packed based VoIP
- lowspeaking call, with both handsets lifted, do not require duplex or LEC resources (due to the low delay)
- all 30 VoIP channels can be used for AlphaNet
Even if old style using AGA/AE1 is used for inter-module audio, it is highly recommended to use TCP/IP for data-signalling to the slaves, instead of RS232. (To set up the data connection, follow same programming as in the preceding VoIP section, except there is no need for a license.)
By default AlphaCom will use AGA/AE1 rings for intermodule call as long one is available. If no (free) AGA/AE1 found, VoIP channel is used for intermodule. (Before AMCD 10.53: intermodule calls used both VoIP and AGA/AE1 channels in strict rotation).
AlphaPro flag: Exchange & System -> System -> VoIp "Use VoIP audio for Multi Module": Disable this flag to only use AGA or AE1 for audio distribution in MultiModule, disabling VoIP for intermodule.
The AGA boards of the modules must be interconnected in a ring.
Limitations in Slave Modules
The slave modules do not support:
- Serial port drivers and other central equipment and licenses like RIO, Paging, AlphaNet, SIP trunk node and SIP registrar Node
AMC versions prior to 10.43 do not support in slaves: