Milestone ONVIF Bridge Tested

By Ethan Ace, Published Jul 06, 2016, 09:09am EDT

The Milestone ONVIF Bridge could be a breakthrough.

Enterprise VMSes have long restricted 3rd party access making larger system integration more difficult, PSIMs more complex and expensive and greater lock-in.

Now, Milestone's ONVIF Bridge, enabling open, free 3rd party integration of live and recorded video could make one of the bigger players more open and spur their rivals like Avigilon, Exacq and Genetec to do the same.

But does it work?

We tested the Milestone ONVIF Bridge with 5 VMSes including Avigilon, Exacq and Genetec to see how it worked.

*******

***** ******** ** ** 'ONVIF' ******, ** ****** more **** ** '****' Bridge *** **** ***** only *******.

** *** *****, *** Milestone ***** ****** ****** to **** **** **** VMSes, **** **** ******** Control ****** **** ** connect ********, **** ***** and ******* **** ******* the ******* ** ***** upon *******.

**** ********* ****** **** all ***** ****** ******* issue, ****** ** * potential ****** *** ***** ***** failed ** ******* *** ONVIF, ****** ** ** more **** ********* ** set ** *** ***** advanced ******** **** ** PTZ ******* ***** ** the ***** ***********.

Key ********

**** *** *** *** findings **** **** ****: 

  • ** *** *****, ********** to *** ***** ****** failed ******** **** ***** four out ** **** ***** Profile * ***** (*****, *******, ******* Optix *** ***** ****).
  • ********** **** ***** *** Genetec ****** *** ***** Bridge ******* ** *****, requiring ** ** ** manually *********.
  • ***** ****** ******* *** able ** ******* ** the ****** *** ****** all ******* ******* ***** (live ***** ****, *** recordings).
  • **** ******* ****** ******** in *** ******, ********, and *****.
  • **** **** ***** *** supported ** *** ***** as *** **** ******* G *** ******, ***** Next, *** ****** ** connect ** *** ********* Bridge.

Tech ******* ******** *********

****** *** ****** *** working ****, ***** ** certainly * *******, ** suspect **** ******* ***** be * ********* ** the ****** ** ***** used ** '********' ******** Milestone ********. ** *** one ****, ********* ********* that **** ***** "******* *** ******** ***** the ***** ****** ** make ***** ******* ****, regardless ** **** ***** components **** ***." ** the ***** ****, ********* also *****, "*** ******* ***** ******* be ******* ** *** functionality ** ********* ***** out. ******* ** *** receiving ***, *** *** party ******, ** *** in ***** *** ********* support." ********, ********* ********* that **** ******** *** was **** *** ******* monitoring *** **** **** were ******** ***** *** Bridge ***** **** *** competitive / ******** ********

*******, *** '*****' ******, despite *** ****, ** not ********** ***** **********, ** it **** **** * subsection ** ***** ************, which ********** *** ******* / ********* ** ********** both ***** ** *** official ***** ********.

******* ** ****, *** attempt ** ******** *** Bridge ** * ******** to ******** **** *** recorded ***** ********** **** Milestone ** * *** party *** ***** *********** risk ** ******* ********.

************

*** ********* ***** ******** ***************** **** ******* **** R2 ** ** ********** charge.

** ** ********* ** all******** ** ************** *** ****** *** tiers (** *** *********).

ONVIF ****** ******

**** **** ** ** a ******** ****** *********, not ***** **** *** Milestone ****** ******.

** *** ** ********* on *** **** ****** or * ******** ****** if *** **** ** a *******. ** *** *****, CPU ****** *** ***, only ********** **** ** 1-2% *** * ******* (mixed *********** **** **** to ***).

*************

***** ** ****** ************* required *** *** ***** Bridge **** ***** **** needing ** ****** *********** to *** ********* ****** during ************.

**** *********, ***** *** RTSP ***** *** ** changed (******* ** *** and ***, ************) *** users *** ****** ******* created

*** ****** *** ** ***** Bridge ************* ******** ******** which *** ********** ***** ******* (*** actual). *** **** ********** stream ** **** *** ONVIF ** **** ** RTSP, ********** ** **** is ******* ****, **** ** transcoding ** *********.

********* ****** ** ***** documentation **** **** ******* the **** ******** ** connect ** *******. ***** *** also ****** *** "*** configurations **** *******" ****** to ****** *** ******'* actual ***** ******** ** VMes. *******, ** *** tests, **** ****** ****** less ********, **** ******** functioning ******** **** ** disabled, *** *** ********** at *** **** ***** configurations **** *******.

** **** ** ************* in **** ****** ** this *****:


Unable ** **** ******** *****

********* ****** *** ***** Bride ******** ******** ***** via ******* *. *******, **** is ** ******* ***, as **** *** ***** (Axxon *** **********) *** officially **********. ********, ** our *****, ***** **** was ****** ** ******* to *** ****** *** stream **** *****, *** alone **********.

