What Intercom Shootout Criteria To Test?

We are putting together a shootout report comparing intercoms from our recent individual tests. This intercom shootout will be similar to other access shootouts like Mobile Access Control Shootout - Farpointe, HID, Openpath, Nortek, Proxy

Which specific criteria would you like us/ is most useful for you to compare?

Our initial criteria:

  • Remote/Cloud-Based Call Answering: Does the intercom support calling mobile phones via app/cloud connection?
  • Day/Night Video Quality: All of the devices have cameras, but how well do they work to 'see' details in various light/no light situations?
  • SIP/PBX/VoIP/ONVIF Integration: How well do the intercom features integrate with phone and surveillance systems?
  • Audio Quality: Do the intercoms use effective noise-canceling to make callers easy to hear over common outdoor background noise?
  • Indoor Master Requirement?: Does the system use a mandatory indoor station, or is it optional? Can software phones be used?
  • Mount/Installability: Does the unit have options for recessed and surface mounting? What kind of tamper/security hardware is used to secure the device?
  • Access Control Integration: How well/ which access platforms supports the intercom calling and integrated access features like lock relays or onboard readers?
  • Keypads/Readers/Custom Displays: Which units can be 'customized' with hardware reader/keypad modules or screens for access control/ mass notification/ user feedback?
  • Pricing: How does unit pricing for both door station, and additional licensing or hardware compare?

Which other comparisons should we evaluate? Thanks!

Note, we have already done individual tests and this is now to compare/shoot them out against each other. Below are the individual test reports:

Login to read this IPVM discussion.
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.

**** ***** ** ********, some **** ******** ** non-network *********:

(*) ** *** ****** better ****** *** *** installs ****** ****-*****? ******** wiring *** ** * nightmare **** ********* ** older ******. *-**** *** 4-wire ******* **** ********* layout *** ****** **************.
(*) ** ***** **** line ** ***** ***********? This *** ********* *** need ** (**)**** ** multi-tenant ********, ******* *** intercoms ***** *** ****** who *** ****** * door **** ***** *****.
(*) ****** *** ************ / *************
(*) ******* *******, ******-**********, and ********* ****

****, ***** *** ******* and *********** ** *** vendor ****.

*** ** **** ****** multiple ***** ****** **** intercom ***** ** *** time? **** ** *** only **** *** ***** deployed *** **** ********** get *** ***** ****** in ** *** **** time. ***** **** **** at *** **** ********* ways ***** *** ** answer * ****?

******** ************ **. *** Installation

*** *****. ****** *** looking **** *********, ********* feels **** ****'** ********** generally.

* ***** **** ** would ** ******* ** look **** ***** *** cloud *********, ********, ********* and ***************. *** * multi-apartment ***-**, **** *** system ****** ***** *** each ****** ***** ** only **** *** **** requests **? ** *** recording ***** ** ***** based? ** ** ****** exportable *** *** ** evidence.

******,

**** *

***** *** *******, ******.

***% ***** **** *** value *** ******** *** overlooked. ****’** ******** ** my ***** *** ********* seen ** ** ********* by ******** ************* ** terms ** ********/************.

*) *** ****** ** encountered ** *** *** comparisons (************* **** **********) was ******* **** / Algo *** *** ******* to ******* (**** ******** of) ***-****** *** ************* of ***** *********** *** failover ** *** **** itself.

***** *** **** *****’* have * ******, ******* our *** (*******) ******** an ********** ****** **** the ******** *********** ** they ****** ** *** in *** **.

*** ******** *** *** reaching ******* ***** *** if * ******* ****** without ******** (** ** primary ** *********** ** case ** ******* *******), redirect ** ***** *** P2P.

*) ***** **** ** see ** *** ********* routed **** ***** *** Business (*****/***** *******) ** other *****-***** **** ****** platforms ** * *** to ***** *** ******* audio ************* ** * SOC.

***** **** ** *** if *** ********* ****** into ***** *** ******** (audio/video *******) ** ***** cloud-based **** ****** ********* as * *** ** unify *** ******* ***** conversations ** * ***.

