Categories
Software Downloads Software Categories exacqVision Client Linux x64 exacqVision Client Categories Products Uncategorized

ExacqVision Client Linux x64 v24.09.3.0

Q3 2024-09-19 ev-Client-Linux-x64^Version 24.09.3.0^https://cdnpublic.exacq.com/24.09/exacqVisionClient_24.09.3.0_x64.deb^19 September 2024^109MB,

Categories
Documentation Integrations exacqVision Client Categories Products exacqVision Integrations Uncategorized

Elgato Stream Deck Integration Guide

Overview

When configured properly, exacqVision may be configured to react to Elgato Stream Deck to take actions, such as changing camera views or activating output alarms. This is made possible by exacqVision’s Serial Profile settings combined with Event Monitoring or Event Linking. This guide provides the steps needed to get started, which you may customize to suit your needs.

IMPORTANT: This guide is provided for user benefit, but Exacq Support will not provide assistance or troubleshooting for Stream Deck devices or Stream Deck software.

<br>

Stream Deck Configuration

  1. Download and install the Stream Deck software, which includes drivers needed to recognize the device when plugged into your workstation as well as software used to customize its behavior.<br><br>
  2. Open the Stream Deck software from the Start menu or system tray on the taskbar. Stream Deck has limited capabilities out of the box, but provides a marketplace where developers offer plugins to expand its functions, similar to adding apps to your mobile phone or tablet.<br><br>
  3. With the Stream Deck software window open, access the Marketplace by selecting the Marketplace icon, which will open a web browser to the Marketplace page.<br><br>
  4. Use the search field to find CommandSender, which at the time of this writing was the most capable plugin available for this purpose and free to download and install.<br><br>
  5. Click on CommandSender in the search results, then select the Get button. Once installed, return to the Stream Deck software.<br><br>
  6. Locate and expand the Custom section from your actions panel on the right, then expand the CommandSender item. Drag an instance of the Send Command action from the panel onto a button in your layout. This button is customized in the lower part of the window.<br><br>
  7. Set the Communication Type to ‘TCP’.<br><br>
  8. Enter the IP address of the system running your exacqVision Server into the IP Address field. The Port number defaults to ‘45671’, but you may customize this if that port is already being used on your system.<br><br>
  9. In the Command Pressed field, enter something unique and descriptive to the action you want to take. In the pictured example we enter GoToCamera 09 because in later steps we will configure a camera panel to change when pressed. This text can be anything you’d like because you will pair it to an action in later steps.<br><br>
  10. Next, add the code for a line feed, \x0a, to the end of your command. This is used to help separate commands when received by exacqVision.<br><br>
  11. You will not use the Command Released field for use with exacqVision.<br><br>
  12. Finally, you can choose to customize the icon using icons from Stream Deck, import icon packs from the Marketplace, or upload custom icons you’ve created. You also have an optional Title field.<br><br>
  13. You may add as many instances of the CommandSender plugin to your button layout as you wish, but the Command Pressed field should be unique for each one. The IP Address and Port fields should be the same unless you are sending commands to different NVRs.<br><br>

<br>

exacqVision Serial Port Configuration

You will need Full Admin or Power User privileges on the system to perform the following steps. The steps in this section are performed only once on each NVR you are sending commands to.

  1. Open the exacqVision Desktop Client application and enter Configuration mode by selecting the cog wheel icon in the upper-left corner.<br><br>
  2. From the left-hand navigation panel, expand the system name, then select the Serial Ports node on the tree.<br><br>
  3. Under the IP section, press the New button.<br><br>
  4. In the new row that appears, enter something in the Name field, such as “Stream Deck”.<br><br>
  5. Change the Use column to ‘POS’.<br><br>
  6. Change the Profile field to ‘New…’.<br><br>
  7. Change the Type field to ‘TCP Listener’.<br><br>
  8. In the Address column field, enter the IP address of the workstation you have plugged your Stream Deck into.<br>
    NOTE: It is expected that you will connect the Stream Deck to a Client workstation, but if you are connecting it directly to the system running the exacqVision Server application, the IP Address used here and in CommandSender will be 127.0.0.1.<br><br>
  9. In the Port field, enter the port number displayed in CommandSender, which by default is ‘45671’.<br><br>
  10. The remaining fields are left as is.<br><br>
  11. Because ‘New…’ was selected in the Profile column, when you press the Apply button you will be automatically taken to the Serial Profiles page to configure the profile described in the next section.<br><br>

<br>

exacqVision Serial Profiles Configuration

  1. Begin by providing a descriptive Name to your Serial Profile.<br><br>
  2. Test the ability to receive commands from the Stream Deck by pressing the configured CommandSender button on the panel. You should see the commands you configured on the button appear in the data window.<br><br>
  3. For this use case you do not need to enter anything into the fields for SOT marker or EOT marker.<br><br>
  4. Select the Event Keywords tab.<br><br>
  5. Press the New button.<br><br>
  6. In the String field, enter the text exactly as you entered when configuring the button in CommandSender, without the line feed code.<br><br>
  7. Press Apply to save your changes.<br><br>

<br>

NOTE: If you need additional help with the configuration of Serial Ports or Serial Profiles, please see the exacqVision User Manual or refer to our User Training Videos on the Exacq Support Portal covering these features.

<br>

Event Monitoring and Event Linking

As this document is not intended to be a complete training guide on the use of exacqVision’s Event Monitoring and Event Linking features, we will provide a single example of changing a camera panel to display another camera when the button is pressed. Keep in mind that Event Monitoring provides client-side actions visible to the user of the workstation, such as changing camera panels, live Views, enabling audio, or digital PTZ presets, while Event Linking performs server-side actions, such as recording video, mechanical PTZ presets, auto exports, sending notifications, or triggering webhooks.

NOTE: For additional help with the configuration of Event Monitoring or Event Linking, please see the exacqVision User Manual or refer to our User Training Videos on the Exacq Support Portal on these features.

For this example:

  1. Select the Event Monitoring node on the navigation tree, located near the top of the left-hand panel.<br><br>
  2. Press the New button under the Profiles panel and enter a descriptive Name in the Profile Configuration area to the right.<br><br>
  3. Change the Show Event List field to ‘On Event’.<br><br>
  4. Check the Show Newest Event box.<br><br>
  5. Set the Type selection to ‘Video Panel’.<br><br>
  6. The first Client Action is added for you. Configure the default action by selecting ‘Default’ from the Event Type panel. Default events do not have an Event Source to select.<br><br>
  7. From the Action Type panel, select ‘Switch Video’.<br><br>
  8. Select a camera from the Action Target panel to display when nothing else is being triggered.<br><br>
  9. Press the New button under the Client Actions panel in the middle of the window.<br><br>
  10. From the Event Type panel, highlight ‘Serial Profile’.<br><br>
  11. You may have many items listed on your system, or several systems to select from. The drop-down menu will filter to specific systems or show them all. Select the item displaying the name of the Serial Profile you created earlier with the Keyword you configured. The profile is monitoring the incoming data being sent from CommandSender on your Stream Deck for this Keyword.<br><br>
  12. Select ‘Switch Video’ from the Action Type panel.<br><br>
  13. Choose a camera from the Action Target panel that you want to display when the Stream Deck button is pressed.<br><br>
  14. Next, you’ll set exacqVision to return to the Default camera after a set number of seconds rather than forcing a user to click in the Event List panel to acknowledge it each time.<br><br>
  15. Uncheck the Confirm checkbox near the bottom of the window.<br><br>
  16. Change the Timeout field to “5”.<br><br>
  17. Press the Apply button to save your changes.<br><br>

<br>

