Alcatel-Lucent OmniTouch, Administration Manual, Page: 92 / 382

............................................................................................................................................................................................................................................................
Remote sites System Configuration
2 - 7 2 8AL90208USAD ed01
November 20, 2008
............................................................................................................................................................................................................................................................
If this step is not performed, ACS will send the IP packets through eth0 (default gateway).
........................................................................................................................................................................................................................
6
Connect the Ethernet cable to the appropriate Ethernet interface.
........................................................................................................................................................................................................................
7
Reboot the server.
Note:
If you connect the Ethernet interface to the wrong connector, you will have to
reconnect to the correct connector and reboot again.
........................................................................................................................................................
E
N D
O
F
S
T E P S
Remote sites
There are two methods by which Alcatel-Lucent OmniTouch Advanced Communications
Servers can operate as an integrated set of servers when they are not co-located. The first
method is by setting up a stack which is connected by a private LAN over long-distance
links. The second method is through ‘federation’, by which Alcatel-Lucent servers are
configured to be aware of specific other servers. Federation is accomplished through the
configuration of Remote Sites. This allows conferences to be effectively bridged between
servers, with participants calling into the server nearest them, thereby minimizing long-
distance charges. Thus, if a conference includes 5 people in London and 5 people in Des
Moines, each person would call into their local server, and the only long distance link
would be a single conference trunk between the two servers. The link would persist only
while there are conferences active that span the two servers.
Remote sites are primarily designed to allow sharing of conference access codes among sets
of servers or stacks which are not co-located. They do, however, have certain functional
limitations. In many cases, a geographically distributed stack with dialing rules will be more
suitable. Please contact your sales representative if you are considering deploying
geographically distributed servers.
Remote Sites require some configuration on the stacking page. Although any stack name
that is defined pertains only to a local stack, node numbers among remote sites must all be
unique. This is because the same conference codes are scheduled on multiple servers.
The trunk between the servers can be either IP or PSTN. If it is PSTN, the phone number
that other servers should call to link to this server is configured on the Stacking
configuration page. In a PSTN configuration, a TDM Network Interface Module must be
present on both servers to allow them to connect. If no remote site phone number is
configured, but sites are defined, the link between them will be VoIP.