Category: exacqVision Client

Categories
User Guides Knowledge Support Documentation Highlighted Support exacqVision Client exacqVision Server Categories Products

Deprecation of Legacy Installers – exacqVision 24.03 Update

As part of the exacqVision 24.03 software release, we are announcing the deprecation of specific installers that were previously part of the collection of software downloads available on the Exacq web site, https://exacq.com.

What installers are being retired?

On both Windows and Ubuntu – the 32-bit installers, also known as “x86” installers, of server, client, and web service will no longer be made available for new releases. The Enterprise Manager 32-bit installer had been deprecated from the 21.12 release. In addition, Illustra 610 and 825 (Edge), and ARM Debian (M-Series) installers will be retired as well.

Why is Exacq taking this step?

This change helps address cyber security/robustness concerns by removing support for those installations that are potentially deployed on operating systems no longer fully supported by the vendor. Additionally, retiring support for older/obsolete technology helps Exacq to streamline engineering resources to focus their efforts on faster delivery of customer outcomes that are needed now and in the future.

What if I have been using 32-bit installers for exacqVision all the time? How do I update to the 24.03 release?

If a customer is currently using 32-bit installers, they would have to move to the 64-bit installers – provided the hardware and the operating system are 64-bit enabled. 32-bit and 64-bit installers cannot co-exist. To move to the 64-bit installation, the 32-bit installation should be uninstalled.

So as to not lose the current configuration, it is recommended that the current configuration be backed up – then restored after the 64-bit installation has been deployed. Please refer to this user guide section for understanding how to do a backup and restore of the exacqVision Server configuration.

If Enterprise Manager is deployed, you may refer to this video to understand how to backup and restore configurations across multiple servers at once.

How do I know if the hardware and operating system on my NVR is 64-bit capable?

It will depend on how old the NVR is.

If the NVR was built by Exacq and is a Windows machine – Any system that shipped on or after May 2013 is capable of running a 64-bit installer.

If the NVR was built by Exacq and is a Ubuntu machine – Any system that shipped on or after August 2017 is capable of running a 64-bit installer.

Please refer to the following Support article to determine the age of your system based on the serial number:
How to Determine the Age of a System Using a Serial Number

If the NVR was not built by Exacq, please contact your IT department or the manufacturer of the NVR to assess if it is capable of running a 64-bit installer. As a reference point, Windows started 64-bit support from Windows Vista, with mainstream support adopted in Windows 7, and Ubuntu from Ubuntu 16.04. So it is more than likely that the NVR in question is 64-bit capable. With that said, please double-check with relevant departments and resources to be sure.

NOTE: Operating system vendors, whether or not they support 64-bit, have set time tables for end-of-life (EOL). It is not recommended to use a system for which critical cyber security patches are no longer available. For example, Microsoft no longer supports Windows 7 or 8. Ubuntu does not support systems older than 14.04 today – and they will continue to obsolete older versions as they release new ones.

I can see my NVR is not capable of running a 64-bit installer. What is the recommended course of action?

It is likely that you are running an old NVR that is probably not in compliance with the cyber security standards of your IT department. In addition, you will not benefit from new features, integrations, cyber security patches, and bug fixes that make up the 24.03 and future exacqVision releases. Our recommendation is that you upgrade to newer hardware and operating system for your NVR. Please reach out to your local exacqVision dealer or call Exacq Inside Sales for better understanding of your options.

<br>

Categories
Video Library Demo exacqVision Client Youtube Video Library Categories Products

exacqReplay

exacqReplay
The exacqReplay feature is a fast and convienient way to view recorded video or simply isolate a live camera for viewing. This short video shows how to use exacqReplay.
Categories
Video Library Configuration User Guides Illustra exacqVision Client exacqVision Server Youtube Video Library Categories Products

How to Add IP Cameras – Quick Add

Exacq Add IP Cameras – Quick Add

Learn how to use the new Quick Add feature, introduced in exacqVision Server/Client 24.03 to remove the multistage process of setting up and adding new cameras to your exacqVision system. Quick Add combined with the Illustra Registration License tool provide an easy to use experience when pairing Illustra cameras with Exacq.

For a written article of these steps, see the Add IP Cameras – Quick Add article.

<br>

Categories
User Guides Documentation Illustra exacqVision Client Categories Products

Add IP Cameras – Quick Add

Description

The Quick Add tab, found on the Add IP Cameras page of the exacqVision Client is a recently added feature. Introduced in version 24.03, this feature accelerates the configuration and addition of supported camera models to your exacqVision system.