Use the same Event Monitoring profile you just created to continue adding additional Client Actions for each CommandSender button you have configured on the Stream Deck.

Navigate to the Live view in the Client window to test your setup.

  1. Drag several different cameras to the layout.<br><br>
  2. Right-click one of the panels. In the menu that appears, expand Event Monitor, and select the name of the Event Monitoring profile you just created. The camera you configured as the Default should display.
    <br><br>
  3. Press the CommandSender button you created on the Stream Deck. This camera panel should now change from the default camera to the camera you configured in your Event Monitoring profile with the Event Keyword.<br><br>
  4. After the 5 second timeout period you set, the camera panel should return to the Default camera.

<br>

Opening the exacqVision Client

If you’d like to create a button on your Stream Deck to automatically open an instance of the exacqVision Client, this can be done without additional plugins or serial data configuration using the built-in Open action.

Within Stream Deck, perform the following:

  1. Expand the System menu from the actions panel.<br><br>
  2. Drag an instance of the Open action from the panel onto an empty button in the layout.<br><br>
  3. Customize this instance near the bottom of the window.<br><br>
  4. Provide an optional Title and/or customize the button’s icon.<br><br>
  5. In the App/File field, either navigate to the edvrclient.exe file on your machine, or enter the path manually. The default path is C:\Program Files\exacqVision\Client\edvrclient.exe

Users of customized Client .XDV files may open instruct the Open action to open the client using their desired .XDV file by adding the file path to the file. e.g.- C:\Program Files\exacqVision\Client\edvrclient.exe -F"C:\Users\myUserName\Documents\myCustomFile.xdv"

<br>

Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server Products Uncategorized

Global At Most Rule 30 Days

Description 

There are some reports that after setting up Global At Most Rules the data is not removing older content off the drives. For example if recording has been taking place for a year and Global At Most Rule is set up after a year of recording some of the older content is not being removed from the data drives.

Product 

  • Server 23.09.9.0
  • Linux 18.04

Steps to Reproduce 

Oldest content on the storage drive will show content past the current Global At Most Rule that are configured. This was seen on units that had been recording for a long amount of time. Then at some point a Global At Most Rule was created. After the 30 days the data was not being removed from the system.

Expected Results 

We should purge older data. However if there is a year worth of data we may need to give it a hand to clear out in special cases where customer need to see a certain amount of Oldest content on the Storage page.

Actual Results 

If data is on the unit for 365 days, then it can take time for that data to be purged. It will keep showing Oldest content of 365 days until it successfully purges the data.

Solution

A work around is to delete some of the older content outside their current Global At Most Rule.

1. Stop the server and check the data folders on the drives.

2. NOTE: ALWAYS HOLD SHIFT and then hit the Delete Key. If you do not do this it can fill up the OS drive’s recycling bin.
Remove Years, Months as needed from the data folder.

3. Start the exacqVision Server Service and allow up to 5 minutes for the Sweeper to run. We delay the Sweeper service from starting right away on purpose.

4. Monitor the logs on the server around the 5 minutes, and search for a sweeper event, and then look for a fscleanup event in the logs. If this is seen you can validate on the Storage page if the Oldest Content numbers change within the next several minutes down to the size of the At Most Rule 30 Days.

In the following example we stopped the service and removed data off the drives down to 62 days and 9 hours.
After removing the data we started the service and waited 5 minutes.

After 5 minutes you should see the following in the logs.

PSFPI    Verbose    Sweeper - expiring all files older than Tue Apr 2 10:20:58 2024.


This indicates that the Sweeper is looking at the older content on the drive and preparing it to be removed.

After a few more minutes the oldest content was reduced down to the target Global At Most Rule of 30 days.




Current Ticket opened is AES-847.

<br>

Categories
User Guides Documentation Integrations Illustra Categories Products exacqVision Integrations Uncategorized

Illustra Body Worn Camera Kiosk 2.x Integration Guide

Overview

This document will guide you through installation, configuration, and functionality of the Illustra Body Worn
Camera system and how to view this video, both live and recorded, from the ExacqVision Server.

<br>

Requirements

Kiosk Requirements

  • Illustra Body Worn Kiosk 2.0.124 or higher

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NOTE: Microsoft .NET 4.8 or higher is needed and will be included if not already found during installation.

Workstation Requirements

For best performance, we recommend installing the Kiosk software on hardware that meets or exceeds that of an Exacq C-Series workstation. For third-party workstations, not built by Exacq, adhere to the following specifications:

  • Operating System – Windows 10 or later
  • RAM – minimum 16GB
  • CPU – Intel Core i7 or greater

If using a C-Series workstation, built by Exacq, please use the Windows OS image release version 22.02.07 or above.

ExacqVision Requirements

  • ExacqVision Server 23.09 or higher
  • ExacqVision Client 23.09 or higher

<br>

<br>

Kiosk Software Installation

  1. Unpack the contents of the downloaded .ZIP file containing the install package.<br><br>
  2. Within the extracted files, locate and run the Setup.exe file.<br>
    <br><br>
  3. Use the text fields provided to create a Kiosk Password. Enter this twice to confirm the entered password before clicking Next.<br>
    <br><br>
  4. The following step displays the four Kiosk components to be installed. Click the Agree and Install button to accept the End User License Agreement and continue.<br>
    <br><br>
  5. When installation has finished, click the Close button.<br>
    <br><br>
  6. If you did not uncheck the box to create a Desktop shortcut, you may now use the created shortcut to open a web browser to access the Kiosk software. If you did not choose to create this shortcut, you will need to navigate to https://localhost:5000 in your web browser.<br>
    <br><br>

NOTE: Successful Kiosk installation will include four new running Windows Services.

  • JCI Body Worm Camera Kiosk Driver Service
  • JCI Dock Controller Service
  • Illustra Mobile Video Manager
  • Illustra Mobile Live Relay

<br>

Kiosk Setup

The Bodycam Kiosk is where camera checkouts are managed and recorded video will be uploaded. These recordings can be searched from a connected ExacqVision server.

  1. The Kiosk utilizes a self-signed certificate A self-signed certification cannot be verified by your browser, so your browser will most likely warn you that your connection is not private. Use the Advanced option to continue to the Kiosk login.<br><br>
  2. Login using ‘admin’ as the Email ID for the default administrator account, and the Kiosk Password you created in Step 3. Additional accounts may be created by followin the User Setup steps.<br>
    <br><br>
  3. Click the gear icon in the upper-right corner of the page to access the Kiosk Settings.<br>
    <br><br>
  4. Create and enter an API Username and an API Password in the labeled fields. These are used in a later step to connect the ExacqVision VMS to your Kiosk.<br><br>
  5. If your deployment will include live video streaming, you will also need to complete the Relay Server field. Enter the IP address of the Kiosk workstation followed by the port number 4257.
    Example: 192.168.10.3:4257<br><br>
  6. In the bottom-right corner is the Charging Threshold. A camera that is docked will not become Available to check out again until the battery charge has reached this threshold. By default this is set to 90(%).<br><br>
  7. Lastly, it is recommended to check the One Camera Per User box, near the bottom, to prevent multiple devices being allotted to a single user/camera wearer.<br>
    <br><br>
  8. Click Save.

<br>

Creating a Camera Profile

