Milestone ONVIF Bridge Tested

Author: Ethan Ace, Published on Jul 06, 2016

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.

*** ********* ***** ****** ***** ** * ************.

********** ***** **** **** ********** *** ***** ****** ****** ****** system *********** **** *********, ***** **** ******* *** ********* *** greater ****-**.

***, *********'* ***** ******, ******** ****, **** *** ***** *********** of **** *** ******** ***** ***** **** *** ** *** bigger ******* **** **** *** **** ***** ****** **** ********, Exacq *** ******* ** ** *** ****.

*** **** ** ****?

** ****** *** ********* ***** ****** **** * ***** ********* Avigilon, ***** *** ******* ** *** *** ** ******.

[***************]

*******

***** ******** ** ** '*****' ******, ** ****** **** **** an '****' ****** *** **** ***** **** *******.

** *** *****, *** ********* ***** ****** ****** ** **** with **** *****, **** **** ******** ******* ****** **** ** connect ********, **** ***** *** ******* **** ******* *** ******* to ***** **** *******.

**** ********* ****** **** *** ***** ****** ******* *****, ****** it * ********* ****** *** ***** ***** ****** ** ******* via *****, ****** ** ** **** **** ********* ** *** up *** ***** ******** ******** **** ** *** ******* ***** in *** ***** ***********.

Key ********

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

  • ** *** *****, ********** ** *** ***** ****** ****** ******** when ***** **** *** ** **** ***** ******* * ***** (Exacq, *******, ******* ***** *** ***** ****).
  • ********** **** ***** *** ******* ****** *** ***** ****** ******* to *****, ********* ** ** ** ******** *********.
  • ***** ****** ******* *** **** ** ******* ** *** ****** and ****** *** ******* ******* ***** (**** ***** ****, *** recordings).
  • **** ******* ****** ******** ** *** ******, ********, *** *****.
  • **** **** ***** *** ********* ** *** ***** ** *** only ******* * *** ******, ***** ****, *** ****** ** connect ** *** ********* ******.

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

****** *** ****** *** ******* ****, ***** ** ********* * problem, ** ******* **** ******* ***** ** * ********* ** the ****** ** ***** **** ** '********' ******** ********* ********. On *** *** ****, ********* ********* **** **** ***** "******* *** ******** ***** *** ***** ****** ** **** ***** project ****, ********** ** **** ***** ********** **** ***." ** the ***** ****, ********* **** *****, "*** ******* ***** ******* ** ******* ** *** ************* ** providing ***** ***. ******* ** *** ********* ***, *** *** party ******, ** *** ** ***** *** ********* *******." ********, Milestone ********* **** **** ******** *** *** **** *** ******* monitoring *** **** **** **** ******** ***** *** ****** ***** used *** *********** / ******** ********

*******, *** '*****' ******, ******* *** ****, ** *** ********** ONVIF **********, ** ** **** **** * ********** ** ***** capabilities, ***** ********** *** ******* / ********* ** ********** **** sides ** *** ******** ***** ********.

******* ** ****, *** ******* ** ******** *** ****** ** a ******** ** ******** **** *** ******** ***** ********** **** Milestone ** * *** ***** *** ***** *********** **** ** working ********.

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

*** ********* ***** ******** ***************** **** ******* **** ** ** ** ********** ******.

** ** ********* ** *********** ** ************** *** ****** *** ***** (** *** *********).

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

**** **** ** ** * ******** ****** *********, *** ***** into *** ********* ****** ******.

** *** ** ********* ** *** **** ****** ** * separate ****** ** *** **** ** * *******. ** *** tests, *** ****** *** ***, **** ********** **** ** *-*% for * ******* (***** *********** **** **** ** ***).

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

***** ** ****** ************* ******** *** *** ***** ****** **** users **** ******* ** ****** *********** ** *** ********* ****** during ************.

**** *********, ***** *** **** ***** *** ** ******* (******* to *** *** ***, ************) *** ***** *** ****** ******* created

