TD 92232GB
2005-06-15 / Ver.G
Installation Guide
ELISE2
24
4.16 Message Distribution
In the administration pages, there are distribution lists that are used to distribute incoming
information to other modules. If a module is to be connected to several carrier systems,
for example both System 900 and a Cordless Telephone System, distribution of incoming
data from the different systems has to be configured independently. The distribution of
"Status Logs" and "Activity Logs" are configured separately. Advanced activity settings for
activity logs are described in the
Function Description, Activity Logging in Unite,
TD 92341GB.
The addressing is described in the examples below:
Addressing a module on the System 900 A-bus
When a specific module on the A-bus is addressed, the data will be transferred directly to
that module. It is however not necessary to address a specific module on the A-bus as the
Central Unit in the System 900 can distribute the data to a module. Note that this requires
configuration of the Central Unit.
• No module addressing
127.0.0.1/S900
The data is sent to the System 900 interface in the ELISE2 module, which sends the
data on the A-bus without the module address defined. The Central Unit in the system
has to be configured to distribute the data to a module. It is also possible to address
the System 900 interface on another module by entering its IP address instead of
127.0.0.1 (localhost).
• Module addressing
127.0.0.1/S900?03
The data is sent to the System 900 interface (127.0.0.1/S900) in the ELISE2 module
and is then sent to the module with address 03 in the system. It is also possible to
address the System 900 interface on another module by entering its IP address instead
of 127.0.0.1 (localhost).
Addressing another Unite compliant module on the LAN
The addressing includes the IP address that the data should be distributed to and also
which service on that address that should take care of it. How a unit is addressed is
described in each units documentation.
• Addressing of another Unite compliant module
xxx.xxx.xxx.xxx/Service
First the IP address of the module is defined. After the “/”, the application service that
should take care of the data is specified.
Below is an example that describes how to distribute data from an ELISE2 software
application to an Alarm Management Server.
• Addressing of an Alarm Management Server
xxx.xxx.xxx.xxx/EventHandler
First the Alarm Management Server IP address is defined. After the “/”, the application
service EventHandler is specified.
Note:
For AMS version 3.00 and 3.10 the service cannot be used. Instead the correct
port on the AMS, port number 10010, has to be used for addressing, i.e.
xxx.xxx.xxx.xxx/:10010.
