Broadcaster™ Testing
25
This Device must be tested at least once a week. Failure to do so can result in no alert notification and
a loss of production.
Call/Text Testing
SMS Text Message
—A Weekly text message will be sent every Wednesday at noon (the date and time must
be set up correctly). The message only goes to the first text number in the list and will be sent only one time.
Sending the correct acknowledgment code will conclude the test and it will be recorded that the user
responded to the test.
Server Calling and Texting
—It is recommended that a test call be run one time per week. This can be done
from the Dial Test Screen.
A "1" must be entered in front of all Voice and Text call numbers.
Example: Sever Voice test call. Result: You should receive a call with the status.
Example: Sever Test Text. Result: You should receive a call with the status.
Cellular Calling
—It is recommended that a test call be run one time per week. This can be done from the
Dial Test Screen.
Landline Calling
—It is recommended that a test call be run one time per week. This can be done from the
Dial Test Screen.
System Alert Testing
It is recommended that at least 1 time per week, a test alert is sent from the control(s) being monitored. It is
recommended that the alert be allowed to move through every number in the notify list to make sure that number
is called and/or sent an SMS message.
Battery Testing
It is recommended that at least 1 time per month, the battery is checked on the Broadcaster
™
. To check the
battery, remove the power cord and allow the system to keep running on the battery backup. Allow the
Broadcaster
™
to contact all numbers on the notify list before ending the test. The battery should have enough
power to go through the entire notify list at least one time. If it cannot, then the battery must be changed.
Broadcaster™ Testing
Warning:
Note:
1)
2)
3)
1)
2)
3)