Go to documentation repository
Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.
Intellect allows sending events from the system objects to the VideoGuard server (see http://videoguard.ae/). In this case, Intellect acts as a client of the VideoGuard system.
The integration with the VideoGuard system is configured as follows:
Create the VideoGuard integration client object on the basis of the Computer object on the Hardware tab of the System settings dialog box (1). If data from several Intellect servers in a distributed system should be sent to VideoGuard, then create and configure a separate VideoGuard integration client object on the basis of each server.
Note
A single VideoGuard integration client object is enough to send messages about the loss of connection with any server. See also step 7.
- Set the Server name in full format checkbox (2), if it is necessary to display the full server name. By default, short server name is displayed.
- In the Server address field, enter the connection address to the VideoGuard server (3).
- In the Device ID on the server field, enter the identifier which is assigned to Intellect on the IP interface server (4). There should be no more than 6 digits in this field.
- From the IP-interface drop-down list, select the network adapter which is used to connect this computer to the VideoGuard server (5).
From the IP address drop-down list (6), select the IP address that will be sent to VideoGuard as Intellect server address.
Note
The IP address list displays all addresses from all available IP interfaces. If you specify an IP address that doesn't belong to the selected IP interface, the system will send a random IP address from those available in the selected IP interface.
- In the Ping sending period field, specify the Heart Beat messages sending frequency in seconds (7). By default, the Heart Beat message is sent right after the Intellect starts and then every 5 minutes (300 seconds).
- Configure the correspondence between the VideoGuard and Intellect events. By default, the correspondence table contains the mandatory events, and their correspondence with the Intellect objects events is configured. If necessary, you can change this correspondence, add or remove additional events:
- From the Server event ID drop-down list, select the event identifier on the VideoGuard server (8). See the supported values in the table below.
- From the Computer drop-down list, select the name of the Computer object. The selected events of the objects, which are based on this Computer object, will be sent to the VideoGuard (9). If the value is not specified, the events are sent from the specified objects, regardless of which Computer object they are based on; in this case such events may not be processed correctly in VideoGuard.
- From the Type drop-down list, select the Intellect object type, the events from which should be sent to the VideoGuard server (10).
- From the Number drop-down list, select the Intellect object identifier, the events from which should be sent to the VideoGuard server (11). If the identifier is not specified, then events are sent from all objects of the selected type.
- After you select the object type and identifier, the Name field will be automatically filled with the name of the selected Intellect object (12).
- From the Event drop-down list, select the event which is coming from the Intellect object of the selected type and which corresponds to the VideoGuard server event with the specified identifier (13).
- To add new event, click Add filter (14), then perform steps a-f to configure it.
- To remove an event, select corresponding row in the table and click Remove filter (15).
- If there is one VideoGuard integration client object and several Computer objects, then connection loss events from all computers in the distributed system are transmitted to VideoGuard software by default. If you do not need to transmit connection loss events from some computers, go to the Computers tab (1) and clear the checkboxes (2) next to the corresponding Computer objects (3).
- Click the Apply button.
The integration with the VideoGuard system is configured.
Restart Intellect after connecting to the VideoGuard server to synchronize the time with the VideoGuard server. After Intellect restart, the time zone in Windows is synchronized with the specified VideoGuard server. Subsequently, the Intellect server will synchronize with the NTP server of the VideoGuard system (by calling the GetNTPServerInfo method). During synchronization, the VideoGuard system server will return the time synchronization period (120 seconds by default), and within 24 hours after synchronization with the NTP server, time synchronization will be performed at the specified interval.
The event identifiers supported on the server:
ID | Description | Corresponding Intellect event |
---|---|---|
1 | No video signal | Camera: Connection lost |
2 | Video source connection | Camera: Connection |
3 | Disk overflow | - |
4 | Error writing to disk | Computer: Disc unmounted |
5 | Client connection | VideoGuard integration client: Video module started Note. The event is generated in the following cases:
|
6 | Client disconnection | VideoGuard integration client: Video module unloaded Note. The event is generated in the following cases:
|
7 | Motion detection trigger | Camera: Alarm |
8 | Case opening (Shelter Alarm) | - |
9 | Start of recording to the archive | Camera: Harddisk rec |
10 | End of recording to the archive | Camera: Record on disk stopped |
11 | Change of recording to the archive schedule | - |
100 | Additional event | Used to send additional events to the VideoGuard server. In this case, the event source identifier is added to the event identifier Example: The event with the 101 identifier will be sent to the VideoGuard server |
Note
If several Servers are added to the configuration, then after the restart of the main Server, the events with the 5 identifier will be sent to those Servers that are turned on or were turned on at the time of the restart of the main Server. At the same time, the event with the 6 identifier won’t be sent to those Servers that were turned off at the time of the restart of the main Server.