Categories
Knowledge Support Configuration Support exacqVision Webservice Categories Products

Creating a Self-Signed SSL Certificate

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:
    1. Navigate to http://gnuwin32.sourceforge.net/packages/openssl.htm
    2. Under the ‘Download’ section, click the link labeled ‘Zip’ beside the row labeled ‘Binaries’.
    3. After downloading, extract (unzip) the contents of this file.
    4. 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

  1. Open a CMD window.
  2. Navigate into the unzipped directory, then into the ‘bin’ directory in which the recently extracted OpenSSL executable resides.
  3. 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
  4. 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).
  5. 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.
      1. Log in to your Web Service Configuration page
      2. Expand the Configuration menu
      3. Click HTTPS
      4. Click Configure
      5. Select External and import your generated .crt and .key files.
      6. Apply the changes
      7. Click the link to restart the web service
    • 3.0 to 8.2: use the file explorer and CMD
      1. place the files in the following directory
        C:\Program Files[ x86 ]\exacqVision\WebService\Apache\conf
      2. Using CMD, stop the web service: net stop webservice
      3. Using CMD, start the web service: net start webservice

Linux Procedure

  1. Open a Terminal window
  2. Create a self-signed certificate by entering the following command:
    openssl req -new -x509 -sha256 -days 365 -nodes -out server.crt -keyout server.key
  3. 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).
  4. 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.
      1. Log in to your Web Service Configuration page
      2. Expand the Configuration menu
      3. Click HTTPS
      4. Click Configure
      5. Select External and import your generated .crt and .key files. Apply the changes
      6. Click the link to restart the web service
    • 3.0 to 8.2: use the file explorer and Terminal
      1. place the files in the following directory
        /etc/evapache
      2. Using Terminal, restart the web service:
        sudo /usr/local/exacq/webservice/service.sh restart
Categories
Knowledge Support Cloudvue Support Categories Products

Migrating or Recovering a Cloudvue Tunneling Machine

Description

Use the following instruction to recover your tunneling machine or migrate  to a new one

Assumptions

  • Your old tunneling machine was configured and working
  • You know the hostname of your old tunneling machine
  • You have a copy of the following files from your old tunneling machine
    • ~/.ssh/id_rsa
    • ~/.ssh/id_rsa.pub

Solution

  • Create a new tunneling Machine
  • See KB#13051 “Cloudvue SSH Tunneling” for instructions and recommendations
  • Copy both of these files from the old tunneling machine onto the new one
    • ~/.ssh/id_rsa
    • ~/.ssh/id_rsa.pub
  • Change the hostname of the new tunneling server to match the hostname of the old tunneling server

Example

Display hostname

$ hostnamectl

Static hostname: Your-Virtual-Machine
Icon name: computer-vm
Chassis: vm Machine ID: 54acc6559a574f06b8b66a7f7ffe90a4
Boot ID: 71d58b5f2ebc40969b795e25392425c3
Virtualization: microsoft Operating System:
Ubuntu 22.04.2 LTS
Kernel: Linux 5.19.0-35-generic
Architecture: x86-64
Hardware Vendor: Microsoft Corporation
Hardware Model: Virtual Machine

Change hostname

$ sudo hostnamectl set-hostname


Pro Tip:  Quick recovery hinges on you having a backup of both, id_rsa and id_rsa.pub , and a record of the hostname of your tunneling machine

Categories
Sales Materials Storage Calculator Cloudvue Cloudvue Cameras Documentation Categories Products

Test Storage Calculator

Categories
Knowledge Support Video Library Release Notes Demo exacqVision Enterprise Support exacqVision Client Other exacqVision Server exacqVision Webservice Categories Products exacqVision Integrations

2023-03 March Quarterly Release Training

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

Categories
Plugin Exclude from Global Search Log Level exacqVision Enterprise Warning Logs Other

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

Description

when the Datarolloff service is failing to start you may see this error or a similar error in the datarolloff log file. There is a foreign key constraint that is failing to delete which in turns stops the service from running, you must delete this constraint manually via the Database

Notes

You must delete the key constraint from the database

Categories
Knowledge Support Support exacqVision Client Products

Login failed “LDAP User is not authorized.”

Description 

When trying to log into the Exacq Client with a LDAP user you get a “Login failed User is not authorized” error. This is due to the User not being queried and mapped to a user role in the Users section of the client.

Product 

  • exacqVision Client

Version

All Versions

Solution

You must search and query for the LDAP user in the Users section in the Client, you must also map the user to a user role.

