Category: exacqVision Integrations

CCure 2.80 Integration – Exacq GUID Install

In CCURE 2.80 CCURE introduced a breaking change to their API in their primary login, so our code had to be modified to let people login. So the first thing to note is that Exacq Server version 20.09 or later is required to be able to login to Victor Web 2.80 or later. The next… Continue reading CCure 2.80 Integration – Exacq GUID Install

Illustra3 with illustraFlex fw 3.1.4 returns http error 500

Description IllustraFlex firmware 3.1.4 returns http 500 from the http metedata request. The camera failed to respond to a motion/input trigger event. This is a fw issue and is fixed in 3.1.5 archived here. \\shares.exacq.org\Public\Software\American Dynamics\Illustra Flex firmware\web-update-Ver.3.1.5-20170213.opk. <br> Version Introduced 8.2.2.108683 <br> Platform All <br> Steps to reproduce Connect illustrFlex(ADCi600F/ADCi800F) that supports iAPI3(fw >… Continue reading Illustra3 with illustraFlex fw 3.1.4 returns http error 500

Axis HTTPS setup

To setup an Axis camera for HTTPS support in 8.4.1 server. Log into the camera web page and go to the setup page.Select “System options” and HTTPS.The HTTPS settings page might look different between fw’s.To create self signed certificates, select the create option and fill in the required fields such as country/locality/state/organization/etc in the popup.To… Continue reading Axis HTTPS setup

Axis V5915 audio-out fails in digest authentication mode.

Description Audio-out does not work with V5915 fw 5.75.1.4 and set to digest or basic or digest authentication mode. This is a misbehave camera fw that server 8.4 does not support properly. Work around is either revert back to 8.2 or set the camera to basic authentication mode until the issue is fixed. <br> Version… Continue reading Axis V5915 audio-out fails in digest authentication mode.

iSCSI CONSIDERATIONS WITH LINUX RECORDERS

iSCSI CONSIDERATIONS WITH LINUX RECORDERSAlso Note: https://crm.exacq.com/kb/?crc=42338 == recovering corrupt iSCSI configuration in Linux (open-iscsi issue). This can also solve the occasionally-observed problem of deleting a portal, restarting service, and observing the portal was not actually deleted after all. Alternatively, you can also: sudo services edvrserver stopsudo apt-get purge open-iscsisudo apt-get install open-iscsisudo services edvrserver start… Continue reading iSCSI CONSIDERATIONS WITH LINUX RECORDERS

Illustra discovery for Pro and Essentials issues with dual nic as well as Una systems

Inconsistent results. Web interface not showing all details, firmware, model, etc. Doesn’t always find Pro cameras even though static IP addressed. Also found 610LT’s twice and added them twice.Workaround suggestedFor Dual nic systems:For dual nic systems with duplicated results, either disable one of the nic’s or make sure that they are not set to the… Continue reading Illustra discovery for Pro and Essentials issues with dual nic as well as Una systems

Using Soft Triggers from CCure 9000 with Event Linking

From the C-Cure 9000 interface, find the Camera ID as pictured below. Setup a “Soft Trigger” under the “Action” tab. Change the “Action Type” to “Soft Trigger. Back in the exacqVision Client, create a new Event Link using the Event Type of “Soft Trigger” and the “Event Source” will match the Camera ID from above.

Kantech Shows Door Forced Open For All Doors

Symptom: When a user triggers a ‘forced open’ status for one door, exacqVision displays ‘forced open’ on all doors.  <br> Cause: The Entrapass user configured in exacqVision does not have permission to read the door state. <br> Solution: Update exacqVision Server to 9.3.0 or later to resolve.  It is recommended that the Entrapass user is… Continue reading Kantech Shows Door Forced Open For All Doors

First command to unlock/lock door or other action via Kantech integration fails

Affected platforms exacqVision Server 7.2.0 <br> Symptom When sending a command to an access control module (lock/unlock door, activate/deactivate relays etc.) the first attempt may fail silently. This is likely to happen if the operator credentials are same as the connection credentials. All subsequent commands will succeed or fail with an error message. <br> Workaround… Continue reading First command to unlock/lock door or other action via Kantech integration fails