Home ] Up ]

Return to Reliance Alarm Company            Return to Lou Arellano, III Home Page

The Automatic Test Signal

Copyright 1993, 1994, 2000 Luis Arellano, III

Through various means, Alarm Dealers are always discovering systems that are unable to communicate correctly with the Central Station.  Routine diagnostic service calls are one means, but more often, unfortunately, the client calls to say there was no response to an alarm by the Central Station.  Some common causes include:

                - Dialers hit by surges, storms or static discharges

                - Modifications, repairs and damage to phone wiring

                - Phone lines that are turned off to cut costs

                - Changes to the phone network itself; access code changes

                - Changes in optional phone services (e.g., Call Waiting)

                - Incorrect data entry at the central station

                - Dialer program incorrect, scrambled or out of date

In many cases it becomes apparent that alarm service has been disabled for weeks or even months prior to the discovery.  We regret that this can and does happen, but practically all of the above causes are beyond the control of Reliance Alarm Company or any other alarm company.  It is simply an inherent risk common to digital dialers, which are essentially  "unsupervised."  This means we have no way to verify that a system can communicate, except by having it send a signal.  If you never trip the system, you cannot be certain.

WHAT CAN BE DONE ABOUT THIS?  To increase the reliability of digital communicators, manufacturers are giving systems the programmable ability to send test signals at regular intervals, typically every 24 hours.  Some sensitive applications are set to send a signal as often as every hour.

HOW IT WORKS:  When so programmed, your system will use the regular phone line to transmit test signals, usually at a time when you are unlikely to be using the line yourself.  The central station computer knows to watch for that incoming signal.  If it's received, the test is recorded in memory, but if it is missed, an "exception" pops out for operator handling.  Notification is made according to the call sequence specified at the time of setup.  Measures can thus be taken to determine if the outage is temporary (e.g., a brief phone system outage) or if a repair call needs to be scheduled.

THE COST:  Most of the security systems we service are programmable to send daily tests, for a typical monitoring surcharge of $5.50-$6.50 per month.  In a few cases, particularly where an 800 number is being dialed, the cost may be slightly higher.   Depending on your location, it is possible you may also see a toll on your phone bill for each message, typically 5-20 cents.

There is a one-time setup charge, which will vary with the nature of the programming we must do.  In many cases it can be done remotely, without a service call, for a flat $25.  (This is what it will be if done at the time of an original installation.)  Some systems may require updating or more involved programming.  The only way to find out for sure is to ask us.

Please call or write if you are interested in having this important optional service, designed to enhance the reliability of your system and your peace of mind.  (Your system may already be configured for automatic tests, but ask anyway if you are not certain.)

Note that this optional service is not intended to provide a notification that a burglar has cut the phone line just prior to an intrusion.  For answers to that concern, see What happens if a burglar cuts my phone line?

 

[ws5:testnotc.02 Rev 10/6/2000]