Categories
User Guides Cloudvue Documentation Categories Products

Cloudvue User Manual cv22.4.0.6

CV-User-Guide-22.4.0.6.pdf
Categories
Knowledge Support Cloudvue Support Cloudvue Access Control Categories

Unable to Validate Mobile Phone in Cloudvue Access to Multiple Accounts

Title

Unable to Validate Mobile Phone to Multiple Accounts

Description 

Currently a Mobile Phone can only be validated to a single account.  Attempts to validate to a 2nd account will fail.

Product 

  • Cloudvue Access iOS
  • Cloudvue Access Android

Solution

Remove the mobile credentials from the current Account. The phone will then validate on the new Account.

Note: It can take many minutes for the deletion to take effect

See AES-370 for additional details

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories

Manually Calculating the SSH Password for a Cloudvue Device

*** INTERNAL USE ***

Description 

The following instructions can be used to manually calculate the ssh password for a Cloudvue video device.

Product 

  • Cloudvue Gateway
  • C2C

Solution

Cloudvue Gateway

The ssh password is the first 32 characters of the MD5 Hash returned when using the following combination

MAC + Version + 3cadcddd84a94e1014f6a9bfeeecfd6

Where MAC is the MAC address of the device in all CAPS and Version is the version of Cloudvue Software the gateway is running

Linux

$ echo -n AC1F6BB04DDC22.9.0a3cadcddd84a94e1014f6a9bfeeecfd6 | md5sum | cut -c 1-32 8d30ee28cc2e0a736e4da9568a3a2367
$ 8d30ee28cc2e0a736e4da9568a3a2367

C2C

The ssh password, while similar to the Cloudvue Gateway, uses only the first 16 characters of the MD5 Hash returned when using the following combination

MAC + Version + 3cadcddd84a94e1014f6a9bfeeecfd6

Where MAC is the MAC address of the device in all CAPS and Version is the version of Cloudvue Software the C2C device is running

Linux

$ echo -n 0050F96C05B122.9.0a3cadcddd84a94e1014f6a9bfeeecfd6 | md5sum | cut -c 1-16
$ 47fae762f9ff87bc
Categories
Knowledge Support Cloudvue Support Categories

Cloudvue Analytics & Intelligence

Description

Cloudvue Intelligence provides access to whatever data analytics a particular camera may provide such as people and vehicle detection. Except for Motion, People and Vehicle Detection the camera must provide the desired analytic.

Products

  • Cloudvue Intelligence
  • C2C Cameras
  • C2G Cameras

Solution

Except for Motion, People Detection and Vehicle Detection, which are native to Cloudvue Intelligence, customers wanting to take advantage of  any of the other Intelligence features must ensure that the camera itself provides the desired analytic and the appropriate subscription has been applied.

NOTE:  The Cloudvue Intelligence feature is only available through the cloud interface.

Analytic Types and Descriptions

Cloudvue provides the following analytics natively but does require a “TCSVMSM – VMS Only” or greater subscription

Data TypeDescription
MotionDisplays a graph of detected motion for people or vehicles and can be set to daily or weekly.
People DetectionUsed to determine a human presence in the camera’s field of vision. This  feature must be enabled in the Settings before use
Vehicle DetectionUsed to determine a vehicle’s presence in the camera’s field of vision. This feature must be enabled in the Settings before use.

Cloudvue also supports the following analytics if provided by the camera and having a retention subscription

Data TypeDescription
People CountingDisplays a graph of the number of people entering, exiting, or both; and can be  set to daily, weekly, or monthly.
Heat MapsDisplays colored maps showing areas with frequent motion. The display can be set in intervals of 5 minutes to 24 hours.
Object Left BehindDisplays the number of events for an object left behind.
Object DetectionDisplays the number of events for detecting a known object.
LingerDisplays the number of events for linger. Linger is the duration of time a person stays within and around a defined area. It may also count a person walking around the area as lingering.
DwellDisplays the number of events for dwelling. Dwelling is the duration of time a person stays inside a defined area.
EnterDisplays the number of events for entering a defined area.
ExitDisplays the number of events for exiting a defined area.
CrowdDisplays the number of events for a crowd formation. Crowd formations specify the number of people necessary to constitute a crowd within a specific detection area.
QueueDisplays the number of events for queue formation. Queue formations specify the number of people necessary to form a line.
ThermalDisplays thermal imaging for infrared cameras for a given date and time

Additional Information

For a general explanation of Analytics and Intelligence see  Security Analytics & Intelligent Alerts Explained