Camera profiles allow you to define common configurations to be easily applied to multiple cameras.

  1. Click the menu icon in the top-left corner of the page, then select Profiles.<br>
    <br>
    IMPORTANT: At this time only the Default profile supports WiFi. Edit the Default profile, using the pencil icon, if you require WiFi enablement. WiFi is only necessary for live streaming.<br><br>
  2. Click the Add New Profile button. Within the New Camera Profile Configuration window, the Profile Overview tab appears.<br>
    <br><br>
  3. Provide a unique Profile Name.<br>
    <br><br>
  4. You may toggle the option to apply this profile to all available cameras. This will only apply to cameras already added to the Kiosk. Cameras added later will need the profile applied manually, or by re-editing the profile configuration. Alternatively, you may opt to select specific cameras to apply the profile to, using the Select Camera menu and Add button.<br><br>
  5. Navigate to the Camera and Recording option. Use the Camera tab to select the aspect ratio, resolution, and frame rate settings for this profile.

    Additional controls on the Recording tab permit you to enable/disable Auto IR and audio recording settings, as well as enable/disable Privacy Mode. Privacy Mode allows the camera wearer to prevent live streaming. The camera firmware must be version 8.2.0.111 or higher to enable Privacy Mode.<br>
    <br><br>
  6. If your intended deployment requires live video streaming, you will configure the Illustra Mobile Video Manager tab. Within the Server Address field, enter the IP address of the Kiosk workstation, which hosts the Illustra Mobile Video Manager service.
    Example: 192.168.10.3<br>
    <br><br>
  7. APN Settings are not supported at this time.<br><br>
  8. Toggle the control to Enable WiFi. See also: Network Profiles. Cameras must be connected to the same internal network as the Kiosk workstation and Illustra Mobile Video Manager service via WiFi for live video streaming.<br>
    <br><br>
  9. Using the Actions and LEDs tab, you may configure the behavior and actions taken by the camera’s buttons and LED indicators.<br>
    <br><br>
  10. The Sounds and Vibrations tab provides the ability to customize audio indicators to alert the wearer to status changes.<br><br>
  11. Click the Save button when you are finished making settings changes to the profile.

<br>

Network Profiles

Enabling WiFi within a Camera Profile permits the device to use WiFi capabilities. To configure the network authentication, select the Network Profiles tab at the top of the Profiles page.

  1. Enter the network SSID.<br><br>
  2. Enter the authentication Password.<br><br>
  3. Select the Security method.<br><br>
  4. Click the Add Network button. Repeat the previous steps as needed for additional SSIDs.<br>
    <br><br>
  5. Click the Save button when done.<br><br>
  6. Additional network settings may be located towards the bottom of this page.

<br>

Configuring Users

  1. Click the menu icon in the top-left corner of the page, then select Users.<br>
    <br><br>
  2. Click the Add New User button.<br>
    <br><br>
  3. Complete the provided fields for the user’s First Name, Last Name, and Email.<br><br>
  4. Create the user’s password by completing the Password field. It is suggested that the user enters this while being enrolled to prevent an administrator from knowing other user’s passwords.<br>
    <br><br>
  5. From the User Type selector, choose whether the user account will be a Camera Wearer or Kiosk Admin.
    • Camera Wearer – may check out cameras, cannot affect changes to Kiosk settings or users.
    • Kiosk Admin – full Kiosk access.<br><br>
  6. Check the box confirming the identity of the user before clicking the Save button.<br><br>
  7. Repeat Steps 2 through 6 for each user needed.

<br>

License Management

Bodycam Kiosk requires licensing for live video and audio streaming.

  1. Click the menu icon in the top-left corner of the page, then select Live Stream License.<br>
    <br>
    <br><br>
  2. This page allows Kiosk Admins to quickly view the license status. Click the View Available Licenses button for an overview of the number of licenses in use or available.<br>
    <br><br>
  3. Clicking Request a New License provides a new dialogue window. Complete the Email and Sales Reference Number fields, then select whether to:
    • Email the license request (requires an email client on your Kiosk workstation).
    • Download the license request file to send from another workstation, or at a later time.<br><br>
  4. Once a valid license file has been provided, return to this page to utilize the Upload a New License button so it may be applied to the system.

<br>

Connecting Cameras

Illustra Body Worn Cameras may be connected to the Kiosk workstation in one of two ways:

  • USB Cable – each camera is packaged with a USB-C to USB-A cable. The USB-A connector will connect to the Kiosk workstation while the USB-C end will connect to the camera.

    It is strongly recommended to keep these cables even if using the Docking Station as you may find that many USB-C cable connectors are not of sufficient depth to properly connect when plugged into the camera.<br><br>
  • Docking Station – an optional 8-port docking station is available, capable of charging and transferring data for up to 8 cameras over USB-A 3.0 cable. Multiple docking stations may be utilized on a single Kiosk.

IMPORTANT: It is strongly recommended to connect cameras and Docking Stations to the blue USB 3.0 ports on the Kiosk workstation. Failing to do so will result in much slower data transfer times.

<br>

Updating Firmware

The process of updating the firmware running on the cameras can be performed through the Kiosk dashboard by a Kiosk Administrator.

  1. Select the gear icon in the upper-right corner of the dashboard and choose Update Firmware, or select the gear icon on one of the individual camera tiles and select Update Firmware.<br><br>
  2. Use the Browse Files button to locate your firmware .APK file.<br><br>
  3. Select the Update button.<br><br>
  4. During the update process you will notice cameras in the Kiosk move to Not Ready and the cameras will reboot. Do not disrupt the update process or disconnect the cameras during this period. When completed, the cameras will return to the Available state.

The camera firmware files may be found in the Kiosk install package. Open the contents of the extracted .ZIP file and locate the .APK file within the ‘bin’ folder.

NOTE: A firmware update will affect all connected cameras.

<br>

Kiosk Dashboard

Kiosk Admins will see a Tiled View by default. Each camera is displayed as a tile, showing the camera name and status information.

The camera tiles are separated into three sections:

  • Available – cameras to ready to be checked out for use.
  • Checked Out – cameras already checked out.
  • Not Ready – cameras still transferring data or charging.

Clicking on the gear icon allows a user to manually change the profile assigned to the camera. If changing the profile assigned to a camera, this must be done prior to check-out. It is not recommended to change the camera password in the camera settings as this is tied to Mobile Video Manager and will prevent live streaming without manual intervention to match this password within the MVM software.

An administrator also has the option of using the Forget Camera button in the camera settings to permanently remove a camera from the Kiosk, as in the case of a lost or damaged camera that will not be reconnected.

A Kiosk Admin may also choose to view cameras in a List View using the View type buttons in the upper right-hand corner of the page.

Adding a new camera to the Kiosk is as simple as plugging in the USB cable or seating the camera in the Docking Station.

When connecting a camera to charge or transfer data, it may take a moment to be recognized and its status to be updated in the Kiosk.

NOTE: A camera must reach the configured battery charge threshold before it becomes Available.

<br>

Connecting to ExacqVision

ExacqVision integration copies the downloaded video/audio from the Kiosk workstation to the ExacqVision Server making the video easy to store and search alone, or alongside your connected IP security cameras.

  1. Within the ExacqVision Client software, click the gear icon to enter Configuration settings.<br><br>
  2. Within the navigation tree on the left-hand side, expand the node labeled with the server name, to display the nodes nested beneath it.<br><br>
  3. Expand the Configure System node.<br><br>
  4. Select the Body Worn Cameras node.<br><br>
  5. On the Body Worn Cameras page, check the Enable checkbox.<br><br>
  6. Using the Type selector, choose Illustra Body Worn.<br><br>
  7. Enter the IP Address of the Kiosk workstation. Do not alter the port number.<br><br>
  8. Enter the API Username and API Password you created in the Kiosk Setup steps into the Username and Password fields.<br><br>
  9. If you plan to use live streaming in your deployment, check the Enable Live Streaming checkbox.<br><br>
  10. Click Apply.<br>

Body Worn Camera users will appear on the camera tree to the left alongside any infrastructure IP or analog cameras.

<br>

Camera Check Out