**'** *********/ ***** **** with * ****** ** tests, ************ ***** *** into ****** *** ********, and ** *** **** a *** ** * support **********.

*******, ***** *** ** different *** ** **** not ****** ****. ***, SIP ** ***** ******* as *** *** ******* than ** ** ***********. It ** ****** ** our ***** ** **** from **** ******* "**, ** ******* ******** SIP *** *** ***** or *****" ** **** ******* combination ** ***** ***************.

* **** **** ** call ****** ***** *********** help ******** *** ******** by ********** ******** *** formats, *** ** **** point, ** *** **** a *** ********** ** me (*** ******** **** SIP **********) **** * cluster ** *** ** for ***********.

******: *** *** **** build * ***** *** that **** ** **** you *** ******** ** the ****?

*****, ****, *********(*** ******) do *** **** **? Screw **** ********** ************** industry's ********* ******** ** idiotic ************* ********* ************ integrations **** ********* ******** insignificant ********** ********* ** ill-advised ** ******** *********.

***** ** *** ***** testing ******** ** *******, I ***** **** ** see ********* **** ***** like ** ** *** have ** ******* ** push, *********** ** ****** databases ** ********* ** clunky **** ** **** circa **** *********.

*****, ***** * ** here ** ***** **** Doe.*****: *** **, ********* John ***, ********* ***** is ****** ** *** visitor ****.

********* **** **** * options, *** *** ******** or ********* ******* *****. Reply ** *** ** option *** ***.

** ****** ****'* **** work, ****** *** **** access ******* ** **** door ** **** *** people *** *** ********** in *** ***'* **** to **** *** **********.

********** * ***'* **** to ** ****** ******** someone ******* ** ****.

*** ** ****'** ********* (i.e. ** *** **** for ** *******), **** you *** **** ** be ******** ******* ***** they're ****** ** ***** in...or **** *** ***** access ****.

*** *****:

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

****** ***/***/****

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

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

**** ***** ***** ****** interests *** ** ***** them ***** *****?

******

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

****** ** *** **** of ****, *** ***** is **** **********, *** a *** ** ******* in *** ********* **** would ** ******** **** them (**** **). **** are ****** *******. * drawback ***** ** ***** support ** ****** *** email (****** ****-**** *** top *****).

****** *** *** ********, George!

* **** *** **** for **** ********** ********, the ****** ** *** testing *** ******* ** ones ***************** ******** ************* ****. * ** ********* going ******* *** **********, and **** ** * pre-test ****** ***** **** at *** ******** ***. :)

** **** **** **** to *********** ********* ******* like **** *** ************* with ********* ********* **** SIP **** *** *******.

*******, ********** ******* ** Algo, ******, *** *********** intercoms **** ** ********* we ******** *** ********** evaluations. *** *** **** shootout, ******.

****** *** *** ********!

*** ****** ** ******** different, ************ ******** *** multi-tenant *********** ***********, *** offers ********** ***** **** compared ** *** ****. Could ** ** ********?

IPVM Image

*** ***** ** *** recently **** *** **** A8105-E ***** *** **** aiming *********. * ***** the ** * ****** issue. *** ****** ****** us ** ** **** to *** *** ****** downward ******* ****** *** hood *******. *** ************ who ********* *** ***** too **** ***** ** coming **** *** ** lower ****.

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

****** **** ******** ***** and **** ******, ** well ** *********** **** ACS.

**** ***** **** *****-****** Technology **., ***

*** ****** ******* ******** streams *** *** **** to **** *** **** from *** ***.

*** ***** *************/**** ***** standard *** ***** ******** or ** ** *** an ************.

- **********

- ***** / **** to **** *******

- ********* *****

***

*** ******** "***** *" issues

*****, * *** ***** back, * *** ******* for ********* ******* ** Ring, *** ***** **********. I **** ****** * Canadian ******* ****** ***** (dbell.ca). * ***** ****** the *******, *** ** still ******** ******* *** the **** ******. ****** consider ***** *** * future ******/********. * **** no ***********.

* **** ***** ****** above, *** *************, *** thus *** ******* ** work **** ** ******** NVR.

******, *** *'* ******* forward ** *** ********!