<br>

Products

  • exacqVision Server 24.03 and higher
  • exacqVision Client 24.03 and higher
  • Illustra IQ Pro Gen4
  • Illustra IQ Pro Gen3
  • Illustra IQ Flex Gen4
  • Illustra IQ Flex Gen3

Quick add requires both exacqVision Server and exacqVision Client versions 24.03 or higher. Only Illustra Pro and Flex Gen3/4 cameras are supported at this time. The Flex Multisensor (IFS16-M10-BT03) does not support Quick Add.

<br>

Pro Tip: If your Illustra IQ cameras are eligible for free licensing, apply your updated license key prior to adding cameras to avoid consuming paid camera channels. Contact your integrator or dealer for details.

<br>

Steps

  1. Connect out-of-the-box or factory defaulted Illustra IQ cameras to your NVR’s network.<br><br>
  2. Navigate to the Add IP Cameras page within the exacqVision Client.<br><br>
  3. Select the Find IP Cameras tab on the bottom half of the page.<br><br>
  4. Discover cameras by pressing the Rescan Network button.
    <br><br>
  5. The Find IP Cameras tab will list all discovered devices whether Quick Add is supported or not. The Quick Add tab will display the number of Quick add supported devices found. You will also see a note beside the Add Selected button. Select either of these to be taken to the Quick Add tab.
    <br><br>
  6. Select the Quick Add supported devices you wish to configure and add using the checkboxes from the list.<br><br>
  7. Press the Edit button and enter the desired Username and Password credentials to be used for the selected devices. Click Save when done.
    <br><br>
  8. Press the Add Selected button in the bottom corner to begin the Quick Add process. The status of the devices will change as each configuration stage is completed on the device. Each selected device will then appear in the IP Camera List above and begin the process of securely connecting to the server.
    <br><br>
  9. After initial use of the Quick Add feature, the created credentials may be used for subsequent Quick Add operations. Username and Password fields are pre-filled with the previously used credentials when returning to the Quick Add tab.<br><br>
  10. Selecting the Edit button allows you to enter a different set of credentials from those previously used.<br><br>
  11. Selecting the View button will prompt users to authenticate to the server with Admin credentials. Once authenticated, the Password will display in plain text for 20 seconds. You may choose to use the copy icon beside the Password field to copy this to the system’s clipboard. The clipboard contents are also cleared after 20 seconds.
    <br><br>

<br>

Categories
Knowledge Support Support exacqVision Client exacqVision Mobile Categories Products

How to Determine if a Mobile User is Connected Through Remote Connections

Description

The exacqVision Mobile application provides the ability to connect straight to the exacqVision Server service, without the use of the exacqVision Web Service, when using server version 24.09 and higher. This connection can be made directly or by means of the Remote Connections feature. This article instructs users on how to determine which method a mobile user is/has connected with.

See also:

<br>

Steps

  1. Open the exacqVision Desktop Client software.<br><br>
  2. Navigate to the Configuration screen.<br><br>
  3. Select the Server name from the system tree on the left-hand side to reach the System Information page.<br><br>
  4. The System Usage panel in the upper-left lists all currently connected users.<br><br>
  5. Mobile connected users will display ‘ipv4:‘ before the IP address in the Address column.<br><br>
  6. The IP address of the mobile device will be shown when connected directly to the system without the use of the Remote Connections feature.<br><br>
  7. If connected through the Remote Connectivity agent, the IP address will be 127.0.0.1.<br><br>
  8. If searching for prior connections using the Login History tab on the bottom half of the System Information page, the addresses there will also be shown according to items 5, 6, and 7 above.<br><br>

<br>

Categories
Knowledge Support Video Library Demo Support exacqVision Client exacqVision Server exacqVision Mobile Categories Products

2024-03 March Exacq Release Training

This training covers the following topics:

Quick Add – Requires exacqVision Server and Client 24.03 or higher. Supports only Illustra Flex and Pro Gen 3/4 cameras.

Architecture changes – Changes made in how the new exacqVision Mobile app connects to exacqVision Server and when exacqVision Web Service is still required.

Remote Connectivity – Provided for exacqVision Mobile support. Requires exacqVision Server and Client 24.03 or higher.

exacqVision Mobile – Demo of new exacqVision Mobile app, including navigation, creating Views, use of Focus View, saving and exporting clips, adding servers, audio, and PTZ.