*** ****** *** ** ***** ****** ************* ******** ******** ***** are********** ***** ******* (*** ******). *** **** ********** ****** ** sent *** ***** ** **** ** ****, ********** ** **** is ******* ****, **** ** *********** ** *********.

********* ****** ** ***** ************* **** **** ******* *** **** required ** ******* ** *******. ***** *** **** ****** *** "Use ************** **** *******" ****** ** ****** *** ******'* ****** CODEC ******** ** ****. *******, ** *** *****, **** ****** proved **** ********, **** ******** *********** ******** **** ** ********, but *** ********** ** *** **** ***** ************** **** *******.

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


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

********* ****** *** ***** ***** ******** ******** ***** *** ******* G. *******, **** ** ** ******* ***, ** **** *** VMSes (***** *** **********) *** ********** **********. ********, ** *** tests, ***** **** *** ****** ** ******* ** *** ****** and ****** **** *****, *** ***** **********.

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

***** ****** ********** **** ** ******** *** ******* ** *** ***** ****** without ******, **** **** ***** ******** ********* *** *** *******. However, ************* ************ ** ***** ** *** *** ******** ********, with *****, *******, ****, *** ***** ******** *** **** ** be ********** ** **** *** ** **** **** ***** *******.

**** **** ***** ** ******** *** ******* *** ** ****** an ***** ****** ******'* **** ***, ***** ** *** "**** Video" **** (********* ******* *****).


******* ******* *** **** *********** ** ***** ** ****** *** our***** **** ****.

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

** *** *****, ********** ** *** ***** ****** *** ***** failed ** **** *****, ********* *****, *****, *** *******. *******, when ********** ** ******* **** ***** ** *******, *** ********* ONVIF ****** ******* ******* *** *** ** ** ******** *********. These ****** ******** ********** ** ****** ** *******, **********, ** Bridge ********.

**** ******** ******* ****** *** **** ** ******** ******* *** stream ***** ****** *******, *** **** **** *** "*** ************** from *******" ****** (********* *****) *** ********.

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


****** ** ********* *** ******** ********, ****** ************* (*****) *** PTZ ******** *** *** ******** ** *** ** *** *****, eliminating *** *** **** ******** ** ***** ***** **** ****. Even ****** ************* ***** **** ** ******** ******* ****** ** ACC.

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

*** ***** ****** **** ****** ** **** ****** *** ****** streaming, ***** ****** ******* ****** ** *** ***** ** *** tests, ** ******** ** *** ***** ***********.

