by demes ALARMSPACE ARC Software For Control Of Security And Fire Devices User Manual
- June 6, 2024
- by demes
Table of Contents
by demes ALARMSPACE ARC Software For Control Of Security And Fire Devices
User Manual
VESTA Gateway Configuration
Introduction
Welcome
The Climax VESTA intrusion control panel can send the generated events in
different formats. AlarmSpace has expanded its capabilities to receive these
events, process them and generate new output signals adapted to the protocols
of the main reception software currently in our country (Manitou, SBN,
Softguard and compatible).
In addition, the AlarmSpace itself performs a programmable polling control and offers us the option to deactivate subscribers (they are not sent to the ARC software) and to change the polling times. Additionally we can monitor the events received in real time.
The reception system offers a high availability configuration through a cluster of two machines (main and backup) that reduces to very low levels the possibility of missing events or experiencing significant delays.
VESTA Panel Programming
The recommended programming scheme for the correct reception of events from
the VESTA Control Panel is represented in the following picture.
In this figure, ARC represents alarm receiving software, VESTA represents an
installed PBX, and
AlamSpace MAIN and BACKUP are two instances of AlarmSpace on two different
machines. They
can be virtualized, but we recommend that they are setup on different physical
machines. If the
connection to AlarmSpace MAIN fails, the control panel will try it through
AlarmSpace BACKUP. It
will always retry the MAIN connection to see if it recovers.
To program the communication parameters in the VESTA panel we must go to the
ByDemes Cloud: https://smarthomesec.bydemes.com/ByDemes/ and log in with our
username and password. Once inside we select the desired panel and go to the
Setting / Report section
In the different URLs we configure the communication parameters. URL1 is reserved for internal use. In URL 2 we enter the data of our main receiver Alarm Space as follows:
Ip: //[email protected]: 23506 / MAN
Where 1234 is the subscriber number, 3.12.123.123 is the Alarm Space public IP, and 23506 is the open port for the Alarm Space machine to receive events.
IMPORTANT NOTE
The IP must be written without leading zeros, it must NOT be completed with 0 up to the 3 digits. If you do this, the connection will not work.
In the group we assign Group 2, this ensures that all events will be sent.
To ensure maximum availability we recommend assigning a new URL (URL 3). This has to be directed to the Backup AlarmSpace machine (with the public IP of the backup machine and the port open on that machine). We will also choose Group 2 to send only the events that fail through the main route (different groups are sending all, the same group sends only those that fail in the previous one).
In the Sequence of Sending (Reporting Sequence) we choose Essential and in the retries we recommend only one retry to speed up the passage to the secondary route if the shipment fails (if the secondary route is not used we can increase up to 3 retries).
Image upload data will be missing:
Also with the “Manitou” protocol and the string [email protected]: 23506 with the same subscriber number, IP and port as the main route.
We click “Send” and we will have the assigned communications.
IMPORTANT NOTE
We recommend that communication with AlarmSpace BACKUP be carried out
over another communication path (another fiber / ADSL different from the main
one) and from different Operators (with different physical infrastructure), to
ensure the reception of events over one of the communication lines.
AlarmSpace Settings
VESTALog – General Settings
The VESTALog application has different functionalities. View the events
received and forwarded to the ARC reception software in real time, view a
history of the treated frames, a text log with the operating details of the
receiver and a configuration of receiver parameters.
Real Time Events
Events visualization received from the VESTA control panels, the responses
and the events sent to the ARC software and their responses.
Events History
The frames received from VESTA control panels are displayed. We can filter
them by date and by subscriber number.
Log
Record of actions carried out by the application. Useful for testing and
debugging.
VESTA Configuration
Receiver parameters:
-
My Server: IP of the local mysql server (the machine’s own IP)
-
My Backup Server: IP of the backup mysql server (leave 0 if it is in Alarm Space Backup or the Backup machine is not implemented)
-
path Videos: path where received images and videos will be saved.
-
Ip: local (private) ip of the machine on which we will open the listening port.
-
Port: the listening port. It must be opened in TCP on the router to receive events for this machine.
-
Encryption Port: the port for listening to encrypted frames (different from the one receiving unencrypted
frames). If more security is desired, the control panels can be programmed to send with encryption as follows:
ip: //[email protected]: 23508 / MAN_TLS for events Choose Manitou (TLS) for images. -
Polling Event Code: the Contact ID code that the application will understand as a polling signal, to control disconnections. It will not be sent to the receiving software.
-
Polling Event Code Fail: Contact ID code sent to the third failure of the polling signal.
-
Polling Event Code Rest: Contact ID code sent when receiving a polling signal while in polling failure.
-
Event Code Mac Error: an event generated by the gateway with this code will be generated when it is detected that the identification (MAC) of the panel sending with a subscriber number does not correspond to the identification that was received when registering the subscriber for the first time.
-
Vesta Auto activate Ab: if it is at 1, the new subscribers that the application receives are activated automatically. If it is zero, the subscriber is registered, but it must be activated manually.
-
Vesta Polling Time: time between polling signals by default. It will be automatically assigned to all new subscribers. It can be changed individually.
-
Vesta Days Preserve Frames: days the history frames will be kept.
-
Vesta Days Preserve Images – Days images will be kept on the Alarm Space hard drive
-
Vesta Num Ab: application subscriber number to send internal events.
-
Vesta Internal Test Code: Contact ID code sent as internal test (heartbeat) of the application itself.
-
Vesta Internal Test Period: frequency with which the internal test of the application will be sent in seconds. If it is 0, the test is not sent.
-
Vesta Account Default Test Period: frequency with which a VESTA panel test will be sent to the ARC Software if it is polling correctly.
-
Allow Multiple Destinations: Allow multiple destinations of signals to ARC
-
Computer Protocol: Output protocol, it must match the one programmed in the control panel (XML, SIA …).
-
AS Receiver Type: ARC software
-
skip Date From Frame: DO NOT send event date, even if it comes in the frame
-
automatic Response: Do not send event to ARC software and confirm automatically
-
Event Code Polling SIA: In case of using the SIAIP protocol (SIA-DC09) we set the code for the polling event.
-
private Protocol: we can change the type of model used (CID) to a custom one in the frame sent to the ARC software.
-
refuse User Captures: if we set this field to true, requests for pircam images made by users (web or App) will not reach ARC, thus preserving privacy.
-
continuous ARC Connection: the connection with the ARC software is made at the start of the service and is not interrupted, it is constantly maintained.
-
send Caller Id To ARC: the identification of the control panel is sent in the frame sent to the ARC.
-
Externally Monitoring: the internal test of the control panel (launched periodically according to Vesta Internal Test Period), you can also check external connectivity by sending it through the public IP.
-
public Ip: public IP used by the Vesta server, used to send the internal test externally..
Event Destinations
We define particular destinations to which signals received from VESTA can be
sent. They will be selectable by each subscriber:
We have to define the Ip, port and a line (if it is used by the ARC software it has to receive the event). We put a name to reference it in the particular subscribers, in the Alarm Space Server -> DVR -> INTRUSION Subscribers.
Reassign Events
Functionality that allows rewriting the event code of a frame, so that the ARC
software receives the desired event:
In this example, when the video event of a pircam jump (E770) is received from the control panel, the event will be sent to the ARC software with event E880. There is also the option of delaying the event so that it arrives a few seconds later at the ARC.
AlarmSpace General Settings
The communication parameters with the ARC Software are configured in the AlarmSpace Server, in the Configuration / Receiver Parameters section:
We have to select the type of program, mark as active, and write the port and
ip of the server. In this version, the VESTA control panel only transmits in
ContactID format (regardless of the selected template, which does apply to
recorder events).
Subscriber Control
On image below, we have the subscribers of the application, if they are active
or not, the polling time, if
they are in polling failure, the date of the last polling received, the Type
of Control Panel, the MAC of the equipment if available, the group assigned to
it, the number of consecutive polling failures to submit the failure, and the
log date:
If we double click on a subscriber we can change some parameters of the
subscriber:
Specifically, we can change the Polling Period (to adjust it to the one programmed in the VESTA control panel in question), in minutes, and activate / deactivate the subscriber. If a subscriber is inactive, the signals that may arrive are recorded, but they do not pass to the ARC management software. It also allows you to program a test periodically (polling that will reach the ARC software). In this example it is sent every 24 hours. With the MAC of the equipment we check if the subscriber number that we receive corresponds with the MAC that we have registered. If not, we send an error event (by default code E304, see VESTA configuration). There is the possibility of assigning a group to each subscriber. Groups can then be assigned to users, so that each user would have two-way access only to their subscriber group. The Num. Polling Failure column is the number of consecutive failures that must exist for the polling failure event to be sent. If not defined, the default is 3. In the last column, we can see the date on which each subscriber was registered.
ARC Alarm Receiving Software Configuration
Manitou
This is an example where the receivers are configured in Manitou and an
example of how it should look:
You can use a dedicated port / driver or a shared one (more than one
receiver). We must choose the line that matches the one we have programmed in
the VESTA panel gateway:
And the type of Manitou transmitter with “Video Capability”:
SBN
Contact your regular IBS technician to enable communication with the gateway.
Soft guard
Contact your regular Soft guard technician to enable communication with the
gateway.
New Viewer Module – Bidirectional access for VESTA control panels
The Viewer module is an application that allows you to view the videos received in alarm and the photographs captured manually through any HTML5 compatible web browser and that allows it to be “called” from any ARC software that allows assigning a URL to an alarm event. It contains bi-directional functionalities with the control panels that allow arming / disarming the control panel, canceling / enabling zones, capturing an image from the pircam and applying scenes defined in the control panel.
Vesta Viewer call command
The current version of AlarmSpace V2 includes an additional web server for VESTA control panels that listens on port 8003.
It looks for (when installed) the first free port on 8003.
This port can be modified in a text file “configuracion.dat” inside the installation folder and restarting the service.
(It should be open between the operators’ machines and the machine running AlarmspaceV2). It is also important that the IP that appears in this file (in the first 4 lines) corresponds to the IP of the AlarmSpace Server (in the example 192.168.X.XXX):
server = 192.168.X.XXX; database = by demes video; User Id = by demes video;
password = 06851f3848543ea; port = 3350; Persist Security Info = True
192.168.X.XXX:8003
192.168.X.XXX:9000
192.168.X.XXX:10003
After all this, you can now use the call to the website with the following
format: http://111.111.111.111:8003/bydemesVisor.html?subscriber=XXXX
111.111.111.111 being the IP of the machine on which Alarm Space runs and XXXX
the subscriber number of the VESTA control panel.
Optionally you can add the parameter seconds Before: http://111.111.111.111:8003/bydemesVisor.html?subscriber=XXXX&secondsBefore=YYY
If we put seconds Before it will only list the videos and images of the last
YYY seconds. If there are none, it refreshes until one is received.
This call will open the web browser with the following window:
On the left side we have the most recent video received in alarm and also the last 10 videos received, accessible from a drop-down.
In the central part we have the last 10 photographs taken manually from the VESTA application, also accessible from a drop-down.
On the right side we have the status of the partitions and zones of the control panel, and the bidirectional functions. We can carry out a partial arming, a total arming or a disarming of each of the partitions. Apply or remove a bypass to an area and capture an image from a pircam (if we have permissions). Finally, we can apply scenes that we have defined in the control panel, which allow, for example, to turn off the lights and arm the panel when leaving the house or the opposite process when entering.