IMPORTANT: When checking out a camera, wait until the light on the camera begins flashing before disconnecting from the USB cable or Docking Station. This light not only indicates the assigned camera, but tells the user it is ready to be disconnected. Disconnecting prior to this will leave the camera in a disconnected, unassigned state.

Kiosk Admin

When logged in as an administrator:

  1. Select one of the Available cameras to use.<br><br>
  2. Press the Check-Out button.<br><br>
  3. In the field titled User ID number, enter the assignee’s email address. This was configured when creating the User account. You may also begin typing the user’s name and select it from a displayed list of matches.<br><br>
  4. Check the box titled, I certify that I have confirmed the identity of this user.<br><br>
  5. Click the Check-Out button.<br><br>
  6. Wait for the camera light to flash before disconnecting.<br><br>

Camera Wearer

If the deployment is not attended by a Kiosk Admin, the Kiosk provides a self check-out experience. A registered Kiosk user will:

  1. Sign into the Kiosk using the registered email and password.<br><br>
  2. Click the Assign A Camera button.<br><br>
  3. The Kiosk will inform the user which camera to remove by name.<br><br>
  4. Wait until the light on the camera flashes before disconnecting.<br><br>
  5. Close the window by clicking the X or the Cancel button to automatically logout, ready for the next user.

<br>

Camera Check In

Reconnect the camera to the USB cable or Docking Station. The Kiosk will automatically begin transferring recorded data. The camera will become Available again once charged and all data has been transferred.

NOTE: A camera must have at least 90% battery charge before it becomes Available.

<br>

ExacqVision Live Streaming

Cameras with WiFi enabled will automatically connect when in range of access points correlating with the SSID and credentials entered in the Network Profile. Cameras that are connected and ready to live stream will display a green arrow in the camera tree of the ExacqVision Client’s Live viewing page.

To view the live stream, add the camera to a panel just as you would a fixed IP or analog camera, by dragging it onto a camera panel or double-clicking it.

When viewing live streaming video or listening to live streaming audio the data is automatically recorded on the NVR. You may stop the live stream by positioning your cursor over the center of the panel and pressing the Stop icon that appears. This will also cease recording on the NVR, but will not stop local recording on the camera if the wearer has enabled recording.

Streams which have been disconnected may be restarted by pressing the Play icon when the ‘Live Stream Available’ message appears.

If attempting to display a live stream when the camera wearer has enabled Privacy Mode, the following image will appear until Privacy mode has been disabled.

<br>

ExacqVision Search

Performing forensic search and playback of video and audio is similar to that of fixed cameras. However, you will note that each camera wearer’s name appears twice in the Camera List pane.

Video and Audio recorded locally on the device while being worn is downloaded from the device to the Kiosk when docked. This data is then transferred to the NVR. Locally recorded video and audio data is searched using option labeled ‘– Recorded‘.

Video and Audio that have been live streamed to ExacqVision Client users is recorded directly to the NVR. This is a separate stream and is searched using the option without the ‘– Recorded‘ label.

Live stream recordings, camera-side recordings, and fixed infrastructure camera recordings may all be displayed side-by-side within the Search screen of the ExacqVision Client, and/or exported.

<br>

GPS Data

Cameras with location data enabled, with a clear view of the sky for GPS positioning, record GPS data as an analytic. Select the geolocation box beneath the camera wearer name from the camera tree, as pictured.

Enter your search date/time range, then press the Search button as you would any permanently positioned IP camera. GPS data is recorded in intervals when the device is moving. This is indicated by the red lines on the geolocation row in the timeline.

Clicking the Show/Hide Keywords and Serial Data icon below the Quick Export button will toggle the Keywords and Serial Data panel to view the geolocation data similar to analytics from infrastructure IP cameras.

<br>

Categories
Knowledge Support Support exacqVision Client Categories Products Uncategorized

XDV Reference

*** INTERNAL USE ***

Type Definitions

  • Integer – Numeric value
  • Bool – 1 or 0 value where 1 is ‘enabled’ and 0 is ‘disabled’
  • String – Any text value
  • DIP – Device Independent Pixel (represents screen coordinates and sizes)
    • Windows
      • If the system is not using any sort of DPI or screen scaling represents actual pixel values
      • If screen scaling is in use then this number is multiplied by the scaling value
        • Example: A 4k monitor would typically use 200% scaling. A value of 1920 would represent your full display width (1920 * 200% = 3840)
    • Other platforms
  • Epoch – Numeric value representing the number of seconds since January 1st, 1970

The options described in the documentation below are listed in dictionary values, where possible. This is indicated by the key values listed between curly braces ‘{ }’. The key is followed by the description of the key value is colon separated, as in the following example:

&nbsp;&nbsp;&nbsp;&nbsp;{key1:description1, key2:description2, …}

More than one Instance or Item tag may be defined.

Tags and attributes not included use client defaults.

<br>

XDV / XML Structure

&lt;exacqVision Init&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Instance&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Live&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Layout&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Item/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Layout&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Video&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Input/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Video&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Audio&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Input&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Audio&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/System&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Live&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Instance&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;SecurityIntegrations/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Sync/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Alerts/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;HWAccel/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Joystick&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt/Joystick&gt;
&lt;/exacqVision Init&gt;

<br>

exacqVision Init Attributes

