Exacq Unbreaks Avigilon Integration

By IPVM Team, Published Oct 18, 2017, 01:03pm EDT

For nearly 4 years, Exacq had broken and effectively blocked use with Avigilon cameras, as IPVM reported in January 2014.

Now, Exacq has 'unbroken' this integration, which we see as being a warming of relations between the two companies. In this note, we examine what happened technically and what this signals about the relationship between the companies.

Avigilon ******* **-***** ** *****

***** ******* *.*.* ***** support *** ******** *******, according ** ******* ***** for *********** ****** [**** no ****** *********].

**** *********** **** ******* to ********'* ***** ******, and **** *** ******* any **** ** *********-***** motion ** ****** **** Avigilon *******.

 

IPVM **** *******

** ****** ***** ******* *.*.*.****** with ******** ** *** and ** **** **** cameras *** ********* ****** events ********* ** *** VMS ** ********, ***** below, **** *** ****** window ****** ******* **** on ****** *** ******** when ****** *****.

** ************* ** ****** VMD ** ********* ** Exacq, **** ** ****** sensitivity ** ****(*), **** pre *** **** ********* time:

Pixel ****** ********* ****

**** **** **** ******* works **** ********'* ***** motion ********* ****, *** classified ****** ****** ********* or ********* *****. ***** other events **** ****** *** recognized ** *** ***** server, *** **** *** not ***** *** ****** in *********.

Response **** *****

***** ********* ** ****:

******** *** ***** *** some ****** ******** ** wanted ** ******* ** their ******** ** ** worked **** **** ** test **** ****** *** validation. ** **** **** it's **** *** ***** motion *********.

Avigilon *******

**** ******** **** *** significant ******* ** ******** management *** ******* ****** get ******* *** ***** cameras **-***** ** *****.

****** *** **** - **** time *****, ******** *** **** ********** competing ******* *****, ********* moves **** ***** **** crossed *** **** ** pushing ** **** ***** VMS ********* ** ********, according ** ****** ***** to *** *******. ***** Avigilon ***** *** ** aggressive sales ****, *** ******* has **** **** ******* in *** ******* *** positioning ******.

Beneficial *** ********

**** ** ****, **** move *** ****** ******* as ***** ******* ****** blocked **** *****. ****, of ******, ******* *********** ******** ************ ****** ** ****. However, ***** ********* *********** with ******** *** ** a ******** *** ********** sign *** *** ******** that ********* *** *** simultaneously ******** *** *********** can ****** **** ********.

Comments (12)

Undisclosed #1

IPVMU Certified | 10/18/17 06:11pm

For nearly 4 years, Exacq had broken and effectively blocked use with Avigilon cameras, as IPVM reported in January 2014.

Just the Avigilon motion detection was blocked, or Avigilon cameras in general?

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed #1 | 10/18/17 06:15pm

VMD. There was no issue connecting to Avigilon cameras with Exacq, but you were limited to continuous recording. Now the VMD and I/O works. 

Agree
Disagree
Informative: 2
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | In reply to Ethan Ace | 10/18/17 06:34pm

Didn't VMD anyway work if you just changed the onvifnvcpi.json file, as you pointed out in 2014?

 

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed #1 | 10/18/17 06:35pm

At the time, yes, but it wasn't officially supported and would be overwritten every time you updated. I think support got a little spotty at one point, as well.

Agree: 1
Disagree
Informative: 2
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | In reply to Ethan Ace | 10/18/17 10:17pm

That makes sense because it's ONVIF motion detection, not some propreitery version.  

So if VMD worked for other ONVIF cameras on Exacq, and assuming Avigilon's implementation was correct, there's no reason it wouldn't work.

Therefore Exacq had to explicitly mark Avigilon cameras as not supporting ONVIF VMD so that the VMS would not even try. 

So really Exacq didn't just break Avigilon VMD, but actually had to break their ONVIF VMD in a way that made it not work for Avigilon.

 

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed #1 | 10/18/17 10:23pm

Nope. ONVIF events are not standardized, even something as simple as VMD. Manufacturers can use different XML strings for events as they see fit. 

So in order to integrate various manufacturers, you need to know where their event stream is. It's not much in the way of coding requirements, but it still has to be integrated for each manufacturer.

That's what the onvifnvcpi.json file contains, the manufacturer name, the event (motion), the location of the event stream (RuleEngine/MotionDetection/), the specific motion event name (MotionActive), and whether it's off or on (1/0), shown here:

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | In reply to Ethan Ace | 10/19/17 02:47pm

Nope. ONVIF events are not standardized, even something as simple as VMD. Manufacturers can use different XML strings for events as they see fit.

Are you sure about that? The strings are not arbitrary manfacturer creations, IMHO, and in any case they are dynamically discoverable at run time.  The Analytic test tool expects:

So in order to integrate various manufacturers, you need to know where their event stream is. It's not much in the way of coding requirements, but it still has to be integrated for each manufacturer.

I agree that Exacq did it this way, and therefore needs the Avigilon entry in the file; but I don't think it was necessary based on the ONVIF docs I have seen.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed #1 | 10/19/17 03:02pm

They unfortunately are arbitrary strings. 

In that onvifnvcpi.json file you can find the strings for multiple manufacturers, here's a sampling:

  • VideoSource/MotionAlarm/
  • VideoSource/MotionDetection
  • VideoAnalytics/Motion/
  • VideoAnalytics/MotionDetection/
  • RuleEngine/MotionDetection/ThresholdCrossed/
  • RuleEngine/CellMotionDetector/Motion/

Some use 1 for on and 0 for off, some use "true" and "false", etc., etc. 

Agree
Disagree
Informative: 1
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | In reply to Ethan Ace | 10/19/17 07:03pm

They unfortunately are arbitrary strings.

Agreed they are different.  Though they look somewhat more alike than arbitrary, consider for instance stream URLS. Maybe it's a holdover from early ONVIF implementations?

Regardless my point was that whatever data definition the device used it could be dynamically retrieved at run time via SOAP calls etc, obviating the need for the motion parts of the file.  Perhaps it was easier for Exacq to manage it the way they did it.

Now the new Analytic test tool expects RuleEngine/MotionRegionDetector/Motion and event.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed #2

10/18/17 06:51pm

8.8 has been the best feature release in years in my opinion. Exacq nailed it on this one.

Agree: 3
Disagree
Informative: 3
Unhelpful
Funny

Undisclosed Integrator #3

08/24/18 09:16pm

Is it possible to use current Avigilon models with the latest versions of Exacq still or is it limited to specific models.  They only have a couple listed.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed Integrator #3 | 08/24/18 10:06pm

We've had an Avigilon camera added to Exacq for months, if not more than a year, with no issues. It only works with the camera's VMD, not analytics, but is otherwise fine.

Archived video from today, with motion highlighted blue in the timeline.

Agree
Disagree
Informative: 1
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 7,023 reports, 934 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports