turning off siren, but sending emergency signal

newalarm

Active Member
I have heard of alarm systems in Europe being set up for the following situation:

Someone breaks into your house and the alarm goes off, and assailant holds you hostage or threatens you, you can input a special code that turns off the siren, and lets monitor company know that you are being held hostage/assaulted. I guess it is similar to a panic button.

Does anyone have any experience with this and how it would be programmed?

Thanks.
 
Duress or ambush are typically how it's referred to within programming.

Depends on the panel what and how it's used. Some used to be a code incremented by 1 (1234, then the duress would be 1235) or repacing the last 2 digits with 99 or similar (hard coded within the panel). Most newer panels allow programming the duress code itself.

Usually they work by sending the code after the digits are entered or the complete disarm sequence (IE: Vista 20P's send after entering the code only).
 
I assume that by the few responses, this is not a common use in residential? We live in city and though i doubt anything will ever happen, It seems like it would be a good thing to have just in case.
 
I use it. On the ELK M1, I set up duress codes for both my wife and me. You need to discuss EXPLICITLY with your alarm monitoring company what their response should be.

If either of us use the duress code to
Disarm the system, the monitoring company gets the duress alarm. We have instructed them to immediately dispatch police, and under NO circumstance to call us first.

They made us sign a special release form stating that they are not responsible for any damages that the police may cause if they are dispatched for a duress call and kick down the front door.
 
Very common in residential, however I know of some large installation companies that used to charge extra to enable the reports from the panel on residential accounts.

Commercial accounts typically would be charged for a panic alarm system/services as there is typically a large waiver involved with a commercial system, as that is alluding to a safety factor or system...plenty of lawsuits involved that are noteworthy.

As far as a central station, it would be irresponsible and against every CS I've dealt with, normal SOP's to not verify a duress signal. Manual keypad panic, I could see a verification after dispatch, but duress and anything templated as HUA (hold up alarm) should not be verified....standard CS best practices.
 
Tip, never use a + 1 duress code. This was standard on older panels until it became obvious that this was the leading cause of false alarms. Make the duress or ambush code unique. If you are worried about remembering it, use a pattern like 2580, straight down the middle.
 
According to the ELK documentation, when you set up a Duress user: "CAUTION: The communicator report code MUST also be programmed!"
 
NextAlarm tells me: "CID is the preferred reporting format and the CID reporting code for Duress is 21"
 
Now I'm stumped. I could list all the things I've tried, but does anyone know where the communicator report code must be programmed? Just having the Duress box checked in the user definition does not send a duress code.
 
RichardU said:
According to the ELK documentation, when you set up a Duress user: "CAUTION: The communicator report code MUST also be programmed!"
 
NextAlarm tells me: "CID is the preferred reporting format and the CID reporting code for Duress is 21"
 
Now I'm stumped. I could list all the things I've tried, but does anyone know where the communicator report code must be programmed? Just having the Duress box checked in the user definition does not send a duress code.
 
In ElkRP2, under the Communicator section, click Area RCs.  Duress is in that list.
 
Back
Top