Fire-Lite IPDACT-2UD User Manual
IP COMMUNICATOR
IPDACT-UD
Technical Reference
Document DM385-Iv2
Version 2.0
April, 2007
i
TABLE OF CONTENTS
I - INTRODUCTION......................................................................................I-1
I - 1. IPDACT-UD Introduction............................................................................ I-1
I - 1.1. User Scenario............................................................................................I-1
I - 1.2. Operation Mode........................................................................................I-3
I - 1.2.1. Monitoring............................................................................................I-3
I - 1.2.2. Alarm sending......................................................................................I-5
I - 1.3. Additional features....................................................................................I-6
II - IPDACT-UD DESCRIPTION...................................................................II-7
II - 1. General Description......................................................................................II-7
II - 2. LEDs..............................................................................................................II-9
II - 3. Jumper.........................................................................................................II-10
II - 4. Connection points to the Control Panel and external..............................II-10
II - 5. LAN..............................................................................................................II-12
II - 6. Console ........................................................................................................II-13
III - CONFIGURATION............................................................................III-15
III - 1. Configuration modes............................................................................ III-15
III - 2. DHCP..................................................................................................... III-15
III - 3. Telephonic Console............................................................................... III-17
III - 3.1. Configuration...................................................................................III-18
III - 3.1.1. Default Configuration...................................................................III-19
III - 3.1.2. Register description......................................................................III-20
III - 3.1.3. Minimum configuration for the installer ......................................III-27
III - 3.1.4. Configuration Example ................................................................III-28
III - 4. Asynchronous Console......................................................................... III-30
III - 4.1. Accessing the console......................................................................III-30
III - 4.2. Main Menu ......................................................................................III-30
III - 4.3. IPDACT-UD generic configuration.................................................III-31
III - 4.4. Monitoring configuration and sending of alarms.............................III-31
ii
III - 4.5. IPDACT-UD Quick Configuration..................................................III-32
III - 4.6. Monitoring.......................................................................................III-33
III - 5. Telnet.....................................................................................................III-35
IV - APPENDIX .......................................................................................IV-37
IV - 1. IPDACT-UD Technical Specifications.................................................IV-37
The manufacturer reserves the right to introduce changes and
improvements to the appropriate features of both the hardware and
the software of this product, modifying the specifications included in
this manual without prior notice.
iii
I - Introduction
I - 1. IPDACT-UD Introduction
The IPDACT-UD is a device which, when connected to a security control
panel, carries out three basic tasks:
• To send over an IP network the alarm information sent by the pan el
to which this is connected.
• To check the connectivity between the control panel and the alarms
reception center.
• In cases where it is not possible to transmit over the IP net work, the
IPDACT-UD will stop intercepting the alarms from the panel. At this
point the alarms will be sent over the telephone line.
The IPDACT-UD operates together with the Teldat VisorALARM device,
located in the alarm receiver center. This behaves as an alarm receiver which
receives the said alarms through an IP network (instead of the traditional
public switch telephone network) and sends them through a serial port to
automation software in order to be processed. Additionally, this receives
monitoring messages from multiple IPDACT-UD and generates the
corresponding alarm in cases where communication fails with one or more of
these.
I - 1.1. User Scenario
A traditional security scenario consists of a control panel (CP), located in the
client environment and an alarm receiver center (ARC) located in the securit y
company’s control center. The CP contains a group of sensors which trigger
a series of alarms or events which, when produced, are sent to the ARC to be
processed.
Communication between the above is traditionally carried out over the
telephone line so that both ends can initiate a call to the remote end: the CP in
order to notify events and the ARC for bi-directional tasks (activation,
teleloading and general control).
The communication protocol varies depending on the manufacturers who
usually tend to use their own solutions. The IPDACT-UD supports Contact -ID
protocol.
The CP is placed as the first connection element to the PSTN so that it can
prioritize the customer’s telephone line.
IPDACT-UD - Introduction
I-1
Doc.DM385-I
Rev. 2.0
Alarm
Control Panel
Public Telephony
Switched Network
Client
Fax
Alarm Receiver
Sur-Gard/Radionics
Alarm Receiver Center
Automation SW
IBS/ MAS/ Micr o Ke y
Figure 1. Traditional security scenario
Within the general user scenario, the IPDACT-UD device is located in the
client area, next to the control panel, intercepting the telepho ne line. This is
displayed in Figure 2. The arrow in the figure demonstrates the preferred
path to send alarms from the CP; here the telephone line is used as a backup
in case there is a communication malfunction in the IP network.
Figure 2. Teldat VisorALARM and IPDACT-UD operating scenario
The IPDACT-UD has a functionality incorporated giving rise to a third possib le
scenario: network backup. In the previous scenario, where communication
fails between the device and the ARC, the IPDACT-UD hands over the
communications to the control panel. With the new functionality, the IPDACTUD tries to open communications with a second device, the backup
VisorALARM. Only in cases where there are problems with this second
device does the control panel take over. Meanwhile, even in this state, the
IPDACT-UD continues to try and communicate with the ARC until one of the
VisorALARMs responds.
IPDACT-UD - Introduction
I-2
Doc.DM385-I
Rev. 2.0
Figure 3. Network backup function scenario.
I - 1.2. Operation Mode
The IPDACT-UD connected to the client control panel carries out two tasks:
sending alarms from the panel and monitoring the connection with the IP
receiver. The network backup option has implications in connection
monitoring. The alarms reception center is composed of two VisorALARM
devices, one main and the other backup.
I - 1.2.1. Monitoring
The IPDACT-UD is a device that intercepts the control panel telephone
connection with two aims: firstly to detect when the panel sends an alarm in
order to capture it and retransmit over the connected IP network and secondl y
to allow the telephone line to be used at the same time as sending alarms.
The interception of the telephone line takes place ONLY in cases where
connectivity with either of the Teldat VisorALARM devices has been verified.
The IPDACT-UD-VisorALARM connectivity is checked through a traffic
monitor which the IPDACT-UD periodically sends and to which the main
Teldat VisorALARM responds. (Through configuration, the main
VisorALARM IP address is given to the IPDACT-UD and is the primary
communication option. The backup VisorALARM IP address is also
configured and is used in cases where the main device fails). If the exchange
of messages does not occur during the configured time, the IPDACT-UD tries
to resend. If, after a configurable number of attempts, a satisfactory response
is not received, the connectivity with the main VisorALARM is presumed lost.
At this point the IPDACT-UD tries to communicate with the backup
IPDACT-UD - Introduction
I-3
Doc.DM385-I
Rev. 2.0
VisorALARM, to which it will now try and send the alarms, polls, etc. In
=
cases where communication with this second device also fails, the telephone
line access is returned to the control panel as if the IPDACT-UD was not
present. From this point on, the IPDACT-UD will try to re-establish
communications both with the main Teldat VisorALARM and the backup,
communication with the main device taking priority. The moment
communications are reestablished with either of the two ARC devices, the
IPDACT-UD intercepts the telephone line once more.
The supervision traffic is encrypted UDP. The Ethern et frame size does not
exceed 70 bytes. The monitoring interval, the number of retries and time
between retries are all configurable, and are values that must be carefully
considered. Normally the monitoring interval in the control pane l is high as
this implies a telephone call. However, in the case of IPDACT-UD, this cost is
irrelevant as it is dealing with traffic which in all likeliness is runn ing over a flat
rate connection. In addition, a high value here is not advisable in cases where
the IPDACT-UD connects to Internet through a router executing NAT, a very
probable situation. This is because traffic coming from the ARC towards the
IPDACT-UD reaches this thanks to the router maintaining the entry in the NAT
table active during a period of time, the entry bei ng refreshed with supervision
traffic. If the supervision interval is greater than the residence time for the
entry in the NAT table, communications from the ARC will not be possible.
There is no rule to say how long an entry i n the NAT table must last for. In
cases of the TELDAT devices, this is around 5 minutes. A low value has the
problem that the traffic the VisorALARM must process is high, the same as
the bandwidth requirements. If ARC Internet access is ADSL, you need to
consider that the upstream channel is smaller than the downstream one and
that supervision traffic returned to the IPDACT-UDs is slighter larger than the
incoming.
The incoming traffic to the ARC is:
NTC **528
−
mipsALIVEKEEP
The minimum supervision time can be 1 second and a Vis orALARM can have
3000 IPDACT-UDs registered that give an input traffic of 1,58 Mbps. The
return traffic is approximately 6% larger.
The Teldat VisorALARM received monitoring messages from the IPDACTUDs. If these are registered, they are assumed alive and an
acknowledgement response is sent to them; if the IPDACT-UDs are not
registered, they are ignored. Periodically the status of all the registered
IPDACT-UDs is checked and all those which have not notified th eir avail abilit y
(i.e. those which have not responded since the last check) an alarm is
generated. This is a 350 code alarm from the Contact-ID protocol
(Communication trouble) which is received in SwAut.
In order to prevent the Teldat VisorALARM from sending hundreds or
thousands of communication failure alarms when faced with a situation of
general failure of IP traffic reception, the device itself monitors the network
IPDACT-UD - Introduction
I-4
Doc.DM385-I
Rev. 2.0
access through echo ICMP packets (ping) to a known address: if the echo
ICMP packets (ping) towards this address fail then a code 356 alarm is
generated from the Contact-ID protocol (Loss of central polling).
Apart from the above codes, the VisorALARM also generates others related
to network backup.
I - 1.2.2. Alarm sending
When the IPDACT-UD has connectivity with the Teldat VisorALARM, the
former intercepts the telephone line and processes all the incoming and
outgoing calls taking place.
The supported alarm sending protocol is Contact-ID. This format sends
alarms through DTMF digits complying with the following format:
AAAA MM QEEE GG CCC S
where AAA is the client number, MM the type of message, Q an event
qualifier, EEE the type of alarm, GG the group or partition number, CCC the
zone number and lastly S is the frame validation digit.
When the panel opens to send an alarm, the IPDACT-UD provides power and
emits the dialing tone. When the control panel dials the alarm center
telephone number, it issues the Contact-ID handshake and receives the alarm
frame. From this point, the IPDACT-UD sends this alarm to the
VisorALARM.
The control panel is not given the frame sent acknowledgement (kissoff) until
the said acknowledgement is received from the Teldat VisorALARM. If the
IPDACT-UD does not receive the acknowledgement within 2 seconds, this
carries on resending a configured number of times after which connection with
the Teldat VisorALARM is assumed lost and the control panel sends the
alarm over the telephone line. From this point, the IPDACT-UD tries to reestablish communication with the VisorALARM as previously descr ibed. In
cases where the network backup functionality is operative, a failur e in sendi ng
an alarm to the main VisorALARM changes into an attempt to establish
communications with the backup VisorALARM and to send the alarms to this
second device. If this attempt also fails, then the control panel takes over the
process of sending the alarms.
It’s essential that the total time, in which the IPDACT-UD deactivates
in cases where communications fail with both the IP receivers, is
greater than the control panel’s highest retry time.
The IP VisorALARM receiver on receiving an alarm from an IPDACT-UD
stores this in a non-volatile internal memory. When the operation has
successfully finished, it sends the acknowledgement to the IPDACT-UD
originating the alarm so that in turn this is sent to the associated control panel.
If the alarm storage memory cannot store the alarm, no acknowledgeme nt is
given.
IPDACT-UD - Introduction
I-5
Doc.DM385-I
Rev. 2.0
As regards the SwAut, the Teldat VisorALARM behaves as an alarm rec eiver
that sends alarms received through a serial port. The Teldat VisorALARM
can emulate a Sur-Gard, an Ademco 685 or a Radionics 6500 receiver. The
serial line parameters are configurable as well as those relative to the
emulated receiver (link-test, receiver and line identifier, start and end frame
characters, etc.)
I - 1.3. Additional features
In order to simplify installation and updating of the registered IPDACT -UDs,
the IP VisorALARM receiver has additional facilities.
To install new IPDACT-UDs, the Teldat VisorALARM possesses
configuration patterns associated to installer passwords. These permit you to
automatically register new IPDACT-UDs in the supported IPDACT-UD list and
at the same time enable the IPDACT-UD to request the necessary
configuration for start up. The device can simultaneously have multiple
patterns; the choice of one or other depends on the installer pass word used in
the IPDACT-UD to request the service.
In order to maintain and update the registered IPDACT-UDs base, the Teldat
VisorALARM has commands available to remotely update one or multiple
configuration parameters used by the IPDACT-UDs.
Additionally, in order to simplify the IP parameters configuration, something
that is not always easy, the IPDACT-UD has a DHCP client program, which
attempts to automatically obtain all the IP connectivity information (address,
mask and gateway) on startup. To do this, you need to have a DHCP server
in the local network. If the IPDACT-UD does not automatically obtain the IP
address, use the parameters that have been statically configured, permitting
you to make sure that the device operates even when the said server is down.
The IPDACT-UD allows trouble signaling to be sent to a maintenance
VisorALARM receiver, which is a different device from the main and backup
VisorALARMs. The IPDACT-UD does not discriminate between sending
to one receiver or another depending on the type of signal (alarm or
trouble), but sends the same signal to both the operating receiver and to
the maintenance receiver. It is the receiver’s task to filter the signals t o be
sent to the automation software.
Receivers that can be configured as maintenance are those containing
firmware version 10.5.16 and higher. These receivers are characterized as
they do not execute IPDACT-UDs supervision functions, nor carry out any
remote operations over the IPDACT-UDs, nor do they admit IPDACT-UD
registration. These are repeat alarms coming from the IPDACT-UDs and
simply filter the signals, sending only the required signals to the automation
software.
IPDACT-UD - Introduction
I-6
Doc.DM385-I
Rev. 2.0
II - IPDACT-UD Description
II - 1. General Description
The figure displayed below, represents the IPDACT-UD hardware.
Figure 4. IPDACT-UD
The hardware version and release is identified through its board number
which is TS-563/X where X is the release number.
The following figure shows the identifier details and how to locate it.
Board identifier
Figure 5. Board identification details
IPDACT-UD - Description
II-7
Doc.DM385-I
Rev. 2.0
The IPDACT-UD basically consists of three elements:
• The Analog Subscriber Line Circuit module (Telephonic module).
• The V32 modem module.
• The Control module.
Figure 6. IPDACT-UD circuit details.
The device CPU, memory and the LAN (identifiable through the RJ-45
connector) are found in the control module. This manages all the information
procedure and the sending of the said information through a n IP network over
the LAN.
The telephonic module physically supports the control and contains all the
connection points with the control panel. This manages the entire telephon ic
interface with the control panel and the client telephone network (public
telephone network termination point and client phone wiring).
The V32 modem module adds the necessary elements to make telephonic
data calls to the control panel and so support upload/download functionality.
From a configuration / monitoring point of view, the IPDACT-UD possesses
LEDs that permit you to view the status of the various elements, from the P1
jumper to control various aspects and a telephonic c onsole. This telephonic
console is accessible from the connection to the control panel (TO-AP) and
requires an analog telephone with tone dialing.
The IPDACT-UD has an asynchronous console which permits you to monitor /
configure the device through an asynchronous terminal.
IPDACT-UD - Description
II-8
Doc.DM385-I
Rev. 2.0
II - 2. LEDs
The IPDACT-UD has three groups of LEDs that provide information on the
status of each type. These are displayed in the following figures:
Figure 7. LEDs and pins for a IPDACT-UD
The LED labeled “ON” (LD1 for all the versions an d releases) is green and
indicates that the IPDACT-UD is powered.
Line status LED: Next to the relays there is a LED labeled LD6. In green this
indicates that the telephone relays are active i.e. the IPDACT-UD interce pts
the telephone line. In normal working mode, this only occurs when the
IPDACT-UD has connectivity with the configured VisorALARM. The relays
also activate when the telephone console activates (pleas e see section IV.2
for further information). When the control panel is executing maintenance
tasks due to a bi-directional call, the relays are inactive.
LEDs LD2, LD3, LD4 and LD 5 each have an independent connotation:
• LED A LD2: Supervision information.
ON: a management frame is sent to the VisorALARM (contact or keep-alive).
OFF: a response is received to the sent management frame. If there is no response,
this remains active, indicating the lack of connectivity with the VisorALARM.
• LED B LD3: TO-AP terminal status
ON: the alarms panel telephone line is off hook.
OFF: the alarms panel telephone line is on hook.
IPDACT-UD - Description
II-9
Doc.DM385-I
Rev. 2.0
Loading...