Q3 2024-08-24 ev-WebService-Linux-x64^Version 24.09.1.0^https://cdnpublic.exacq.com/24.09/exacqVisionWebService_24.09.1.0_x64.deb^17 October 2024^145MB,
Category: exacqVision Webservice
Q3 2024-08-24 ev-WebService-Windows-x64^Version 24.09.1.0^https://cdnpublic.exacq.com/24.09/exacqVisionWebService_24.09.1.0_x64.exe^17 October 2024^74.7MB,
<br>
exacqVision Server
- Bug Fix – Fixed insertion of objects lacking metadata or bounding box
(AESW-9440) - Bug Fix – Improvements to event size estimates for bookmarks
(AESW-11010) - Bug Fix – illustra3 and illustramultipi fixed issue where Alarm 2 status would not change after being canceled
(AESW-10146) - Bug Fix – illustra3 and illustramultipi fixed issue causing edgestor backfill to hang
(AESW-9581) - Bug Fix – Onvif, fixed issue preventing simultaneous PTZ
- Big Fix – Onvif, fixed excessive pullpoint logs on errors
(AESW-10727) - Bug Fix – Onivf, fixed potential PTZ disconnects
(AESW-11469) - Bug Fix – psfpi, fixed potential hang when evAPI attempts to cancel search
(AESW-10961) - Bug Fix – Samsungpi, fixed crash on disabled device during connection
- Bug Fix – Samsungpi, fixed potential crash when connecting to newer devices
- Enhancement – Support Area Zoom on Axis M5000-G PTZ camera
(AESW-10568) - Enhancement – eventpi, new event indicates thinning occurred, includes event linking sources
(AESW-7651) - Enhancement – Installer adds firewall rules added for failover and failback
- Enhancement – Improved analytic parsing
- Enhancement – Provide the analytic type to core
- Enhancement – Improved handling of transport errors
(AESW-10120) - Enhancement – New SOAP calls for Onvif Profile M and S conformance
- Enhancement – remotepi, move connection to production switchboard service
(AESW-9771) - Enhancement – Additional logging around LDAP reauth queries
(AESW-9769) - Enhancement – Improved performance by reducing amount of analytics sent from server to client
(AESW-7715) - Feature – Support for Wasabi S3 as archiving target
(AESW-5814, AESW-10924) - Feature – Support added for Axis Thermometry
(AESW-8816, AESW-8918) - Feature – Illustra LPR Support
(AESW-6504)
exacqVision Client
- Bug Fix – Manage the preferred MAC address in License panel
(AESW-11267) - Bug Fix – Fixed issue where exacqReply controls did not appear until window was resized
(AESW-9992) - Bug Fix – Clear grid dropdown, to fix issue where drop-down menus duplicate entries
(AESW-10923) - Bug Fix – Fixed issue with Oldest Desired Content of Cloud Drive
(AESW-8097) - Bug Fix – Fixed issue of event forward button being disabled when skipping ahead
(AESW-8958) - Bug Fix – Fixed issue of client crash when selecting Find Camera when creating a new View
(AESW-10038) - Bug Fix – Fixed client crash when selecting audio in Add Video panel
- Bug Fix – Fixed issue of auto play not working in Timeline search
(AESW-8529) - Enhancement – Remote Connections, found on navigation tree
- Enhancement – Added Mobile Optimized Streaming panel for Remote Connections
- Enhancement – New toast message indicating event thinning has occurred
(AESW-9871) - Enhancement – Client improvements to amount of analytic data passed between server/client
(AESW-7716) - Enhancement – Support “horizontal flip” for Storage page to accommodate storage layout for new Avnet systems
(AESW-10562) - Enhancement – Apply our security standards to Bodyworn password fields
(AESW-1575) - Feature – Support for Wasabi S3 as archiving target
(AESW-11025)
exacqVision Web Service
- Bug Fix – Fixed 24.03 issue where iPAD experienced video buffering and timeout errors
(AESW-10945, AES-839, AES-863, AES-909) - Bug Fix – Web client supports session timeout detection, respects the login token
(AESW-9753, AES-774)
exacqVision Enterprise Manager
- Bug Fix – Add missing pagination endpoints
- (AESW-11414)
Exacq Mobile 3
- Bug Fix – Fixed issue with video failing to play after one hour
- Enhancement – Added notification to point users to new exacqVision Mobile app
(AESW-9166)
exacqVision Mobile
- exacqVision Mobile requires Server version 24.09 or higher
- Remote Connectivity requires Client 24.09 or higher as the Client is needed to connect to the cloud switchboard and generate access codes
- If SSA expiration or OS requirements prevent updating to Server 24.03, users will need to continue using Exacq Mobile 3, with the exacqVision Web Service
Exacq Hardware
Hardware Revisions
- C-Series 16S & 32S
- G-Series Micro
- G-Series PoE 8ch & 16ch
- Q-Series Desktop & Desktop Hybrid
- A-Series 2A & 2A Hybrid (no RAID)
- A-Series FA & FAR (RAID)
- X-Series 1U & 2U (RAID)
exacqVision Advantage
- Provides free exacqVision licensing on BBE hardware for most models of Illustra Flex and Pro cameras (Gen3, Gen4, and future generations).
- Does not apply to the Flex Gen3 Multisensor, which is ONVIF only, does not have the Illustra API
Illustra
- New Pro camera models providing LPR on the edge
- Bullet IPS05-B12-LPR4
- Dome IPS05-D12-LPR4
<br>
The most recent release of the exacqVision Mobile app represents a departure from the previous functionality of Exacq Mobile 3. Previous versions of the mobile app connected to the exacqVision Web Service. The Web Service acted as a client to the Server, passing video between the server and mobile app.
Changes in the architecture of the exacqVision Server along with a mobile app rewritten from the ground up now allow the mobile app to connect directly to the exacqVision Server.
The exacqVision Web Service will continue as a product but will no longer be needed for those using the exacqVision Mobile app. When installing the exacqVision Server Bundle users may opt not to install the Web Service. Deployments which will still require the Web Service will be those in which users use the Web Browser Client, cannot update the exacqVision Server to a version supporting this, or which rely on the evWebAPI for integrations.
<br>
NOTE: The file upload utility tool has been deprecated. This process should be used in its place. Use of file sharing providers such as Google Drive, Dropbox, iCloud, etc for file exchange with customers is forbidden by JCI.
Sharing Files
- Log into the Exacq Support Portal with an Administrator or Level 2 user role.<br><br>
- Access the File Manager, found under the Admin menu.<br><br>
- The root (home) directory will list existing directories you have access to view. Administrators can see all directories, Level 2 technicians will see only directories they have created or are given access to.<br><br>
- Create a directory for each case, or create a directory structure for customers and place case directories inside these.
<br><br> - With the directory created, drill down into the directory by selecting the directory name.<br><br>
- Select the +Files option. Drag and drop a selected file, or use the Browse option to select a file to upload.
<br><br> - Attach one or more files, then select Upload.
<br><br> - Click the Close button to return to the directory.<br><br>
- Select the Copy Link button beside the file you wish to share and share this link with the customer. They will need to log into the Exacq Support Portal to reach the file.<br><br>
- Files are automatically set to be deleted after 30 days to manage file storage.<br>
<br>
Customer File Uploads
- Log into the Exacq Support Portal with an Administrator or Level 2 user role.<br><br>
- Access the File Manager, found under the Admin menu.
<br><br> - The root (home) directory will list existing directories you have access to view. Administrators can see all directories, Level 2 technicians will see only directories they have created or are given access to.
<br><br> - Create a directory for each case, or create a directory structure for customers and place case directories inside these.<br><br>
- With the directory created, either drill down into the directory, by selecting the directory name, or check mark the box beside the directory in list view.
<br><br> - Expand the Actions menu and select Share.
<br><br> - Use the Account Search field to locate the Support Portal user you will provide the directory share link to.
<br>NOTE: Yes, the customer MUST have an Exacq Support Portal member account. Direct them to the Sign Up form if they do not have one.<br><br> - So that you may provide a link to the customer, you will need to change permissions from Private to Access List.
<br><br> - To enable uploads, toggle the Access Level beside the user’s name to change it from READ to READWRITE. In situations where multiple users are added, you may mix access levels between users.<br><br>
- Press the Copy Link button to copy a link you may wish to share with the customer. They will need to be logged into the portal and use this link to access the directory you have shared to upload files. They should also receive an email with links as well.<br><br>
- Close the dialog window and reload the directory to refresh any changes in the files displayed. Files are automatically set to be deleted after 30 days to manage file storage, but you may select files to manually remove them earlier than the expiration date if desired.
NOTE: Portal Admins will find that their file uploads default to an Expiry date of Never. This is because it is assumed Admins are uploading files that need to remain. Use the chevron icon beside the file name to change the Expiry date.<br><br>
Description
When watching search back in the Exacq WebService Thin Client at high speeds for longer duration’s the search will skip to the end of the search results. This results in a black screen after being able to view the searched contents and scrubbing the video at 16x’s speed and higher.
Product
exacqVision Web Service 22.12.2.0 through 23.09.7.0.
Steps to Reproduce
- Search a time range of 2 hours using the web client.
- Video will play back from the search results.
- Scrub the video at 16x speed to 32x speed and the search marker will skip to the end of the search content.
Expected Results
Users should be able to scrub the entirety of the the searched content with no skipping.
Actual Results
The playback scrubber/cursor skips to the end time of the search content, displaying a black box.
Solution
A fix was introduced in branch build exacqVision Web Service 23.09.107.0 (x64).
Please contact technical support for assistance on installing this build.
A Permanent fix will be in our March 2024 Release. Version 24.03.
Description
Viewing live video will cause a black screen on the Live page with a buffering icon. Live video may also work for a short time then start to buffer. This has been noticed on Ipads and Iphones.
Product
exacqVision Web Service 23.09.6.1 up to 24.03
Steps to Reproduce
- Open the Exacq Mobile 3 app or Mobile Client within a web browser to connect to the server.
- Pull up a live view of a single camera or 4 cameras.
- Live view will sometimes show 3 of the 4, or sometimes when adding a single live view it will show video for a short time.
- Look in the web service logs for the following error if this behavior is being seen.
debug get frame no video in decompressor nvrg 236426Expected Results
Users should be able to view the live video.
Actual Results
After a short amount of time, for example 3 minutes, the live view will show a black screen with buffering overlay. Often pulling in the live stream at first will often cause buffering to populate in the view instead of the live video. Specifically with views made up of more than 4 cameras.
This is caused by streaming transcoded jpeg through the mobile app, and decompression is not always being enabled correctly.
Solution
Update to exacqVision Web Service 24.06.1797300.0_x64.
Please contact technical support for assistance on installing this build.
This will be in our 24.09 Release.
AES-909
The method used for connecting to an exacqVision system from outside the LAN it resides on will depend on your network configuration and use case. Examples are provided below based on each method.
Remote Connections
Remote Connections are supported by exacqVision Server/Client 24.09 and above to facilitate connections from the exacqVision Mobile app. When considering the network configurations Remote Connections eliminate the need to open ports or enable port forwarding rules on your router by using Exacq’s Remote Connectivity service. Users of the mobile app enter an access code generated by the system admin and the Remote Connectivity agent handles the connecting of the mobile app user and the Server.
NOTE: Remote Connectivity does not accept connections for the Desktop Client software or the earlier Exacq Mobile 3 app. Only exacqVision Mobile 24.09 and higher are supported.
<br>
Traditional
In a traditional setup, the site’s router is configured to port forward incoming external connections on each port. The ports configured for forwarding incoming traffic vary depending on whether users will connect via exacqVision Desktop Client software, the web browser client, or a mobile app.
<br>
Web Relay Service
Sites using exacqVision Web Service 19.06 and higher may wish to take advantage of the web service Relay, which provides a web-based proxy to connect to, avoiding the need to configure the router for port forwarding. When enabled, the exacqVision Web Service Status page will display the Relay Service IP. Remote users will then be able to connect their Exacq Mobile 3 app or web browser client directly to this proxy IP address.
NOTE: The Relay Service does not accept connections for the Desktop Client software, only web browser and Exacq Mobile 3 connections.
<br><br>
Related Articles
- Example Network Diagram for Multi-NIC Systems
- Exacq Software/Service Connections Diagram
- Remote Connections
- Video: Remote Connections
- Accessing exacqVision from Tablets and Phones using the exacqVision Mobile App
<br>
| 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>
What is a HAR file?
HAR stands for HTTP Archive Record and is a JSON structured file containing network traffic information about a browser’s interactions with a server as well as the content on a webpage.
When HAR files are useful
- Performance issues: slow page loading, timeouts when performing tasks, time spent negotiating proxy connections, time spent issuing requests, time spent receiving the response data, DNS lookups, and others
- Page Rendering: incorrectly formatted pages or missing information
How to Capture HAR files
Prior to performing a capture open an Incognito window or tab to eliminate capturing decrypted request-response communications or cookie from unrelated sites or events.
Chrome
- Access Menu > More tools > Developer tools (CTRL+SHIFT+I or F12)
- Select the Network tab, if not already selected.
- Ensure that the Preserve log box is checked.
- Check mark the Disable cache box.
- Reload or recreate the activity you wish to capture.
- Click the Download icon.
Firefox
- Access Menu > More tools > Web Developer Tools (CTRL+SHIFT+I or F12)
- Select the Network tab, if not already selected.
- Ensure that the Persist Logs box is checked.
- Check mark the Disable cache box.
- Reload or recreate the activity you wish to capture.
- Click the cog icon.
- Select Save All As HAR.
<br>