AllowAccelerators
ShowSunkenBorder bool {0:disabled, 1:enabled}
ShowRecStatusBorder bool {0:disabled, 1:enabled}
ShowPTZFocusBorder bool {0:disabled, 1:enabled}
ShowOnScreeDisplay bool {0:disabled, 1:enabled}
UseOsdColor bool {0:disabled, 1:enabled}
Use OSD color for Serial Profiles
KeepAspectRatio bool {0:disabled, 1:enabled}
Keep aspect ratio during resize
RestoreOnAttnReq bool {0:disabled, 1:enabled}
Restore client on user attention request
MySystemsColMask
EntCamColMask
AnalogCamColMask
IPCamColMask
EntCamFilterTreeSize integer (DIP value)
Width of filter tree panel on Enterprise Cameras
NonEntCamFilterTreeSize integer (DIP value)
Width of filter tree panel on Camera Recordings
VGAAccelMode
VGAAccelColorspace
DisplayAdapter
TimelapsePlaybackInterval integer {0-15}
Immediate jump to next frame if gap exceeds X seconds
PanelSizeRatio integer {0:content, 1:window, 2:16×9, 3:4×3}
CameraSortOrder integer {0:default order, 1:ascending, 2:descending}
GroupsSortOrder integer {0:default order, 1:ascending, 2:descending}
MapsSortOrder integer {0:default order, 1:ascending, 2:descending}
ViewsSortOrder integer {0:default order, 1:ascending, 2:descending}
EventsSortOrder integer {0:default order, 1:ascending, 2:descending}
BookmarksSortOrder integer {0:default order, 1:ascending, 2:descending}
ReportsSortOrder integer {0:default order, 1:ascending, 2:descending}
LiveAudioLipSync integer {0:auto, 1:enabled, 2:disabled}
AudioInputDevice integer
0 indexed list based on client detected devices
MuteDuringTwoWayAudio bool {0:disabled, 1:enabled}
AutoFillEmptyVideoPanels bool {0:disabled, 1:enabled}
CPUDecompResult
EnableIndicators bool {0:disabled, 1:enabled}
Show notifications for indicators
ConfirmClose bool {0:disabled, 1:enabled}
Prompts user for confirmation when attempting to close client window
CollapseLiveAutoContexts bool {0:disabled, 1:enabled}
Hide individual quality streams
CombineRegionOfInterestStreams bool {0:disabled, 1:enabled}
Manage all streams as quality streams
CameraPreviewMode integer {0:no preview, 1:thumbnail, 2:video
ShowSystemGroups bool {0:disabled, 1:enabled}
Show system group folders
RequireSSLCert bool {0:disabled, 1:enabled}
Require SSL certificate validation
UseSparseConnections bool {0:disabled, 1:enabled}
Use dynamic connections
SparseSystemCount integer
Number of systems using dynamic connections
EnableAllAnalytics bool {0:disabled, 1:enabled}
NormalLayoutCollapseMode integer {0:auto, 1:expanded, 2:collapsed}
EventButtonCollapseMode
LastUsedNormalLayout
LastUsedWidescreenLayout deprecated
LastUsedEventButton
DeblockingMode integer {0:auto, 1:enabled, 2:disabled}
H.264 deblocking, attempts to smooth sharp edges of decoded compressed video blocks
DirectSearch integer {0:disabled, 1:prefer system video, 2:prefer archive video, 3:prefer cloud video}
LastUsedLayout string
Language
Caption string
Title of the client window
ViewLayout integer
Number of panels in startup layout
LegacyAuthentication integer {0:only if required, 1:force, 2:never}
To be deprecated
TimeoutEnabled bool {0:disabled, 1:enabled}
Inactivity timeout
TimeoutMinutes integer {1-100}
KeepAliveSeconds
CurrentTheme string {light:Light, dark:Dark, classic:Classic}
DisableLiveStreams bool {0:disabled, 1:enabled}
Prevents user from viewing live video, does not affect search
Use12HourClock bool {0:disabled, 1:enabled}
TemperatureScale bool {0:Fahrenheit, 1:Celsius}
LicenseWarningAck bool {0:disabled, 1:enabled}
LicenseExpirationAck epoch
AutoCheckForClientUpdates bool {0:disabled, 1:enabled}
Found on client About pop-up
ShowNotificationsForIndicators bool {0:disabled, 1:enabled}
StartUpInstanceCount integer
Number of client instances to open
IgnoredVersion
SendAnonymousData bool {0:disabled, 1:enabled}
Found on client About pop-up
MotionColor integer {0-16777215}
Decimal color value
AlarmColor integer {0-16777215}
Decimal color value
FreeRunColor integer {0-16777215}
Decimal color value
PTZFocusColor integer {0-16777215}
Decimal color value
EventMonitorColor integer {0-16777215}
Decimal color value
BookmarkColor integer {0-16777215}
Decimal color value
NoColor integer {0-16777215}
Decimal color value
ClientIniAutoUpdateEna bool {0:disabled, 1:enabled}
Toggles automatic import on Add Systems
ClientIniAutoUpdateUrl string (path or url address to XDV file to import)
HWAccelLimit
ShowTrayIcon bool {0:disabled, 1:enabled}
Shows icon for Client instance in System Tray
See also: How to Configure No Close Client Usage
Delete bool {0:disabled, 1:enabled}
Disabling prevents Client instance closure.
See also: How to Configure No Close Client Usage

Instance Attributes

Number integer
Client instance number
Top integer (distance from top of desktop where client window begins)
Left integer (distance from left edge of desktop where client window begins)
Width integer (width of client window from left point)
Height integer (height of client window from top point)
Maximize bool {0:disabled, 1:enabled}
Client window fills screen or not
FullScreen bool {0:disabled, 1:enabled}
Fills screen and hides window controls (F11)
ShowToolbars bool {0:disabled, 1:enabled}
Hide/show toolbar (F8)
ShowNavPanel bool {0:disabled, 1:enabled}
Hide/show nav panel (F4)
LiveMode integer {0:cameras, 1:groups, 2:maps, 3:views}
Client opens with Live nav panel to the selected option
LiveModeNavButtons integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:all expanded}
Expanded or collapsed level of nav panel buttons
SearchModeNavButtons integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:views, 5:events, 6:bookmarks/cases}
Expanded or collapsed level of search panel buttons
RemoteControlEnabled bool {0:disabled, 1:enabled}
Toggles receiving of video push display
RemoteControlName string
MainSashPos integer (width of left side nav panel)
PTZControlLeft integer (distance from left edge of desktop where ptz pop-up begins)
PTZControlTop integer (distance from top edge of desktop where ptz pop-up begins)
SoftTriggerControlWidth integer (width of soft trigger pop-up from left point)
SoftTriggerControlHeight integer (height of soft trigger pop-up from top point)
SoftTriggerControlLeft integer (distance from left edge of desktop where soft trigger pop-up begins)
SoftTriggerControlTop integer (distance from top edge of desktop where soft trigger pop-up begins)
TwoWayAudioDialogWidth integer (width of two-way audio pop-up from left point)
TwoWayAudioDialogHeight integer (height of two-way audio pop-up from top point)
TwoWayAudioDialogLeft integer (distance from left edge of desktop where two-way audio pop-up begins)
TwoWayAudioDialogTop integer (distance from top edge of desktop where two-way audio pop-up begins)
RemoteControlDialogWidth integer (width of video push pop-up from left point)
RemoteControlDialogHeight integer (height of video push pop-up from top point)
RemoteControlDialogLeft integer (distance from left edge of desktop where video push pop-up begins)
RemoteControlDialogTop integer (distance from top edge of desktop where video push pop-up begins)
RemoteControlGUID string

Live Attributes

View string (name of View)
Tour string (name of Tour)
EventMonitor string (name of Event Monitoring profile)
Must be Switch View type
StartLayout

Layout Attributes

Name string (layout name)
Rows integer (number of video panel rows to allot)
Cols integer (number of video panel columns to allot)

Item Attributes