Connecting **** ***** ****** *******

***** ****** ********** **** ** ******** and ******* ** *** ONVIF ****** ******* ******, with **** ***** ******** displayed *** *** *******. *******, configuration ************ ** ***** DM *** *** ******** properly, **** *****, *******, time, *** ***** ******** not **** ** ** configured ** **** *** be **** **** ***** devices.

**** **** ***** ** provides *** ******* *** to ****** ** ***** Bridge ******'* **** ***, found ** *** "**** Video" **** (********* ******* *****).


******* ******* *** **** information ** ***** ** should *** *** ***** **** ****.

VMS ***********

** *** *****, ********** to *** ***** ****** via ***** ****** ** most *****, ********* *****, Axxon, *** *******. *******, when attempting ** ******* **** Exacq ** *******, *** Milestone ***** ****** ******* crashed *** *** ** be ******** *********. ***** issues ******** ********** ** number ** *******, **********, or ****** ********.

**** ******** ******* ****** was **** ** ******** connect *** ****** ***** Bridge *******, *** **** when *** "*** ************** from *******" ****** (********* above) *** ********.

** ****** ***** ****** in **** *****:


****** ** ********* *** streamed ********, ****** ************* (below) *** *** ******** did *** ******** ** ACC ** *** *****, eliminating *** *** **** benefits ** ***** ***** over ****. **** ****** configuration ***** **** ** renaming ******* ****** ** ACC.

RTSP ***********

*** ***** ****** **** ****** an **** ****** *** camera *********, ***** ****** without ****** ** *** VMSes ** *** *****, in ******** ** *** ONVIF ***********.

