A walk through, how-to video on connecting analog audio base stations from Louroe to ExacqVision Hybrid NVRs.<br><br>
See also: Line Level vs Mic Level Audio for more details on the differences in these audio signals from various devices.
<br>
Category: Video Library
This video shows example diagrams on wiring a Kantech ioSmart reader to the KT-1 and KT-1 PCB single-door controllers.
The diagrams displayed in the video can also be viewed below.
<br>
ExacqVision Server
Bug Fix – Fixed excessive Archiving status messages (AESW-4989)
Bug Fix – Debian installer no longer enabled eventpi by default
Bug Fix – Fixed issue capturing all metadata when multiple events are sent as one alarm
Bug Fix – Ensure eventpi database is purged after server reboot
Bug Fix – Fixed connection status problem from Axis cameras with older firmware
Bug Fix – Prevent needing to restart client after adding Axis body worn camera system, caused by receiving cert before configuration (AESW-3445)
Bug Fix – Fixed potential streaming issue from Exacq’s RTSP Server resulting in gaps (AESW-5251)
Bug Fix – Fixed problem where time triggers were not firing on some days (AESW-4573)
Bug Fix – Fixed socket crash from Bosch intrusion plugin (AESW-5105)
Bug Fix – Fixed a problem with stale metadata for Illustra3 and Illustramulti plugins
Bug Fix – Restart the SSL session and restart metadata on error 94 from Illustra3 and Illustramulti plugins (AESW-4574)
Bug Fix – Corrected issue with missing codecs from Panasonic camera plugin causing them to default to JPEG (AESW-631)
Bug Fix – Fixed issue with motion issues on some Panasonic cameras (AESW-4794)
Bug Fix – Fixed problem with issue making settings changes to Panasonic multisensor (AESW-4562)
Enhancement – Improvements made to search results returned for audio/video events
Enhancement – Improved loading time of eventpi
Enhancement – Cameras previous detected as Samsung are now detected as Hanwha Vision
(AESW-5539, AESW-5538)
Enhancement – Added Hanwha Vision option (AESW-5189)
Enhancement – Integration of WiseAI analytics from Hanwha
Enhancement – Enhanced camera discovery for new Illustra Flex Dual Sensor camera (AESW-5541)
Enhancement – Server installer no longer checks Illustrapi or Illustraflexpi for install by default
Enhancement – Changed the reported name to “Illustra Multisensor”
Enhancement – Added legacy tag to Illustrapi and Illustraflexpi
Enhancement – Added support for Axis “Optics Control” autofocus (AESW-2649)
Enhancement – Added support for Bosch “RuleEngine” analytics (AESW-1326)
ExacqVision Client
Bug Fix – wxWidgets version upgrade
New installs, not upgrades, automatically select dark or light theme based on the OS theme and prevent user changes
(AESW-5146)
Enhancement – Copy selected camera information when adding a new camera
If camera is highlighted in IP Cameras List on the Add Cameras page when the New button is clicked, the Device Type field will automatically populate with the same as that which was highlighted saving time from selecting from Device Type list.
(AESW-5855)
ExacqVision Web Service
Bug Fix – Updated nvrg version to fix group type retrieval, fixes issue with group items (AESW-3340)
Bug Fix – Updated nvrg version to fix a soft trigger bottleneck, fixes issue where triggers from web or mobile client resulted in status flickering between ‘Alarm’ and ‘Normal’ in Desktop Client. (AESW-3816)
ExacqVision Enterprise Manager
Bug Fix – Improved logging for DynamicDNS files for Integrator Service Portal (AESW-5897)
<br>
With Artificial Intelligence being used more often users may notice a spike in the analytic metadata being processed and stored. Here are our recommendations to manage this increase.
Update exacqVision Server/Client Software
- Ensure you are running the latest version of both exacqVision Server and Client software.
- Search “updating” in the exacqVision Client User Manual, available Here for information on updating.
Adjust Camera Settings
- Access Analytics from the camera’s configuration GUI page
- Only those analytic types required by the customer should be enabled
- The goal is to keep this setting as minimal as possible, while still achieving the customers goals.
Reduce DB retention period
- Reduce ‘Maximum Days to Keep Bounding Box Metadata’ available in exacqVision Server/Client 23.09 and higher. See: Maximum Days to Keep Bounding Box Metadata Explained
- Reduce the ‘Maximum Days to Keep Logged Events’
- These settings decide when older items should be removed or “Purged” from the Database (eventPI), the lower the value, the less storage needed.
- It is recommended to set this value as low as possible and adjust based on available storage when data is processing
- Customer retention requirements must also be considered.
Disable Analytics
- Each camera is different, but if the user does not have enough storage for 24 hours of analytics, or if analytics are not needed, currently the best option is to disable the analytics completely.
- Within the exacqVision Client software, go to Configuration → Server → Configure System → Add IP Cameras → Camera Recording → Analytics Camera → Analytics tab – Uncheck “Record analytic data”
Related Articles
- Artificial Intelligence Object Classification Event Triggers Filling OS Drive
- Maximum Days to Keep Bounding Box Metadata Explained
AESW-5987
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.
Using the Illustra Tools Mobile App to discover, connect to, and configure cameras
Issue
When system reboots and boots up to recovery mode it selects “Factory Capture” by default leading the system to commit a full factory restore upon pressing “enter”.
Solution
Windows
- Open CMD, using Run as Administrator
- Enter
mountvol z: /s - Enter
z: - Enter
dir - Enter
cd EFI/BOOT - Enter
notepad refind.conf - Search for the default_selection entry
- Set the parameter to “1” instead of “factory restore”
- Save your changes and reboot the NVR
<br>
Linux System
The file at ‘/boot/efi/EFI/BOOT/refind.conf’ will need to be edited in the same way it is for the Windows instructions. Instead we would follow these steps:
- Open Terminal (CTRL+ALT+T)
- Enter
sudo -i - Enter
caja(this should open a file explorer type window) - Navigate to /boot/efi/EFI/BOOT/refind.conf
- Right-click and open file a text editor
- Edit the text as shown in Step 6 of the Windows instructions above.
- Save your changes, close the file, and restart the system
<br>
Before Beginning…
- Self-signed certificates are NOT secure. It is recommended to use Let’s Encrypt (configurable via the web service UI) if you do not wish to pay for the cost of a trusted HTTPS certificate.
- A self-signed certificate allows you to use a web browser, but does not work with mobile devices. Only trusted third-party certificates work with mobile devices.
- This document assumes that ExacqVision Web Service 3.0 or later has been installed with the default settings.
Requirements
You will need the OpenSSL program to create a self-signed certificate. The method of obtaining this program varies based on the operating system used.
- Linux – OpenSSL is included by default on all modern Ubuntu distributions. If for any reason it is not, run:
sudo apt-get install openssl
in a Terminal window and follow the prompts.
- Windows – The easiest way is to obtain a pre-compiled executable from SourceForge:
- Navigate to http://gnuwin32.sourceforge.net/packages/openssl.htm
- Under the ‘Download’ section, click the link labeled ‘Zip’ beside the row labeled ‘Binaries’.
- After downloading, extract (unzip) the contents of this file.
- The executables extracted may then be run independently without installation. OpenSSL.exe is located within the ‘bin’ folder of the extracted Zip file contents. The following procedures explain how to continue.
Note: A certificate generated on either platform will work on the other
(i.e.- a certificate generated using openssl on Linux can be used with a Windows web service).
Windows Procedure
- Open a CMD window.
- Navigate into the unzipped directory, then into the ‘bin’ directory in which the recently extracted OpenSSL executable resides.
- Create a self-signed certificate by typing the following:
openssl.exe req -new -x509 -sha256 -days 365 -nodes -out server.crt -keyout server.key -config ..\share\openssl.cnf - When running this command you will be prompted to enter several fields. Answer the questions according to your needs. COMMON NAME should be the IP address or FQDN that you use to access your ExacqVision Web Service (www.domain.com).
- Place the resulting files (server.crt, server.key) according to your ExacqVision Web Service version:
- 8.4 and above: Use the web service configuration interface to configure HTTPS using the generated files.
- Log in to your Web Service Configuration page
- Expand the Configuration menu
- Click HTTPS
- Click Configure
- Select External and import your generated .crt and .key files.
- Apply the changes
- Click the link to restart the web service
- 3.0 to 8.2: use the file explorer and CMD
- place the files in the following directory
C:\Program Files[ x86 ]\exacqVision\WebService\Apache\conf - Using CMD, stop the web service: net stop webservice
- Using CMD, start the web service: net start webservice
- place the files in the following directory
- 8.4 and above: Use the web service configuration interface to configure HTTPS using the generated files.
Linux Procedure
- Open a Terminal window
- Create a self-signed certificate by entering the following command:
openssl req -new -x509 -sha256 -days 365 -nodes -out server.crt -keyout server.key - When running this command you will be prompted to enter several fields. Answer the questions according to your needs. COMMON NAME should be the IP address or FQDN that you use to access your ExacqVision Web Service (www.domain.com).
- Place the resulting files (server.crt, server.key) according to your ExacqVision Web Service version:
- 8.4 and above: Use the web service configuration interface to configure HTTPS using the generated files.
- Log in to your Web Service Configuration page
- Expand the Configuration menu
- Click HTTPS
- Click Configure
- Select External and import your generated .crt and .key files. Apply the changes
- Click the link to restart the web service
- 3.0 to 8.2: use the file explorer and Terminal
- place the files in the following directory
/etc/evapache - Using Terminal, restart the web service:
sudo /usr/local/exacq/webservice/service.sh restart
- place the files in the following directory
- 8.4 and above: Use the web service configuration interface to configure HTTPS using the generated files.
ExacqVision Server
Bug Fix – Fixed PTZ preset administration for custom users to create presets for analog cameras (AESW-4357)
Bug Fix – Fixed monitoring RAID background tasks, like consistency checks and background initialization (AESW-4387)
Bug Fix – Fixed reporting incorrect RAM, was displaying MB instead of GB (AESW-2498)
Bug Fix – actipi – Reduce metadata channel reconnects for cameras with S3L chips, this caused cameras to stop recording after a while (AESW-4327)
Bug Fix – illustramultipi – Fixed ability to enable motion zones per sensor, accommodated changed to camera firmware (AESW-4456)
Bug Fix – illustramultipi – Fixed direct input/output triggers, fixed output numbering that was preventing trigger status from updating (AESW-3474)
Bug Fix – onvifnvcpi – Fixed motion issues with AVCostar-Contera (AESW-4464)
Bug Fix – onvifnvcpi – Increased maximum SOAP read size to accommodate Clinton encoders, see Enhancements (AESW-3474)
Enhancement – Modified all emissions from eventpi and notifypi to use separated IDs rather than compressed IDs, fixed in part, this is an enhancement to affect problems with searching the event database with very large amounts of records (AESW-3333)
Enhancement – Added camera detection of several Illustra Standard cameras to be discovered as Illustra3
(AESW-1668)
Enhancement – axispi – Added support for color metadata (AESW-1725)
Only vehicle color is currently provided by Axis
Enhancement – illustra3, illustramultipi – Added support for “final color” (AESW-2850, AESW-2844)
Enhancement – samsungpi – Added support for Area Zoom (AESW-4003)
Enhancement – onvifnvcpi – Added support for Advidia cameras (AESW-3521)
Enhancement – onvifnvcpi – Added support for Clinton Electronics encoder (AESW-2489)
ExacqVision Client
Bug Fix – Don’t reorder keywords when building conditions panel tree
Ensures ‘Upper Clothing Color’ is listed above ‘Lower Clothing Color’ in Filters (AESW-4502)
Bug Fix – Allow live analytic keyword colors to be processed before bounding boxes (AESW-4458)
Bug Fix – Fixed an issue with display of multiple trigger events (AESW-3861)
Bug Fix – Fixed issue saving image from Live view where OSD background color was removed from the saved image (AESW-4277)
Enhancement – Support for “final color”, choose search type based on “final color” (AESW-3345)
ExacqVision Web Service
Bug Fix – Updated nvrg version to fix group type retrieval (AESW-3340)
Bug Fix – Updated nvrg version to fix a soft trigger bottleneck (AESW-3816)
Enhancement – Disabled search playback in browser client until buffer threshold is reached (AESW-3622)
Enhancement – Enabled ability to detect an invalid session in browser client (AESW-3621)
ExacqVision Enterprise Manager
Bug Fix – Removed architecture change logic from NSIS (AESW-491)
Bug Fix – Support added for Windows authentication login for MS-SQL (AESW-3378)
Illustra
Enhancement – New Pro Gen4 6.0 firmware adds new Object Classes
Trolley, Backpack, Handbag, Suitcase
Enhancement – Improved face detection
Enhancement – “Final color” sent after object tracked leaves FOV
IMPORTANT: This video was made for BWC Kiosk Software version 1.x and was deprecated upon release of version 2.x
This video is for internal support training and includes Troubleshooting information towards the end, beginning at the 15:00 mark.
<br>