Key ******
*** *** ****** *******:
- "********" - **** **** ****, **** integrators *** ***** ** * ********.
- ******** *********** ***** *****
- ********** ***** *** **** ** *** direct ******* **** *****
- ******** **** *** *********** ** *****, such ** ******* **** *.***, ********* and **** (************* * ******* ** ************).
- **** ** *********** / ********** ***** ONVIF
Standards ****
**** *********** ********** ******* ***** ** being * ********, **** ****** *** question **** ** ********* ** ****:
- "** ******* ** ** ** ******** standard."
- "******** ******** - **** ** *** when ****** **** ******* ******* ******* VMS."
- "***** ***, ***** *** **** ** a "**********" **** * "********." *****, it ******* *****-********** ****** ***** *** cameras **** **** **** **** *** recorders."
- "* ***** *** ********* ** **** a ******** ************* ******** ** *** industry."
- "*** * ******** ** **** ** comment"
- "******** *** ****** **** ** ****."
- "**'* *** ******* **** ******** *** IP ******."
- "*************** ***** **** ****** *** *** integrator."
- "* ***** *************** ** *** **** is * **** *****."
- "**** ** *** **** ***** ** a "********" ** ***** *** ********!"
- "******* *** ********* ******** ** ******* it's ***** ** *** ******."
- "**** **** ** *** ********* **** the ***** ** ******* *** ***'* play ********."
- "* **** ***** ****** ******* ** the ******** ** ******* **********."
- "* ***** ***** *** **** * great *** ** ************* ******** *******."
- "****'* *** ** ****? ** **** standard ** **** *** ****** **** is **** ****"
- "********* *** ****** **** *** *** industry. ******** ******-**** ** *** ** started ****** **** * ****** ***** ago **** *** ** ** *********."
Positive ******
*** ***** ******** ******** **** ***** ONVIF's ******* **** ****** ** *** industry:
- "*** ******* * ***** ****** *** industry ** **** *******. **** ** has *** *********, *** *******, ****** positive."
- "************* ******* ** ** *********** * ton ** ******* ** ***** *** right ******** *** *** *********."
- "***** - ** * ***** **** and **'* **** ** ***** ** a *** ********* **** ****** ******* to ******** *******."
- "****** *** **** ******* ****** *** matching ****** *** ** *****."
- "** ****** ******** **** ****** *****? It ****'* ******. *** *** *****."
Not ******
*******, **** ** ***********, ********* **** who ***** ******** *** *****, *** cite ******** ***** ***** *** ***** far ****** *** ****** ******** ***** beyond ***** ***** ********* *** *************:
- "** ** **** ** *** ***** functions."
- "**** * ***** *********, **** *** take **** ********* ** *** *** features ** *** ******."
- "******* ** **** *** *********** ** always *** *** ****, ********** **** it ***** ** *********."
- "*** ******* ***** ** ********* *** functions ***’* **** ** **** *********."
- "** *** **** **** ***'** ****** to **, *** *** ******* ** accept **** ***********, ** ***** ****.
- "** *** "*****" **** *******. **** usually ********** **, "*** *** *** and ******" *** *** **** **** feature **** ** *** *** ********* record ** ******."
- "***** ***** ******* *** *********, **** PTZ ******* (********, **********, ********) ******* is ****** ** **** *** * failure ** *****."
- "** ***** **** ****** ********* *** want ***'* ******** ********. ***** ******."
- "***** ** ****** ******* * *** and *** ***** * ***'* *** a ****** ** ** **** * want **** ****** *** ****** *** VMS **** ******* *** **** *******. Still ***** * *** ** **** I *****."
- "***** ***** *** *** ****** **** trying ** *** *** **** ********* of *** ******. ** ********** **** problems, *********** ***. **** ** *** onvif ** * ******** ** *******."
- "****** **** ** *** *********** ******** on **** *******."
- "******* ** **** *********, *** *****'* cover *** *** ********** ***** *********."
- "*** ********* *** *** ****, *** I ** *** **** *** ********* that **** ***** *********."
- "***** ** * *** ** **** for *********** ** ****** ******* **** features."
- "*** ** ********** ** ***** ** what ******** *** ******** ********* ******* ONVIF ***********."
- "***** ** ******, *****'* ****** ****. No *.*** *******."
- "** *****´* ****** *.*** *** ***** device ** ***** ********** **** **** protocol. ** ******* **, ** *********** in ***** **** * ****** **** that ** ******* ***** **** *****, for *******, **** ** **** *** other ****** ***** *** ************* **** their ***'*."
Profile * **** ** ******* ********** ********
** ****,***** ******** ******* * ***** **** to *********** ** *** *********** **** *********** understandably ********** *****. *******, ** ** March ****, *** **** ** **** publication, ***** ******* * *** **** 1 *** ********** **********, ****** *** quite *******. ** ** ******** **** this **** *******, ******* ***** *************, in *** **** ****.
Compliance ******
*** ***** *** ******* **** *********** called *** *** *** **** ** actual **********. ***** ***** *** ** official *********** *******, *** ******* *** claim ** ** ***** '*********' ** 'works **** *****' *** *** ********** that ***** **** ********* ** **** low (** **** ******* **** **** the *****). **** *** ****** ********** complaints:
- "** ****** ******** ** * ********."
- "* **** ***** *** * *** for ***** *** *** ** *** more ******** ** ************ ** ******."
- "*** **** **** *** ***** ** even **** *** ********** ** ******* their *********...***** ****** *****."
- "******* *** ***** ***** ** ******** without ***** ********, *** *** ******** rendered ** **** *********. ** ***** was * *****-**** ** ***-********* ********, it ***** **** ** **** *********."
- "***** ******** ********* *** ***, * don't *** **** ********* ** *****. It's **** **** *** ****** *** made ** ****** * ********, *** it ***** ** **** *****. ** virtually *** ****** ***** ** ***** standard, ****'* *** *****?"
- "** **** *********, *** ***** ** be ******** ****** ** ************* ******* self ******** *************."
- "***** ** ** ***** ** *** "standard". **** *** ***** *** ******** in *** ******. *** ****** ****** but ***** ***** ** ********."
- "* ***’* **** *** ************* ** the ************ ***** ***** ***** ** why *** *** *** ******* ******** work."
- "*** **** ********* ***** ***** ********* and ***** *** ***** **** ********."
- "** * ********, ******** *** ***** be **** ****** ** ******** ******** and *********. ***** ******** ** '***** conformant'"
- "***** ** * ******** ** * good **** *** ***** ****** ** more ********* *********** *** ********** ** Onvif."
- "***** **** ***** ******* ** ***** - *** **** **** **** ****."
- "*** **** **** ****** *** “******” that **** ************* *** *** ***** seal ** ************* ** ***** ******** without ****** ***** ********** **** *** standardized ***** ********"
- "* **** *** ********** *** ******** to ****** ***********."
**** *********** **** ***** **** *** years, *** ********** ** *** ** that **** ** *** **** *** take ****** ****** ***********. ** ** strange. ***** ** *** * ***** organization, **** *** ******* *** ****** membership **** ** ~$*.* ******* (***** on ***** ******* ************* *********). *********, ***** **** *** *** enforcement ** * ******** ** ***** spending.
*******
*** ******* ** ***** ********* ******** for *****, ********* ** *** **** Profile * ***** *** ** *******, as **** ***** ***** *** ******* pain ***** *** ***** *****.
Comments (17)
Undisclosed Distributor #1
ONVIF is a great, but very ambitious project for our industry. Unfortunately you can't just run into a room and declare yourself the standard, it takes years and years to build the groundwork necessary to be accepted. ONVIF doesn't have the juice that IEEE or ANSI has, so it's a very hit-or-miss situation. Also, when dealing with most of the manufacturers of low-cost products that we see every day, they seem to do just enough to get on the ONVIF list and not more in hopes of having customers purchase ALL of their CCTV products from them and not mixing and matching vendors.
Create New Topic
Undisclosed Manufacturer #2
What gets me about ONVIF is it's pay to play. Has anyone ever looked to see who authors these standards? Designee's (authors) with relationships with AXIS, Sony, Bosch, etc. All well bankrolled, all writing the standards, just for how a client connects to / interacts with to a MAC address (IP cameras and encoders).
Sure, it gives the warm and fuzzy knowing that your actually getting something that may work with a minimum "S" profile, but "T" compliance is another story. Why would you allow someone to say they are compliant when the entire feature doesn't have to be met, then allow exceptions.
Create New Topic
Undisclosed #3
One thing that would be interesting to know, via intergrator poll maybe, would be what percentage cameras actually connect (in the field) via ONVIF.
is it 5% or 50%? apologies if this info has already been reported somewhere...
Create New Topic
Undisclosed Manufacturer #4
ONVIF is outdated and insecure backed by those ancient minds.
No new players will adopt onvif. There are already many successful startups because they didn't fall trap to onvif but their own closed but efficient protocol.
Create New Topic
Undisclosed
OnVIF isn't a manufacturer yet you dumped it in your 2019 end of year manufacturer favorability summary. By that logic does Wiegand, or OSDP, or HD analog video, or IPv6 merit a survey?
My only disagreement is that the label is mildly misleading. I appreciate your tracking of OnVIF.
Create New Topic
Undisclosed
OSSA? You mean android for cameras? Do we have to?
Create New Topic