X integer (beginning column number)
Y integer (beginning row number)
Width integer (number of columns to merge)
Height integer (number of rows to merge

System Attributes

Name string (host/IP:port)

Video Attributes

Position
Name string
CameraID integer
Device string (IP address)
DeviceMac string (MAC address)
Number integer
Context
AutoContext integer
ToggleAnalytics integer

Audio Attributes

Name string
Device string (IP address)
DeviceMac string (MAC address)
Number integer
Context

Systems Attributes

Address
Port
Group
Name
AllowSave
Username
Password
PasswordType
Enabled
Latency
ExportPermission
EnterpriseManaged
UseSystemLogin
SupportsTargetSearch
IsEdgeServer
ExpandedInCamTree
FailoverState
Model
Serial
Package
Version
MAC
License
IsLicensed
IsEnterprise
IsEnterpriseEx
Expiration

Security Integrations

AlwaysPrompt bool

Sync Attributes

Enabled
ConnectedOnce
SyncFrequency
CredsSingleSignOn
CredsPrompt
Username
Password
PasswordType
UpdaterPath
UpdateCheckInterval
ForcedUpdates
Categories
Knowledge Support Support exacqVision Enterprise Products Uncategorized

Windows Firewall Rules to prevent Failover / Failback function issues

By default VFBA uses port 28774 and TCP to communicate with EM and the Server from the Spare NVR. Rules need to be configured for outbound and inbound firewall rules on the SPARE server for failback to work as expected.

To check the settings Open up Windows  Defender Firewall with Advanced Security and click on Inbound Rules on the SPARE server.

Look for a rule allowing communication on port 28774, if you do not see this in the list, then click on New Rule in the upper right hand corner in the Actions section.

Select Port and click on Next.

Select Port 28774.

Click on Next and Select Allow the connection.

Make sure all three boxes are checked.

Click on Next.
In the Name box type a name for this rule. I.E.- VFBA or evFailover, and click Finish.

Repeat this action for Outbound Rules on port 28774. It is neccessary to have both INBOUND and OUTBOUND rules configured on port 28774 on the SPARE server.

After configuring the inbound and outbound rules you can check the status by doing the following:

Open up task manager and click on the Performance Tab>Open Resource Monitor

Look at the Network Tab and under Listening Ports, verify it says Allowed and Not restricted.

Once any changes were made it is recommended that we restart the SPARE server and EM services and then check EM failover to see if the process can succeed. In some cases it may be necessary to whitelist vfba.exe and ExacqVision program components (core.exe, edvrclient.exe, including .ps and .psi file types & ExacqVision Enterprise System Manager components) when Antivirus software is in use within the configuration of your Antivirus program.

Categories
Knowledge Support Support exacqVision Client Categories Products exacqVision Integrations Uncategorized

Using the Axis A8207 Door Station with exacqVision

This article applies to the Axis A8207-VE and A8207-VE MkII Network Video Door Stations using firmware 11.5.64.

exacqVision does not currently support SIP calling functions. However, these door stations can be integrated for interactive operation with exacqVision as detailed here.


In the example that follows we will step through an example scenario wherein pressing the door station call button brings the door station camera to the attention of the exacqVision operator to trigger a door lock.

The following topics are discussed:

  • Wiring an electric door strike to the door station
  • Adding the device to exacqVision
  • Enabling Two-Way Audio
  • Adding Associations
  • Creating custom Views
  • Creating an Event Monitoring profile

You will combine several features and functions within the exacqVision Client. It is recommended that users acquaint themselves with the exacqVision Client prior to use. We provide User Training Videos on these topics.<br><br>

Wire a Door Strike

The simplest configuration is that of a single electric door strike, or maglock, wired directly to the door controller.

The Axis A8207-VE and A8207-VE MkII can be wired in a number of different ways, using PoE, external power sources, A9801 Relay, A9161 Network I/O Relay, or an Axis access control system. For more information on the many wiring and hardware configurations please refer to the manufacturer’s website or documentation. <br><br>

Add the Device

  1. You will want to use a web browser to log into the door station and perform the initial setup, which at this stage usually means setting a non-default username/password, and possibly setting a static IP address.<br><br>
  2. The call button should be enabled by default.
    <br><br>
  3. If you do not already know the IP address of the door station, you will need to discover it on the network.<br>
    • If using the Find IP Cameras tab on the Add IP Cameras page, note that you may find the device listed twice. Ignore results with a 169.254.x.x address. You will want to use the IP address in the same range as your exacqVision VMS, however this result may be discovered with ‘Onvif’ displayed in the ‘Type’ column. Access the discovered IP address in your web browser to set the username and password.
      <br><br>
  4. Add the device manually by clicking the New button under the IP Camera List in the top half of the page. Select AXIS VAPIX from the Device Type selector. Enter the IP address in the same range as your exacqVision VMS, then enter the username and password credentials before clicking Apply to add the device. The device should display a ‘Connected’ status in the IP Camera List before continuing.
    <br><br>

Enable Two-Way Audio

  1. Expand the Add IP Cameras node from the navigation tree.<br><br>
  2. Select the Audio Inputs/Outputs node nested beneath the Add IP Cameras node.<br><br>
  3. The resulting list displayed will show each door station device listed twice. Note the column, titled Audio. One of these rows shows ‘Audio,’ while the other displays ‘Audio Output.’ For easier identification we can apply our own labels here. We change ‘Audio Output’ to ‘Talk’ and change ‘Audio’ to ‘Listen.’
    <br><br>
  4. Find the Record Enable column. Place a check in the box for both of these rows for the door station. This enables two-way audio functions within exacqVision.<br><br>
  5. Press the Apply button to save your changes. Use the Talk and Listen buttons to verify audio is functioning and adjust the audio gain as desired in the door station’s web browser interface.<br><br>

IMPORTANT: Client workstations intended for use with two-way audio devices MUST have a microphone enabled. Two-way audio menus and controls are disabled or hidden until a microphone is recognized by the operating system. Each client workstation used for two-way audio must have its own microphone.<br><br>

Add Associations

You have the option of using soft triggers and audio controls from the top toolbar in live view, but these will open dialogues showing all system options. Controls that are used frequently and directly related to the specific camera being displayed in a panel may be easier for operators to use when added as Association buttons within the camera panel.

  1. Select the Associations node from the navigation tree.<br><br>
  2. The panel along the left lists existing cameras. Find and click to select the door station.<br><br>
  3. From the Available Controls panel, we select the ‘Listen’ option we relabeled earlier and click Add. There will be two controls labeled ‘Talk’ that we relabeled earlier. Select and add the one showing the microphone icon.<br><br>
  4. So that your exacqVision operators can unlock the door remotely, find and add the control labeled ‘Door.’
    Note: This control may be relabeled from within the door station’s web browser interface, but is labeled ‘Door’ by default for us.<br><br>
  5. You should now have three Associated Controls listed. You may wish to edit the Button Style listed. ‘Sustained’ requires a click on, and another click to turn off. ‘Momentary’ functions only while a user is pressing down the button which will also prevent a user from accidentally forgetting to lock the door or leaving a microphone on. You may refer to the User Manual or Associations training video for more information on customizing your Associations.<br><br>
  6. Click Apply to save your changes when done.

<br><br>

Create Custom Views

In our example we will create a View to display when triggered, rather than changing a single video panel. Learn more about these two options in the Event Monitoring training video. To make this work, we will create two custom Views to use later when creating an Event Monitoring profile. Refer to the Views training video if you need more details on performing these steps.

  1. Select the Views node from the navigation tree.<br><br>
  2. Click the New View button, then enter a descriptive name. In this example, we name our view ‘East Entry.'<br><br>
  3. Select a layout for the view from the layout toolbar above. This view may have a single panel layout showing only the camera view from the door station, or you may use a multi-panel layout displaying the door station and other cameras showing the entry from different angles.<br><br>
  4. Use the Available Items panel to find your door station camera and drag it to the empty panel in the layout. If using a multi-panel layout, fill the other panels as you like. <br><br>
  5. Because the Associations are already displayed, an exacqVision operator may easily enable/disable each when viewing in Live mode. However, if you’d like the Microphone or Speaker to be on automatically upon the view changing, you may also drag one of these onto the layout as well. Only one may be active.<br><br>
  6. Click Apply to save you changes when done.<br><br>
  7. Since we are changing the entire view displayed in Live mode, we will also want to create a view that is displayed when the door station is not in use. Repeat the steps above to create another view titled ‘Default View.’

<br><br>

Create an Event Monitoring Profile

Next you will create the Event Monitoring profile that changes the view displayed while in Live mode.

  1. Select the Event Monitoring node from the navigation tree.<br><br>
  2. Click the New button under the Profiles panel to begin creating a new profile.<br><br>
  3. Enter a descriptive Name under the Profile Configuration panel. Our example will name this ‘East Entry’ for the door where it is being placed.<br><br>
  4. The option you select for the Show Event List menu will depend on your intended use.
    • Never is the less obtrusive option as it hides the Event List from popping up in our view. The trade off for this is you will probably want to set Timeout later so the View changes back to the default display after a given amount of time. Without this, the displayed View will remain on the door station camera.
    • On Event will pop open the Event List window which some users do not like. However, the benefit of this is the exacqVision user can decide when to return to the default View and the View will not change in the middle of being used simply because a timer ended. When the event is cleared the Event List window will disappear.
    • Always will always be displayed whether or not the door station is being utilized.<br><br>
  5. Checking the Show Newest Event box is optional. This feature is most useful when many possible events are included in an Event Monitoring profile. An example may be a site with multiple door stations, in which case checking this box will change the view to display the station with the most recently pressed Call Button.<br><br>
  6. As mentioned previously, this example will use ‘View’ from the Type field. Refer to the Event Monitoring training video for more on the ‘Video Panel’ option, which does not require creating custom Views.<br><br>
  7. Under Client Actions in the middle of the window is where you will create the actions that occur when triggered by various events. Our first row, currently labeled ‘Unknown’ should already be highlighted because we are creating a new profile.<br><br>
  8. From the Event Type panel list below, select ‘Default’.<br><br>
  9. From the Action Type panel list, select Switch View. Note that you could also opt to make your default display a Tour, which is covered in the Tours training video.<br><br>
  10. From the Action Target panel list, select the default View you created earlier.<br><br>
  11. Click the New button under the Client Actions panel in the middle of the window. This adds a new row to configure.<br><br>
  12. With the newly created row highlighted, select Input Trigger from the Event Type list.<br><br>
  13. The door station has already named the input for you. Locate the door station in the list. It has several inputs, select the one labeled ‘Call button’. Do not enable the ‘Lasts at Least’ checkbox.<br><br>
  14. From the Action Type list, select Switch View.<br><br>
  15. From the Action Target list, select the door station View you created earlier. In our example we named this ‘East Entry’.<br><br>
  16. Your next choice will depend on the option you selected from the Show Event List, in step 4, above.
    • If you chose Never and want the Live view to return to your default view after a set number of seconds, uncheck the Confirm box and set your Timeout as desired.
    • If you chose On Event or Always and want to allow your exacqVision users to acknowledge the event to return to the default view, leave the Confirm box checked.<br><br>
  17. Click the Apply button to save your changes when done.

<br><br>

Handling Calls From exacqVision

  1. Using the exacqVision Client software, browse to Live mode.<br><br>
  2. By default, the panel along the left side of the window displays a list of Live Cameras. Using the options at the bottom select Views to update this panel to Live Views.<br><br>
  3. The Live navigation panel lists System Views, User Role Views, User Views, and System Tours, which includes any Views created earlier in the process of configuring our profile. Towards the bottom is a list of Event Monitors.
    <br><br>
  4. Find the name of the Event Monitoring profile you created. Again, our example was named ‘East Entry’. Drag this profile to the cameras panel to the right.<br><br>
  5. You should now be viewing your default View. When the Call Button on the door station is pressed the View will change to display the door station camera view you created earlier.<br><br>
  6. The Association icons we added earlier can be seen at the bottom corner. The door station will continue to ring until an exacqVision user presses the Talk button or the configured ring timeout is reached.
    <br><br>
  7. Press the Talk button to transmit audio from your client workstation microphone to speak to door station users. Press the Listen button to hear door station users speaking.

    Note: Audio from Talk and Listen actions may be buffered, presenting a delay. Practice with the system to gain a feel for this on your network.<br><br>
  8. If you have correctly wired a door strike, maglock, or other electronic locking mechanism to the door station, pressing the icon for the output will unlock the door.

    Note: Door controls may be customized within the door station’s web browser interface.<br><br>

Door Station Visitor Operation

  • A visitor using the door station may simply press the Call Button to activate the Event Monitoring profile, as created above.<br><br>
  • The use case detailed in this article does not prevent the door station from being used for SIP calls.

    Once a SIP server has been configured within the door station’s web browser interface, a SIP call is initiated by dialing a designated SIP extension number prior to pressing the Call Button.

    Note: When used together with SIP, any press of the Call Button will trigger the Event Monitoring profile regardless of whether it was used when dialing an extension number or not.<br><br>

<br>

Categories
Software Downloads Software Categories Lenel Categories Products Uncategorized exacqVision Integrations

Lenel OnGuard version 6.3 and 6.4

exacqVision plug-in for Lenel OnGuard Version 6.3 and 6.4^Version 2.0.1^https://exacq.s3.us-east-1.amazonaws.com/Lenel/exacq-lenel_03_2011.zip^18 September 2014^4.7MB,

Categories
exacqVision Client Windows x64 Software Downloads Software Categories exacqVision Client Categories Products Uncategorized

ExacqVision Client Windows x64 Legacy Versions

{2024}

Q2 2024-08-15 ev-Client-Windows-x64^Version 24.06.2.0^https://exacq.com/public/24.06/exacqVisionClient_24.06.2.0_x64.exe^15 August 2024^144MB,

Q1 2024-04-16 ev-Client-Windows-x64^Version 24.03.4.0^https://cdnpublic.exacq.com/24.03/exacqVisionClient_24.03.4.0_x64.exe^16 April 2024^144MB,

{2023}

Q4 2023-11-20 ev-Client-Windows-x64^Version 23.09.7.0^https://cdnpublic.exacq.com/23.09/exacqVisionClient_23.09.7.0_x64.exe^20 November 2023^138MB,

Q2 2023-06-15 ev-Client-Windows-x64^Version 23.06.2.0^https://cdnpublic.exacq.com/23.06/exacqVisionClient_23.06.2.0_x64.exe^30 June 2023^138MB,

Q1 2023-03-15 ev-Client-Windows-x64^Version 23.03.1.0^https://cdnpublic.exacq.com/23.03/exacqVisionClient_23.03.1.0_x64.exe^8 March 2023^138MB,

{2022}

Q4 2022-12-15 ev-Client-Windows-x64^Version 22.12.2.0^https://cdnpublic.exacq.com/22.12/exacqVisionClient_22.12.2.0_x64.exe^13 December 2022^138MB,

Q3 2022-09-15 ev-Client-Windows-x64^Version 22.09.3.0^https://cdnpublic.exacq.com/22.09/exacqVisionClient_22.09.3.0_x64.exe^15 September 2022^140MB,

Q2 2022-06-15 ev-Client-Windows-x64^Version 22.06.3.0^https://cdnpublic.exacq.com/22.06/exacqVisionClient_22.06.3.0_x64.exe^13 June 2022^137MB,

Q1 2022-03-15 ev-Client-Windows-x64^Version 22.03.1.0^https://cdnpublic.exacq.com/22.03/exacqVisionClient_22.03.1.0_x64.exe^8 March 2022^137MB,

{2021}

Q4 2021-12-15 ev-Client-Windows-x64^Version 21.12.2.0^https://cdnpublic.exacq.com/21.12/exacqVisionClient_21.12.2.0_x64.exe^14 December 2021^123MB,

Q3 2021-09-15 ev-Client-Windows-x64^Version 21.09.5.0^https://cdnpublic.exacq.com/21.09/exacqVisionClient_21.09.5.0_x64.exe^30 September 2021^124MB,

Q2 2021-06-15 ev-Client-Windows-x64^Version 21.06.5.0^https://cdnpublic.exacq.com/21.06/exacqVisionClient_21.06.5.0_x64.exe^23 June 2021^123MB,

Q1 2021-03-15 ev-Client-Windows-x64^Version 21.03.4.0^https://cdnpublic.exacq.com/21.03/exacqVisionClient_21.03.4.0_x64.exe^11 March 2021^141MB,

{2020}

Q4 2020-12-15 ev-Client-Windows-x64^Version 20.12.4.0^https://cdnpublic.exacq.com/20.12/exacqVisionClient_20.12.4.0_x64.exe^13 January 2021^124MB,

Q3 2020-09-15 ev-Client-Windows-x64^Version 20.09.3.0^https://cdnpublic.exacq.com/20.09/exacqVisionClient_20.09.3.0_x64.exe^11 September 2020^123MB,

Q2 2020-06-15 ev-Client-Windows-x64^Version 20.06.4.0^https://cdnpublic.exacq.com/20.06/exacqVisionClient_20.06.4.0_x64.exe^11 August 2020^122MB,

Q1 2020-03-15 ev-Client-Windows-x64^Version 20.03.6.0^https://cdnpublic.exacq.com/20.03/exacqVisionClient_20.03.6.0_x64.exe^21 April 2020^122MB,

{2019}

Q4 2019-12-15 ev-Client-Windows-x64^Version 19.12.4.0^https://cdnpublic.exacq.com/19.12/exacqVisionClient_19.12.4.0_x64.exe^13 December 2019^109MB,

Q3 2019-09-15 ev-Client-Windows-x64^Version 19.09.8.0^https://cdnpublic.exacq.com/19.09/exacqVisionClient_19.09.8.0_x64.exe^8 October 2019^108MB,

Q2 2019-06-15 ev-Client-Windows-x64^Version 19.06.6.160676^https://cdnpublic.exacq.com/19.06/exacqVisionClient_19.06.6.160676_x64.exe^1 August 2019^108MB,

Q1 2019-03-15 ev-Client-Windows-x64^Version 19.03.8.153179^https://cdnpublic.exacq.com/19.03/exacqVisionClient_19.03.8.153179_x64.exe^22 March 2019^124MB,

{2018}

Q4 2018-12-15 ev-Client-Windows-x64^Version 9.8.4.150001^https://cdnpublic.exacq.com/9.8/exacqVisionClient_9.8.4.150001_x64.exe^10 January 2019^123MB,

Q3 2018-09-15 ev-Client-Windows-x64^Version 9.6.3.143138^https://cdnpublic.exacq.com/9.6/exacqVisionClient_9.6.3.143138_x64.exe^20 September 2018^120MB,

Q2 2018-06-15 ev-Client-Windows-x64^Version 9.4.2.136542^https://cdnpublic.exacq.com/9.4/exacqVisionClient_9.4.2.136542_x64.exe^22 June 2018^119MB,

Q1 2018-03-15 ev-Client-Windows-x64^Version 9.2.2.129658^https://cdnpublic.exacq.com/9.2/exacqVisionClient_9.2.2.129658_x64.exe^28 March 2018^118MB,

{2017}

Q4 2017-12-15 ev-Client-Windows-x64^Version 9.0.3.124656^https://cdnpublic.exacq.com/9.0/exacqVisionClient-9.0.3.124656_x64.exe^8 January 2018^119MB,

Q3 2017-09-15 ev-Client-Windows-x64^Version 8.8.1.119433^https://cdnpublic.exacq.com/8.8/exacqVisionClient-8.8.1.119433_x64.exe^14 September 2017^118MB,

Q2 2017-06-15 ev-Client-Windows-x64^Version 8.6.1.115131^https://cdnpublic.exacq.com/8.6/exacqVisionClient-8.6.1.115131_x64.exe^14 June 2017^73.9MB,

Q1 2017-03-15 ev-Client-Windows-x64^Version 8.6.1.115131^https://cdnpublic.exacq.com/8.4/exacqVisionClient-8.4.2.111578_x64.exe^14 June 2017^78.5MB,

{2016}

Q4 2016-12-15 ev-Client-Windows-x64^Version 8.2.2.108645^https://cdnpublic.exacq.com/8.2/exacqVisionClient-8.2.2.108645_x64.exe^25 January 2017^78.3MB,

Q3 2016-09-15 ev-Client-Windows-x64^Version 8.0.7.105361^https://cdnpublic.exacq.com/8.0/exacqVisionClient-8.0.7.105361_x64.exe^3 November 2016^76.5MB,

Q2 2016-06-15 ev-Client-Windows-x64^Version 7.8.1.98221^https://cdnpublic.exacq.com/7.8/exacqVisionClient-7.8.1.98221_x64.exe^13 June 2016^76.2MB,

Q1 2016-03-15 ev-Client-Windows-x64^Version 7.6.4.94409^https://cdnpublic.exacq.com/7.6/exacqVisionClient-7.6.4.94409_x64.exe^30 March 2016^76.1MB,

{2015}

Q4 2015-12-15 ev-Client-Windows-x64^Version 7.4.1.89736^https://cdnpublic.exacq.com/7.4/exacqVisionClient-7.4.1.89736_x64.exe^11 December 2015^62.7MB,

Q3 2015-09-15 ev-Client-Windows-x64^Version 7.2.4.87479^https://cdnpublic.exacq.com/7.2/exacqVisionClient-7.2.4.87479_x64.exe^30 October 2015^60.2MB,

Q2 2015-06-15 ev-Client-Windows-x64^Version 7.0.1.81045^https://cdnpublic.exacq.com/7.0/exacqVisionClient-7.0.1.81045_x64.exe^10 June 2015^58.8MB,

Q1 2015-03-15 ev-Client-Windows-x64^Version 6.8.3.76558^https://cdnpublic.exacq.com/6.8/exacqVisionClient-6.8.3.76558_x64.exe^13 March 2015^56.6MB,

Categories
Configuration Knowledge Support Documentation exacqVision Enterprise Support exacqVision Client exacqVision Server Products exacqVision Integrations Uncategorized

Enterprise Manager supports LDAP authentication with Azure Active Directory 

Azure Active Directory supports the LDAP interface when properly configured, and therefor LDAP can be used to sync the ExacqVision Enterprise Manager software with the Azure AD instance.

Background Information: Lightweight Directory Access Protocol (LDAP) is an application protocol for working with various directory services. Directory services, such as Active Directory, store user and account information, and security information like passwords. The service then allows the information to be shared with other devices on the network. Enterprise applications such as email, customer relationship managers (CRMs), Video Management Software (VMS – ExacqVision), and Human Resources (HR) software can use LDAP to authenticate, access, and find information.

Azure Active Directory ( sometimes referred to as Azure AD) supports this pattern via Azure AD Domain Services (sometimes referred to as AD DS). This allows organizations that are adopting a cloud-first strategy to modernize their environment by moving off their on-premises LDAP resources to the cloud. ExacqVision has supported the use of LDAP authentication since early versions, and now has been enhanced to support the use of LDAP authentication when integrated with Azure Active Directory as a modern solution to cloud based computing.

When a network hosting Enterprise Manager on-premise has been properly configured for communication with an Azure Active Directory instance by verifying no port restrictions or other environmental variables inhibit communication – ExacqVision Enterprise Manager has the ability to support the use of LDAP authentication with Azure Active Directory as of December 15th, 2022 – and subsequent releases thereafter.  

Products 

  • ExacqVision Enterprise Manager version 22.12.0.0 and up

Minimum Requirements for ExacqVision Enterprise Manager Software: 

  • Enterprise Manager version must be 22.12.0.0 or later
  • Your network configuration must be properly configured to communicate with your Azure AD instance
  • you must have Azure Active Directory credentials with access to the following Active Directory parameters – as supplied by your Local IT Department or Network Administrator: objectClass (specifically “group” & “user”), userPrincipalName , sAMAccountName , inetOrgPerson , krbPrincipalName

Configuration Steps for Enterprise Manager: 

  • Properly configure the network to communicate with Azure Active Directory instance without restriction.
  • Verify you possess the minimum credential requirements needed to complete the integration as listed above (supplied by your Local IT Department or Network Administrator) and login to Enterprise Manager user interface with administrative privileges
  • Navigate to the Domain settings page
  • Under “Add Domain” enter the address of the Azure Active Directory instance in the “Hostname or IP” field and enter the above mentioned credential criteria with the proper port number, security protocol, Search Criteria information, and Attribute names information in their corresponding fields – as supplied by your Local IT Department or Network Administrator
  • Apply the changes.

Expected Results 

The above steps when executed properly will sync with the Azure AD Instance, allowing LDAP authentication in ExacqVision Enterprise Manager.

For more information on how to configure ExacqVision Enterprise Manager for use with LDAP authentication please see the ExacqVision Enterprise Manager user manual.