**** **** ** ** typical **** **** *******, no ****** **** *** or ***** ******, */*, or *** ******* ** supported.

**** ****** ********

*** ******** *** ** locate ****** **** **** is *** ***** **. Users *** ****** **** the **** *** **** the **** ***** **** and ***** ** **** their *** (** *********).

** ***** ** ** unavailable, ***** *** ***** the *** *** *** following ******:

****://*********************:***/****/***********

********* ******** ***** ************ for ******** ****:

** ********* *** ****** GUID ** ** ******** Advanced ******** ** ********* Husky ******** ********, **** the ********** ******, ******** to *** ******, ****** the **** ***, **** down **** *** ***** on *** ******. *** GUID **** ** ********* at *** ****** ** the **** ***.

** ********* *** ****** GUID ** ** ******** Professional ******* ** ******** Milestone *****, ******** ** C:\ProgramData\Milestone\Milestone ************ *** **** the “*************.***” **** ** Notepad. ** * ****** for *** **** ** the ****** (******** *** camera ** ***** ** the ********** ***********). *** line ******** ***** *** name ** *** ****** will ** *** **** for *** ******.

******** ****** - ******************>

********-****-****-****-****************>

Software ******** ****

*** ********* *** ******** were **** ** **** test:

  • ********* ******** *********: **** R2 **.**
  • ******** ******* ****** **********: 5.8.4.10
  • ***** ****: *.*.*.****
  • *********** **********: *.*.*.*****
  • ******* ******** ******: *.* SR *
  • ******* ***** *********: *.*.*.*****
  • ***** ****** *******: *.*.***

Comments (15)

Undisclosed Integrator #1

07/06/16 01:27pm

"The support would however be limited to the functionality of providing video out. Support on the receiving end, the 3rd party client, is not in scope for Milestone support."

For integrators, this translates to a lot of finger pointing.

I don't blame Milestone. It is logical that they cannot support someone else's product. However, it still makes a challenge when two parties do not support connection to each other's product. This makes the functionality of limited use as updates on one end or the other could break it.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Sergey Bystrov

NetworkOptix
07/06/16 04:44pm

I have to admit this is the key here.

  • ONVIF Device Manager was able to connect to the Bridge and stream all cameras without issue (live video only, not recordings).


It could be a million reasons why VMSes do not recognize milestone ONVIF( could be not Milestone issue. For example VMSes are counting on the fact that profile could be changed, since cameras normally allow it, unlike Milestone).

For the developer who needs to integrate with Milestone the fact that it works well with ODM - is all what is needed.

Agree: 2
Disagree
Informative
Unhelpful
Funny
Avatar

Murat Altuev

AxxonSoft | In reply to Sergey Bystrov | 07/08/16 06:17pm

I'm sure that it is Milestone's issue. Axxon, Genetec and Exacq are officially compliant ONVIF clients, while Milestone ONVIF bridge is not official compliant ONVIF device. May be they need to try to pass testing process and become listed and then it will work well, I believe.

Agree: 2
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #3

In reply to Murat Altuev | 07/08/16 07:44pm

I think the problem is partly due to the fact that ONVIF Profile S is designed to provide an interface to encoders, i.e. cameras. For it to make sense on a VMS, the VMS would have to re-encode (i.e. transcode) the video output rather than just forward it from the camera. Many of the ONVIF XML packets are based around configuring the encoder (e.g. frame rates, protocols, resolution, GOP, audio/video protocols etc) , but since the VMS has no encoder to configure it is questionable how it handles this.

Sergey is right I think. The ONVIF clients are probably confused that they can't find a useful profile, can't modify a profile, and can't create a new one...

If the VMS is just forwarding video, then IMO there is little advantage in using ONVIF over just plain RTSP.

Agree
Disagree
Informative
Unhelpful
Funny

John Honovich

IPVM | In reply to Undisclosed Manufacturer #3 | 07/08/16 07:47pm

The ONVIF clients are probably confused that they can't find a useful profile, can't modify a profile, and can't create a new one...

3, thanks, that makes sense to me. Milestone did tell us originally that:

Most, but not all of ONVIF will be supported, most notably changing configurations via ONVIF will not be allowed

And as for:

If the VMS is just forwarding video, then IMO there is little advantage in using ONVIF over just plain RTSP.

On the other hand, PTZ control would be useful, maybe knowing when motion is occurring (i.e., passing motion events) and, on the profile G side, getting recorded video.

Agree: 2
Disagree
Informative: 1
Unhelpful
Funny

Undisclosed Manufacturer #3

In reply to John Honovich | 07/08/16 07:52pm

PTZ control would be useful, maybe knowing when motion is occurring (i.e., passing motion events) and, on the profile G side, getting recorded video

Yes true, I stand corrected on my last point.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #3

In reply to John Honovich | 07/08/16 08:16pm

The question I ask then, for those who require ONVIF-OUT on a VMS, would it be better for the VMS to:

1) transcode the output, and hence probably support lower frame rates and resolution than the original stream.

2) or is there an expectation that the video output should be unaltered from the original video from the camera

The first would work well for mobile ONVIF clients, the majority of existing ONVIF clients, access control integrations etc, The second is more in line with what would be needed by law enforcement as evidence, although you'd think the VMS export options would be used in this case.

I am actually thinking (1) might be more useful, and the more natural implementation to go with the way ONVIF works.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed #2

IPVMU Certified | In reply to Sergey Bystrov | 07/08/16 06:30pm

For the developer who needs to integrate with Milestone the fact that it works well with ODM - is all what is needed.

Perhaps we should eliminate all the pesky self-certification requirements and just make ODM the standard bearer?

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #4

03/29/17 06:39pm

Can you provide any further details on how you were able to successfully add an Onvif Bridge stream to Genetec Security Center via RTSP?  Please outline the steps if possible.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed Manufacturer #4 | 03/29/17 07:18pm

We actually were never able to get it to work. From the report:

...when attempting to connect with Exacq or Genetec, the Milestone ONVIF Bridge service crashed and had to be manually restarted

I just tried it again briefly to see if anything changed, and it seems to no longer crash the service on the Milestone server, but now... the Genetec directory restarted. Not sure that's an improvement!

If anyone else has had success integrating it with Genetec, I'd be interested.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Alexander Bakke

In reply to Ethan Ace | 01/21/19 08:40am

Can you please clarify if it did or did not work with RTSP to Genetec?

Like Undisclosed 4 says below, your answer differs from what is written in the article.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Alexander Bakke | 01/21/19 11:03pm

Yes, RTSP streaming does work, but you cannot simply type in a URL in Genetec Security Center as you can in most of the other clients. You need to create a custom driver for it, which requires tools from Genetec which aren't publicly available to output an XML file which is saved to the server. So while it works, it's not so simple.

Trying to connect to the ONVIF bridge using Genetec's ONVIF driver crashed the Genetec directory service the last time I tried it.

Agree
Disagree
Informative
Unhelpful
Funny

Alexander Bakke

In reply to Ethan Ace | 01/22/19 07:53am

I appreciate the reply.

"RTSP Integration

The ONVIF Bridge also offers an RTSP option for camera streaming, which worked without issues in all VMSes in our tests, in contrast to the ONVIF integration."

Can you really use the words "without issues", when getting it to work requires the steps you described?

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #4

03/29/17 07:22pm

Thanks for the update Ethan.  I was basing my assumption that it worked from a statement in the original article :

"The ONVIF Bridge also offers an RTSP option for camera streaming, which worked without issues in all VMSes in our tests, in contrast to the ONVIF integration."

I am more interested in getting RTSP to work as opposed to ONVIF.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #4

01/22/19 12:37am

https://ipvm.com/forums/video-surveillance/topics/adding-rtsp-streams-to-genetec-security-center

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

This article is part of IPVM's 6,943 reports, 926 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