<br>

Categories
User Guides Documentation exacqVision Client exacqVision Server exacqVision Mobile Categories Products

Remote Connections

exacqVision Server and Client versions 24.09 introduce our Remote Connections feature. This added feature currently only supports exacqVision Mobile. Connections for the Desktop Client, Exacq Mobile 3, or Web Client remain unchanged.

Products

  • exacqVision Server 24.09 and higher
  • exacqVision Client 24.09 and higher
  • exacqVision Mobile 24.09 and higher

What benefit does Remote Connections provide?

  • Ease of Setup – There is no need to configure routers to open ports and/or port forwarding, or configure additional software. This relay previously required configuration through the Web Service.
  • Authorization – Mobile users enter a single-use code provided by the exacqVision administrator to add a server connection.
  • Encryption – Enforces SSL/TLS connections.

Why don’t I have to configure port forwarding?

Traditionally, users outside of a LAN wishing to connect to services inside a LAN initiated the connection request. This can still be done if users choose this method.

However, when Remote Connectivity is enabled, the exacqVision software takes advantage of the fact that routers usually permit devices already inside the private network to initiate connections to outside services. This is what allows your web browser to load web pages without configuring port forwarding on your router. The exacqVision server establishes a secure connection to our Remote Connectivity agent. Users of the exacqVision Mobile app then connect to this Remote Connectivity agent. The Remote Connectivity agent handles the secure passing of data between the exacqVision Server and the user’s app.

What is this code users enter?

The Remote Connections feature provides another layer of security over just usernames and passwords. exacqVision administrators press a button within the exacqVision Client to create one or several single-use codes. A user wishing to add an exacqVision Server instance to their mobile app must enter the code provided by their system administrator before it expires (within 24hrs). The code is only needed for the initial connection to the server. Unless the user deletes the system from their mobile app, there is no need to enter a code the next time the app is used.

<br>

Related Articles

<br>

Categories
Knowledge Support Support exacqVision Client Products

Camera Recording Page Columns Missing on Fresh Install

Description 

The Camera Recording Page in the client doesn’t show any of the default options such as, IP Address, Camera Name, Video Detection, Record Status, Last Motion, Mac Address, Type, Model, Firmware.

Product 

Exacq Client 23.06 and as early as 22.12

  • Windows and Linux

Steps to Reproduce 

Remove Exacq Vision Client completely from the Recorder, or any client machine.
Install Exacq Vision Client 23.03, 23.06, 23.09

Expected Results 

Client shows all the same default options on a fresh install.

Actual Results 

The checkbox for all the devices is missing. This allows selecting multiple cameras to push updates to. The other options like IP Address, Connection Status, Type, Model, Firmware are not enabled by default.

Solution

You are able to add the default options with the exception of the Checkbox to select all the cameras.
Simply Right click on one of the default columns such as , Frame Rate, Resolution, Format, Quality and select a new column to be added seen below.

Once you select the option it will appear seen below by selecting the IP address.

The only item that can not be added currently is the checkbox to select cameras. This is resolved in our March 2024 Release with version 24.03

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories exacqVision Webservice

HTTP Response Code Reference

