DCT e-track, Руководство пользователя

Страница: 49 / 212

2.12. REMOTE HOST SOFTWARE [ADVANCED]
2.11.2 Reporting messages
The unit output messages when a command or query is sent or when
reporting an event message generated by the
Event Machine . These
messages are either the
EV
or
ET
messages. See the TAIP reference for
information on how to get the information contained on these reports.
2.11.3 Interacting
TAIP communication must be driven by a timeout-retry mechanism.
2.12 Remote host software [Advanced]
e-track
TM
’s is designed to interact with Automated Tracking servers
which have the ability of interpreting TAIP messages.
In this document, Tracking Server, AVL system, AVL host, AVL
application, remote peer, all make reference to the same thing: A
piece of server-type software which receives and makes some sense of
e-track
TM
reports. It may also have the capability of sending queries
or commands to the unit(s).
Depending on the communication mechanism the unit uses to com-
municate with a server some requirements have to be fulfilled. See
the next sections for information on this.
2.12.1 Working with TCP
In order for the unit to start connecting to a server an IP-type Des-
tination has to be configured first. The configuration flag for this
Destination must indicate a TCP host. Refer to the Destinations
section on the Configuration chapter. Destinations are also config-
ured with e-track Configuration Assistant’ Address Book .
These are the general requirements for a server working with units
on TCP:
1. The server has to be able to work as a TCP server, as e-track
TM
’s
is always going to initiate the TCP connection acting as TCP
client. Technically speaking, for this to happen the server has to
be able to open a TCP socket on listening mode on an available
port.
2. The port number has to be the same port number used on the
unit’s IP-type Destination and it has to be clear of any Firewall,
NAT and/or router restriction.
47