Installation manual

VBIP Install Manual
V1.00
Page 2/4
www.villbau.com
The following sections detail the network and telephone
communication parameters of the module.
3.1. Network Parameters
These paramters define the operation of the VBIP
Module on the ethernet network.
IP Address
This is the IP address of the VBIP Module in case of
fixed IP addressing is chosen, and the module tries to
obtain this IP address first from the DHCP server. In
this case, however, it can occur, that the DHCP server
assigns another address to the module. The default IP
address is 192.168.1.128. Check the „Use DHCP”
switch to use automatic address inquiry.
Gateway/Router Address
The VBIP Modul forwards all requests to external IP
addresses to the gateway (router). The default is empty
(0.0.0.0), if using DHCP, the module obtains gateway
address from the router automatically.
Subnet Mask
The VBIP Module can decide between internal and
external addressing according to the given subnet
mask. The default is 255.255.255.0. with DHCP, the
module obtains subnet mask from the router
automatically.
Server IP Address
The VBIP Module tries to forward its events to this IP
address. The default is 192.168.1.240. In case the
server address is not known, the address resolution
through the name of the server is also possible:
Server Name
In case only the name of the server is known, the
module can resolve its IP address by using the DNS
name servers. DHCP must be enabled for this feature,
as the DNS server addresses are obtained from the
router. Also, the „Use DNS” switch must be enabled,
and the name of the server must be given. If the server
name is valid, the module will use its IP address for
forwarding events.
Server Port
The port of the monitoring server, where it receives the
events. By default it is 9999, the actual port is assigned
by the system administrator of the monitoring station.
VBIP Port
This is the port of the VBIP Modul, which is used for
reporting to the server. The default is 6200. This can be
any number, but care must be taken as specific port
numbers are already bound to functions according to
the standards (E.g. 21 for Telnet, 80 for HTTP, etc.)
UDP/TCP Reporting
For the VBIP Module it can be chosen, which protocol it
will use for reporting the events. The options are UDP
or TCP. Normally, UDP protocol uses a lower amount of
traffic, while in theory, TCP protocol offers extra data
security through its built-in software handshaking. In
practice, the UDP protocol ensures the proper data
security as well, with much less traffic, so that its usage
is recommended. Receiving servers usually support
both protocols, so that the final setting is decided by the
system administrator of the monitoring station. The
default setting is UDP.
IP Reporting Format
The VBIP Module supports multiple IP reporting
formats. The default is simple CID reporting, where the
Contact ID event is forwarded 1 to 1 as is, with or
without encryption (AES128 encryption is an option).
The second format is the E2, the custom IP format of
the Enigma II receiver. This allows forwarding additional
data as well, like MAC, Serial, etc. Encryption (AES128)
is also an option for this format. This format is of course
used primarily with Enigma II receivers.
The third optional format is the standard, SIA IP
reporting format (ANSI/SIA DC-09-2007), which offers
versatile use of the module with any monitoring station
supporting this standardized format. AES128
Encryption is optional for this format, too.
The actual reporting format to be used is always given
by the system adminsitrator of the monitoring station.
AES Encryption
Regardless of the reporting format used, the VBIP
Module can encrypt its messages (full or partial
encryption) with the AES-128 encryption method. This
is a standard encryption using a 128 bit key. The actuak
process (full or partial encryption) is determined by the
reporting format used. The key for the encryption is
provided by the system adminsitrator of the monitoring
station.
Keep Socket Open for Reporting
(not supported by version 1.00)
If using TCP protocol, the module closes the socket to
the server after succesful reporting. In some cases, it
might be useful to keep the socket open, even if there is
no event to report, thus maintaining continuous
connection to the server. This can be used for
monitoring the connection but care must be taken, as
maintaining too many open sockets at once, can
overload the monitoring station receiver. The usage of
this option is enabled by the system adminsitrator of the
monitoring station. By default, the option is disabled.
Note: In case the option is disabled, the module closes
the socket after about 10 seconds of inactivity. This
ensures, that the connection will not unnecessarily be
closed during telephone communication reception.
Block PING
The VBIP Module can block the incoming PING
commands, thus being „invisible” on the network. By
default, this option is disabled.