Code Description Definition Exacq Tips
Informational
100 Continue Server received request, client should continue.
101 Switching Protocols Response to upgrade header
102 Processing Server processing received request.
103 Early Hints Used with link header.
Allows browser to preload resources.
Successful
200 OK Standard response for successful request.
Meaning varies based on method (GET, POST, etc).
201 Created New resource successfully created.
Usually in response to PUT or POST request.
202 Accepted Request accepted but still in progress.
203 Non-Authoritative Info Data returned isn’t from the origin server.
Modified data from third-party.
204 No Content Request successful but there is no content.
205 Reset Content Request successful, server asked to reset doc.
206 Partial Content Server delivered part of the resource.
Used with range header.
207 Multi-Status Provides status of multiple resources with sub-requests.
208 Already Reported Members of element already reported.
226 IM Used Server completed GET request.
Redirection
300 Multiple Choices Request has more than one possible response.
User should choose one.
301 Moved Permanently Requested resource has permanently moved
to a new URL.
302 Found Requested resource temporarily moved to new URL.
303 See Other Server redirects user to requested resource
with GET request to another URL.
304 Not Modified Used for caching. Response unmodified so client can use cached version of resource.
307 Temporary Redirect Requested resource temporarily moved to new URL.
308 Permanent Redirect Requested resource permanently moved to new URL.
Client Error
400 Bad Request Server can’t or won’t process request due to client error.
401 Unauthorized User doesn’t have valid credentials to get requested
resource.		 Invalid username or password
403 Forbidden Client doesn’t have access rights to content.
Unlike 401, the server does know client’s identity.
404 Not Found Server can’t find requested resource. No redirection set. Request Not Found
The device didn’t understand the request.
May be caused by untested device or firmware.
405 Method Not Allowed Server supports request method, but target doesn’t.
406 Not Acceptable Server doesn’t find content satisfies criteria given by user.
407 Proxy Authentication Required Similar to 401, but proxy must authenticate to client.
408 Request Timeout Server times out because client didn’t issue request
in a timely manner.
409 Conflict Server can’t fulfill request due to conflict with resource.
410 Gone Requested content has been removed.
411 Length Required Server rejection becauce it requires defined
content-length header field.
412 Precondition Failed Client has precondition headers the server does not meet.
413 Payload Too Large Client request larger than server limits, so server
refuses to process request.
414 URI Too Long Requested URI is too long for server to process.
415 Unsupported Media Type Request uses media format unsupported by server.
416 Range Not Satisfiable Server can’t fulfill value in request’s range header.
417 Expectation Failed Server can’t meet requirements of expect header in request.
421 Misdirected Request Request made to server that can’t produce response.
422 Unprocessable Content Server unable to process request due to semantic errors.
423 Locked Requested resource method is locked to be inaccessible.
424 Failed Dependency Request failed because a previous request it is dependent on also failed.
425 Too Early Server is unwilling to process request that may be delayed.
426 Upgrade Required Server refuses request using current protocol version.
428 Precondition Required Server needs request to be conditional.
429 Too Many Requests User has sent too many requests within allotted time.
431 Request Header Fields Too Large Server can’t process request because headers are too large.
451 Unavailable For Legal Reasons Server can’t legally provide requested resource.
Server Error
500 Internal Server Error Server encountered unexpected error and cannot
complete the request.		 Device reporting an error.
The device has reported that it has encountered an error.
501 Not Implemented Server doesn’t recognize the request method.
502 Bad Gateway Server acts as a gateway and gets invalid response from inbound host.
503 Service Unavailable Server is unable to process request.
Often occurs if server is overloaded or down.		 Device Unavailable.
The device is currently unable to process this request.
504 Gateway Timeout Server acting as a gateway or proxy has timed out
waiting for response.
505 HTTP Version Unsupported Server doesn’t support the version of HTTP request.
506 Variant Also Negotiates Server has internal configuration error.
507 Insufficient Storage Server can’t process request because it doesn’t
have enough storage space.
508 Loop Detected Server detected infinite loop while processing request.
510 Not Extended Further extensions required for request.
511 Network Authentication Required Client needs to gain network access.

<br>

Categories
User Guides Documentation exacqVision Client exacqVision Server Categories Products

Maximum Days to Keep Bounding Box Metadata Explained

Description

Despite adhering to Analytic Metadata Best Practices, users could encounter storage or performance issues. Symptoms, such as software performance issues or operating system drives that fill up, may be encountered as a result.

More devices than ever today are implementing advanced analytics to detect and classify objects within camera views or audio. Many of these analytic functions continue to emit classification data at a high rate, whether or not anything is occurring. Consider a camera configured with vehicle detection. A camera directed at a street or parking lot is likely to continue to emit metadata about each vehicle each second regardless of the fact that they may be parked, doing nothing of considerable interest to the viewer. As a result, the database receiving this metadata can grow to large size very quickly.

Product

  • exacqVision Server 23.09 or higher
  • exacqVision Client 23.09 or higher

Both Server and Client versions must be version 23.09 or higher to take advantage of this feature.

<br>

Solution

Maximum Days to Keep Bounding Box Metadata

Located at the bottom of the Event Linking page, just above the buttons to add and delete new event linkages, this control allows administrators to enter the maximum number of days, up to 365, to retain the bounding box data for object classification analytics.

This provides a method, beyond following metadata best practices, to aid in controlling the size of the database to improve forensic metadata search performance and limit its size. Data that reaches this threshold will be eliminated from the database.

IMPORTANT: If your drive was previously filled to capacity due to the database size, delete the eventpi.db file from the exacqVision Server directory, then restart the exacqVision Server service.

NOTE: While this constrains the size of the database, once removed these metadata points may not be used in forensic searches.

<br>