MultiModule

MultiModule: Up to 4 modules, 552 subscribers

The STENTOFON AlphaCom E MultiModule function makes it possible to increase the capacity of an exchange by adding up to four AlphaCom E 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 refered to as InterCardCage, ICC.

All configuration data are stored on the AMC-IP board in the master module. The master module controls the resources in the slave modules using the ICC Protocol.

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.

Autonom mode

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 one audio source for program distribution, connected to the master module. See Audio Program feed in master

Module interconnections

IP network - VoIP

Connecting master and slave

An ethernet switch is needed to connect the 3 slaves and the master

When using MultiModule over IP no additional AlphaCom hardware required. MultiModule licenses are required for each AlphaCom E module. Conversations between modules are point to point, and not in a ring as in traditional MultiModule using AGA or AE1 boards.

The modules should be on the same LAN, as MultiModule uses fixed jitter buffer size of 10 ms

Cabling

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.

Programming

AlphaPro: Enter the IP adress of the slave modules

Perform a cold start of each module separately

AlphaWeb:

- Assign an IP Adress to each module

- Enable MultiModule Data (port 50.010) and AlphaNet Audio (port 61.000 - 61.150) in the Filter Setting. Default enabled on the Eth1 port.

- Enter the license key to enable the VoIP channels

AlphaPro:

- Enter the IP adress of the slave modules.

E1 link - AE1

AlphaPro flag: Use VoIP audio for Multi Module: Disable this flag when using AGA or AE1 for audio distribution in MultiModule, and not VoIP. Note that it is also possible to use a mix of VoIP audio and conventional AGA/AE1 links. Then this flag must be enabled.

Analog links - AGA

MultiModule configuration using analog AGA boards

AlphaPro flag: Use VoIP audio for Multi Module: Disable this flag when using AGA or AE1 for audio distribution in MultiModule, and not VoIP. Note that it is also possible to use a mix of VoIP audio and conventional AGA/AE1 links. Then this flag must be enabled.

Limitations in Slave Modules

Slave modules support analogue stations only, no other types of inputs or outputs. The slave modules do not support:

• Remote Control Inputs - RCI's
• Remote Control Outputs - RCO's
• Serial port drivers and other central equipment and licenses like RIO, Paging, AlphaNet, SIP trunk node and SIP registrar Node