Test adding an override of #config=dynamic to the camera’s address field on Add IP Cameras page
Examine the logs to identify the following log message:
onvifnvcPI Verbose 10.247.216.144 searching for relevant settings<br>in JSON config file
Once troubleshooting is complete, roll the customer back to 23.06 for the time being until the issue is fixed. (See update at the bottom of page.)
Tier 3 Will create New Tickets based on the Manufacturers and link them to AES-701.
Update: When seeing motion issues with the above logs please see if Version 23.09.9.0 will allow motion and free run will record. https://exacq.com/support/downloads.php
When running 23.03 Exacq Client on Mac some cameras intermittently show up very small in live view. Instead of filling the available space, they are 1/16th to 1/4 of the view area and the rest is black. Macs running two different versions of macOS (Sonoma and Big Sur) have been seen.
Product
Exacq Client 23.03-23.06 versions.
Steps to Reproduce
Update Mac Client to 23.03 and 23.06 version and views will show behavior.
Expected Results
This should not been seen.
Actual Results
The live views will be shown as 1/16th or 1/4 the size in the live pane.
Solution
Exacq Client 23.09.7.0 releases on 11-20-2023 will resolve both OS’s.
Exacq Support has identified the need to make edits and adjustments to Edge Storage device XML files in situations where network bandwidth may be limited. If an Axis Edge Storage device is recording to the camera SD card – but fails to offload video data back to the exacqVision Server when regaining network connection, it may be necessary to adjust these values manually in the axispi.xml file contained in the exacqVision Server software file directory.
Product
exacqVision Server software
Axis Edge Storage capable cameras
Steps to Reproduce
Connect several Axis Edge Storage capable cameras, configured for network loss recording to an exacqVision Server.
Emulate the camera’s losing their network connection (i.e.- from managed switch disable the ports cameras are connected to).
Wait an extended period of time, and then restore network connectivity to these same cameras.
Expected Results
Upon restoring network connectivity to these cameras we should begin to see footage being restored from the camera’s SD card back to the exacqVision Server data drives. We should see log entries similar to the following for successful completion:
9/14/2023 03:00:25.704 PM AxisPI Warning 172.19.234.88 EdgeStor – operation 29f2df6a-05cf-4c19-8c02-036e09263e84 for gap start time 2023-09-14T18:38:53Z gap end time 2023-09-14T18:58:25Z was created.
9/14/2023 03:00:25.716 PM AxisPI Warning 172.19.234.88 EdgeStor – operation 29f2df6a-05cf-4c19-8c02-036e09263e84 for gap 2023-09-14T18:38:53Z to 2023-09-14T18:58:25Z is starting.
9/14/2023 03:00:27.036 PM AxisPI Verbose 172.19.234.88 EdgeStor – camera time is 2023-09-14T18:59:41Z converted to UTC time is 2023-09-14T18:59:41.0000-00:00 exacq server time in UTC is 2023-09-14T19:00:27.0000-00:00.
9/14/2023 03:00:27.045 PM AxisPI Verbose 172.19.234.88 EdgeStor – 3 recordings found on device.
9/14/2023 03:00:27.046 PM AxisPI Verbose 172.19.234.88 EdgeStor – requesting disk space reservation of 1 GB for operation 29f2df6a-05cf-4c19-8c02-036e09263e84..
9/14/2023 03:00:27.054 PM AxisPI Verbose 172.19.234.88 EdgeStor – download recordings in gap from 2023-09-14T18:38:53Z to 2023-09-14T18:58:25Z for op 29f2df6a-05cf-4c19-8c02-036e09263e84.
9/14/2023 03:00:35.607 PM AxisPI Verbose 172.19.234.88 EdgeStor – clip for operation 29f2df6a-05cf-4c19-8c02-036e09263e84 clip start time 2023-09-14T18:55:26.703242Z clip end time 2023-09-14T18:58:25Z from recording 20230914_185029_C0D6_B8A44F008DAD has been downloaded Size delta is 3407618.
Logs appear to show this attempting to start exacqVision’s Edgestor event to offload footage for gaps but never completing ending with the following log entries and nothing after:
6/5/2023 06:16:24.003 AM (GMT-4:00) AxisPI Warning 10.35.8.91 EdgeStor – operation 4bfa14de-9ff7-4e99-940b-3c9fcdd2296a for gap start time 2023-06-03T00:03:08Z gap end time 2023-06-05T10:14:23Z was created.
6/5/2023 06:16:24.028 AM (GMT-4:00) AxisPI Verbose EdgeStor – operation 755ce521-0a75-4d73-9dcf-c8b4bd97909d is running.
Solution
With all cameras online, stop the exacqVision Server service and find axispi.xml in server folder directory.
Edit axispi.xml so the first portion of the file looks like (changes needed are in bold): xml eDVR Delta="0" Devices ID="458752" Description="AXIS VAPIX" MaxDevices="255" DefaultPort="80" DefaultUsername="root" DefaultPassword="pass" HttpConfigOptions="2,1,3" SupportsMetadata="1" MaxEdgestorAttempts="5" MaxConcurrentEdgestorDevices="10">
Note: Be advised these Capital values may vary depending upon total number of Axis Edge Storage devices on the network, and the network bandwidth capability.
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.
Axis P3247-LVE “Axis Object Analytics” not passing through the Exacq Mobile 3 app Analytic Rules. If seen please see AES-609. Escalate the case to be added to ticket.
Product
exacqVision Server: 23.06.1.0
exacqVision Web Service: 23.06.2.0
Steps to Reproduce
Set up the camera to allow analytics. Note we do not support line cross for axis cameras.
Once camera is set up navigate to the mobile app and connect to the NVR.
Once Connected navigate to the main menu.
Select Push Notifications
Select Analytics
You should see any analytic that cameras are sending.
Expected Results
We should be able to see the Analytics from the Axis cameras.
Actual Results
Analytics do not show up in the mobile app but do on the NVR’s Server when creating event linking and on the camera settings page.
If this setting is enabled then it is possible with certain version of Server software, an API issue could occur. Specifically with the OVID plugin when integrating with S2.
Product
TESTED Version: Client Version: “22.12.2.0” Server Version: “22.12.5.0” evOVID plugin version 1.1.12.123380
Steps to Reproduce
If the Password Strengthening and Augmented Authentication is enabled then OVID plugin will not allow the live views once it is enabled.
Enabled Strengthening.
In S2 if you go to live view, the video streaming box is “black” (i.e. no video).
Removed the Strengthening by reinstalling the software and the OVID worked successfully.
Expected Results
We should be able to utilize the Password Strengthening and maintain live views via integrations.
Actual Results
While enabled the OVID would not show live video in S2 integration.
Solution
We have verified using evOVID by upgrading evAPI is all that is needed to get the evAPI component of the integration working.
In theory, any version past 1.35.2.53326 should resolve the issue.
AES-311 WORKAROUND: To update the evAPI we can use a drag-in upgrade. Grab the DLLs from the zips (below) and copy them to the ‘bin’ subfolder of the OVID install location.
