Exactly! The questions isn't why would they want to do it, the questions is "why not?" How much harder is it for them to write a SIP driver versus an ONVIF or RTSP driver? Add a simple two way communication button on the client software and your done. Tie into existing SIP based intercoms and speakers. I have been prodding other VMS companies about this for over almost two years. Other companies better start getting a clue and thinking about possibilties instead of just sitting back and going "we're not going to do in unless there's we get enough people asking for it and there's an oppurunity to make gobs of money at it". Hello, if you have people asking about something and you don't have it, they're just going to move on to someone else that does.
Genetec Adds IP Telephony (Sipelia)
Why would one of the biggest VMSes get into Voice over IP?
That is the big question as Genetec has announced Sipelia, a "communications management" module for their Security Center platform, running a dedicated SIP server and integrating intercom calls with video and access.
In this note we review what SIP is, Genetec's implementation, and how it applies to the security/surveillance market.
What ** ***?
*** ****** ********** ********** *********** ** **** ** ********* *** voice *** ***** ***** **** **. SIP ** **** ** **** ******** phone ******* *** **** *****, *** also ** **** ******* ********* ******** for ***** *****, ****** *********** ********* are ***** **** ** ****. ** most ***** **** *** (**** **** Protocol) *** ***** *** *****, *** TLS *** **********.
Sipelia ********
**** *** ************ ** *******, ******* has ******** *** *** ****** **** Security ******, ***** ** * ****, making ** ** ******** ******** ****** similar ** **** ******* ** ****** Server. **** ** ******** ** ******** deployment, ******* ** *********** ** * third-party ******, *** **** ********** *** operation ** ******* **** ***** ** Security ****.
*********
******* ******* ** *** *** ********* (expected ** *** **** **-** ****) but **** ** ******** ******* ** cameras, **** * **** ****** ******* and ********** ******** *** *******, ** well ** *********** ** ******** *******. Advanced ******** ***** ******** *** ***** recording.
Supported *******
******* ********** ******** *** ******** ******* from ******* [**** ** ****** *********],*********, *********** **** *******. ************, ***** ******** SIP ******* (*********, ******, ********* **** stations, ***.) *** ** ****, *** with ******* **** ******* **** *******. Official *********** ******** *** ***** ******* depend **** ******* *************.
**** **** **** *** ******* ** for ***** ****. ***** **** ******** with **-***** ******* **** ** ******** and ********** **********.
Why * *** ****** *** ************?
*********** **** *** ****** *** ******* has ******* **********:
- ********** ******: ****** ******** ****** ** ******** Center ****** **** ** ** **** together **** ***** *** ****** ******. Calls *** ** ****** **** ****** cameras ** ****** ********, ********* *** of **** ** ****** ***** *** trigger ******** ******** **** ******, *** more. ***** ****** **** ********** ******** with ******** ******** ******* *** *******'* prior *** *******, *** **** ******* digital */* *** ******** ** ****** events, **** ******* ***********.
- ****** *********: ****** *** ****** ***** **** the **** ********* **** *** ***** to **** ***** ***/** ****** ******, instead ** ******* ** * ***** or ***** * ********** **** ******* intercom *******.
- ******** ********* *********: ***** ******* *** *** *********, ****** running the ******** **** ****** *** ****** calls ***** * ** *** ** headset. **** ****** **** *** **** operators, ******** ******* *********, ** ****** easier ******** ** ***** ***** *** operator ** ** *****, ****, ** at *****. ****************** ******* *** ********* ******* ** *** **** inside ********* ******** *** ** ****. Additionally, ***** ******* *** *********, ********* hundreds ** ****** ****.
***** ********** *** **** ****** ********** only ** * *** *******.
- ********(**** ********* *** ****** **) ********* have ******** ********* ** ********* *** staff, ********, *** **********, **** ******** at ***** *********, *** **** ***** emergency ****** ** ****** *****. ***** could *** ** ******* ** ******* as *** ******, ******* ** *** 2-3 *********** ********* ******** ****.
- *-** ************ **** ** ******** ** ******** use ** ******* *** ******** ***** are ********* ******. ****** *** ****** of ********* *** **** *** ** low, **** ********* **** ***** ** answering ***** ***** *** ******* ***** via *** ******** ******** ****** ******* of *******, ***** ******* *** ********. Additionally, *********** ** ********* ***** ** each ******** *** ** ******, ** other ***** *** ***** *** * primary ************ ******* ***** **** ** a ********* ****** ******* ** * single ****.
************ **** ** *****-****** *********, **********, or ***** ********** ********** ********* ** not **** ***** ******* ** ******** call ********, ****** **** **** ****** to *** ******** ** *******.
An emergency phone done right in modern times is a sip phone able to survive a baseball bat in an inner city parking garage. Of course it makes sense to use SIP. That's what you'd do in the 21st century as opposed to the (sometimes antique) implementations inside some of these vendor's solutions. Watching the sales dude timidly type in 192.168... to configure the sadly primitive network stack on some of these solutions is just scary.
Also, admitting you're running SIP is a good step towards realizing you have audio streams, flowing both directions, along a network used for video surveillance.
By the way if they cared a serious IP phone vendor (Cisco, Avaya) could compete with Stenephon etc. in their sleep.