**** **** ** ** ******* **** **** *******, ** ****** side *** ** ***** ******, */*, ** *** ******* ** supported.

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

*** ******** *** ** ****** ****** **** **** ** *** ONVIF **. ***** *** ****** **** *** **** *** **** the **** ***** **** *** ***** ** **** ***** *** (if *********).

** ***** ** ** ***********, ***** *** ***** *** *** via *** ********* ******:

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

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

** ********* *** ****** **** ** ** ******** ******** ******** or ********* ***** ******** ********, **** *** ********** ******, ******** to *** ******, ****** *** **** ***, **** **** **** and ***** ** *** ******. *** **** **** ** ********* at *** ****** ** *** **** ***.

** ********* *** ****** **** ** ** ******** ************ ******* or ******** ********* *****, ******** ** *:\***********\*********\********* ************ *** **** the “*************.***” **** ** *******. ** * ****** *** *** name ** *** ****** (******** *** ****** ** ***** ** the ********** ***********). *** **** ******** ***** *** **** ** the ****** **** ** *** **** *** *** ******.

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

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

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

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

  • ********* ******** *********: **** ** **.**
  • ******** ******* ****** **********: *.*.*.**
  • ***** ****: *.*.*.****
  • *********** **********: *.*.*.*****
  • ******* ******** ******: *.* ** *
  • ******* ***** *********: *.*.*.*****
  • ***** ****** *******: *.*.***

Comments (11)

"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.

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.

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.

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.

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.

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.

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.

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?

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.

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.

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.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

The IP Camera Lock-In Trend: Meraki and Verkada on Jan 18, 2019
Open systems and interoperability have not only been big buzzwords over the past decade, but they have also become core features of video...
Mobile Surveillance Trailers Guide on Jan 17, 2019
Putting cameras in a place for temporary surveillance where power and communications are not readily available can be complicated and expensive....
Avigilon Favorability Results 2019 on Jan 15, 2019
Since IPVM's 2017 Avigilon favorability results, the company was acquired by Motorola and has shifted from being an aggressive startup to a more...
Gorilla Technology AI Provider, Raises $15 Million, Profiled on Jan 15, 2019
Gorilla Technology is a Taiwanese video analytics manufacturer that recently announced a $15 million investment from SBI Group, saying this...
Pelco Favorability Results 2019 on Jan 11, 2019
Pelco had a significant favorability problem amongst integrators in our previous study (see 2016 Pelco results). Now, in the first edition of our...
NTP / Network Time Guide For Video Surveillance on Jan 10, 2019
Inaccurate time can lead to missing or inadmissible video, yet this topic is often overlooked, with cameras and servers left defaulted,...
Wavelynx Access Control Manufacturer Profile on Jan 10, 2019
Denver-based WaveLynx is not well known as an access reader manufacturer, but OEMs for big industry brands including Amag, Isonas (Allegion),...
H.265 / HEVC Codec Tutorial on Jan 08, 2019
H.265 support improved significantly in 2018, with H.265 camera/VMS compatibility increased compared to only a year ago, and most manufacturers...
2019 Video Surveillance Cameras Overview on Jan 07, 2019
Each year, IPVM summarizes the main advances and changes for video surveillance cameras, based on our industry-leading testing and...
IPVM Best New Products 2019 Opened - 70+ Entrants on Jan 07, 2019
The inaugural IPVM Best New Product Awards has been opened - the industry's first and only program where the awards are not pay-to-play and the...

Most Recent Industry Reports

The IP Camera Lock-In Trend: Meraki and Verkada on Jan 18, 2019
Open systems and interoperability have not only been big buzzwords over the past decade, but they have also become core features of video...
NYPD Refutes False SCMP Hikvision Story on Jan 18, 2019
The NYPD has refuted the SCMP Hikvision story, the Voice of America has reported. On January 11, 2018, the SCMP reported that the NYPD was using...
Mobile Surveillance Trailers Guide on Jan 17, 2019
Putting cameras in a place for temporary surveillance where power and communications are not readily available can be complicated and expensive....
Exacq Favorability Results 2019 on Jan 17, 2019
Exacq favorability amongst integrators has declined sharply, in new IPVM statistics, compared to 2017 IPVM statistics for Exacq. Now, over 5 since...
Testing Bandwidth Vs. Low Light on Jan 16, 2019
Nighttime bandwidth spikes are a major concern in video surveillance. Many calculate bandwidth as a single 24/7 number, but bit rates vary...
Access Control Records Maintenance Guide on Jan 16, 2019
Weeding out old entries, turning off unused credentials, and updating who carries which credentials is as important as to maintaining security as...
UK Fines Security Firms For Illegal Direct Marketing on Jan 16, 2019
Two UK security firms have paid over $200,000 in fines for illegally making hundreds of thousands of calls to people registered on a government...
Access Control Cabling Tutorial on Jan 15, 2019
Access Control is only as reliable as its cables. While this aspect lacks the sexiness of other components, it remains a vital part of every...
Avigilon Favorability Results 2019 on Jan 15, 2019
Since IPVM's 2017 Avigilon favorability results, the company was acquired by Motorola and has shifted from being an aggressive startup to a more...
Gorilla Technology AI Provider, Raises $15 Million, Profiled on Jan 15, 2019
Gorilla Technology is a Taiwanese video analytics manufacturer that recently announced a $15 million investment from SBI Group, saying this...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact