The IP Alarm Transmitter requires no additional hardware; only the Controller is required.
Firmware requirement: To use IP Alarms, the Controller must be using Application version 2-3-11 or higher. Check the 'Application' field in the Controller's properties.
If the customer requires third-party monitoring, you can configure the IP Alarm Transmitter as an alternative or addition to the Permaconn or Alula alarm transmitter.
In the SMB Installer Portal, click the MONITORING tab.
Enter the Account Code received from the monitoring station and click SAVE.
The IP Alarm Transmitter item displays.
Enable the toggle next to the IP Alarm Transmitter.
Note: If you are also enabling the Permaconn or Alula alarm transmitter, select which transmitter is the primary one from the Primary option (next to the 'Account Code' field).
Click on the IP Alarm Transmitter to open its properties.
The IP Alarm Transmitter lightbox displays.
Select the required Protocol for transmitting to the monitoring station.
CSV uses Comma Separated Values (CSV) format for transmitting alarms. This method uses TCP/IP and is unencrypted.
DC-09 Gallagher uses Gallagher's own format of DC-09. Select this option if you are transmitting alarms to a Gallagher receiver. Encryption is available.
DC-09 SIA uses the Security Industry Association (SIA) protocol for DC-09. You will most likely want this option when transmitting to a third-party monitoring station. Encryption is available.
If you selected a DC-09 protocol, the Encryption check box displays. Optionally select this check box to encrypt all transmissions from the Controller, then enter the Encryption Key.
You can either generate this Encryption Key yourself and then provide it to the monitoring station, or request an Encryption Key from the monitoring station. Either way, the monitoring station must have the same key that you enter here.
For the IP Alarm Transmitter to provide authentication, select the Authentication check box and enter the Username and Password that will be used by the monitoring station to authenticate the data received.s
Note: The Username and Password must not contain the following characters: < > & ‘ “ ,
Enable as many Receivers as you like; there are two available. You must enable at least one Receiver for the IP Alarm Transmitter to function.
Transmissions are sent to 'Receiver 2' if attempts with 'Receiver 1' fail.
In the IP field of the enabled receiver(s), enter the IP address of the receiver. This must be provided to you by the monitoring station.
In the Port field of the enabled receiver(s), enter the Port used by the receiver. This must also be provided to you by the monitoring station.
To enable polling, select the time under the Polling field and enter how often a heartbeat will be sent to poll the receiver. Otherwise, select 'None'.
Click OK to complete the configuration.
A timer test or 'poll' (also known as the ‘periodic test’ or ‘24 hour’ test) is an affirmation to the monitoring station that the alarm system is capable of sending Contact ID. Most alarm systems send one test per day. The signal is fixed in its format and will be sent with an XYZ (Contact ID event code) of 602 and it will be sent in the (GG) partition or Alarm Zone 00. Only one periodic test can be enabled per account number for accurate reporting of line status (this is a consideration when using multiple Diallers using single client code reporting). It may be necessary to configure periodic tests from different diallers into different account numbers. It will also be reported as a new event and will have a CCC of 000, (e.g. 123418160200000, where 1234 is the account number).
If a test ('poll') is not received when it should have been, action is taken by the monitoring station staff.
Publishing configuration with monitoring enabled pushes the monitoring-related configuration to the controller. This publishing is also the trigger for the controller to carry out dial checks and construct and send messages to the monitoring station.
THE MONITORING STATION WILL RECEIVE ALARMS FROM THE SITE WHENEVER MONITORING IS ENABLED AND A PERMACONN IS CONNECTED OR THE IP ALARM TRANSMITTER IS ENABLED (even if installation and configuration are still underway).
Monitoring Report
Generating the report Once a site is activated, a Monitoring Report will be available to download and send to the monitoring station. The Monitoring Report outlines the XZY Codes, GG Codes, Zone list CCC Codes, and User CCC Codes.
Under Site Actions on the right-hand side of the screen, click Download Monitoring Report.
A warning appears: Only published changes will appear in the report. NOTE: This report contains personal data. Please respect privacy laws.
Click Download.
The Monitoring Report downloads as a CSV file.
Send the file to the monitoring station.
As no users are created for the site yet, the User List CCC Codes will only contain the Key Account Holder. The Monitoring Report can be downloaded at any stage, and you may wish to wait until the Site is set up with more users before downloading and sending the report.
Users' CCC codes If an incident occurs and the monitoring station doesn’t know who the user is by name, they will have a CCC code. In the SMB app, the customer can search for this code.
For the Site Manager to find which user the CCC code is related to:
Log into the SMB customer app.
Select Team from the navigation bar.
In the search field, enter the CCC code.
The user with the related CCC code appears in the search results.
For New Zealand and Australia sites, the Permaconn PM54 is the available alarm transmitter. For North American sites, the Alula BAT-Connect is available.
NZ/AUS: Permaconn PM54 The Permaconn PM54 can also function as an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Permaconn PM54 is powered by the Gallagher SMB Kit and provides connection to the site's WAN or Wi-Fi.
North America: Alula BAT-Connect The Alula BAT-Connect is an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Alula BAT-Connect is powered by the Gallagher SMB Kit and provides connection to the site's WAN, cellular, or Wi-Fi.
If the customer requires third-party monitoring, configure the alarm transmitter.
In the SMB Installer Portal, click the MONITORING tab.
Enter the Account Code received from the monitoring station and click SAVE.
The Alarm Transmitter item displays.
Enable the toggle next to the Alarm Transmitter.
Note: If you are also enabling the IP Alarm Transmitter, select which transmitter is the primary one from the Primary option (next to the 'Account Code' field).
Click on the Alarm Transmitter to open its properties. The Alarm Transmitter lightbox displays.
Enter the transmitter device's serial number or MAC address (this is an optional field).
To enable periodic dialling tests, enable the Periodic Dialling toggle.
To set the frequency of dialling tests, select either Dial daily at or Dial every.
Dial daily at: Select this option to have a periodic dial occur at the same specified time each day. Consider selecting a unique time for each site so the load on monitoring stations is spread throughout the day. If you change the periodic dial time, notify the monitoring station of the new test time. The time will automatically adjust for daylight savings.
Dial every: Select this option if you require more frequent periodic test dials. This means that a test dial will occur at the interval specified, starting at the time that has been specified. Any time can be entered as the start time. Daylight savings corrections will be applied when the Controller's clock is updated.
If required, select the Skip periodic dial following successful alarm dial check box.
With this option selected, the periodic dial test will be skipped if there has been a successful alarm dial since the last periodic dial test. If the periodic dial is skipped, the next time you can expect a periodic dial is at the configured time the next day or after the periodic dial interval, depending on how it is configured.
Click OK to complete the configuration.
For more information about your alarm transmitter, refer to the appropriate installation note:
Permaconn PM54 (NZ/AUS only)
SMB Monitoring Kit (North America only)
About Periodic Dialling
A timer test (also known as the ‘periodic test’ or ‘24 hour’ test) is an affirmation to the monitoring station that the alarm system is capable of sending Contact ID. Most alarm systems send one test per day. The signal is fixed in its format and will be sent with an XYZ (Contact ID event code) of 602 and it will be sent in the (GG) partition or Alarm Zone 00. Only one periodic test can be enabled per account number for accurate reporting of line status (this is a consideration when using multiple Diallers using single client code reporting). It may be necessary to configure periodic tests from different diallers into different account numbers. It will also be reported as a new event and will have a CCC of 000, (e.g. 123418160200000, where 1234 is the account number).
If a test is not received when it should have been, action is taken by the monitoring station staff.
Publishing configuration with monitoring enabled pushes the monitoring-related configuration to the controller. This publishing is also the trigger for the controller to carry out dial checks and construct and send messages to the monitoring station.
THE MONITORING STATION WILL RECEIVE ALARMS FROM THE SITE WHENEVER MONITORING IS ENABLED AND A PERMACONN IS CONNECTED OR THE IP ALARM TRANSMITTER IS ENABLED (even if installation and configuration are still underway).
Monitoring Report
Generating the report Once a site is activated, a Monitoring Report will be available to download and send to the monitoring station. The Monitoring Report outlines the XZY Codes, GG Codes, Zone list CCC Codes, and User CCC Codes.
Under Site Actions on the right-hand side of the screen, click Download Monitoring Report.
A warning appears: Only published changes will appear in the report. NOTE: This report contains personal data. Please respect privacy laws.
Click Download.
The Monitoring Report downloads as a CSV file.
Send the file to the monitoring station.
As no users are created for the site yet, the User List CCC Codes will only contain the Key Account Holder. The Monitoring Report can be downloaded at any stage, and you may wish to wait until the Site is set up with more users before downloading and sending the report.
Users' CCC codes If an incident occurs and the monitoring station doesn’t know who the user is by name, they will have a CCC code. In the SMB app, the customer can search for this code.
For the Site Manager to find which user the CCC code is related to:
Log into the SMB customer app.
Select Team from the navigation bar.
In the search field, enter the CCC code.
The user with the related CCC code appears in the search results.
In situations where organisations or Site Managers are apprehensive about managing their own alarms and don’t want to take on this responsibility outside of work hours, Third-Party Monitoring can be configured for the site.
Alarm messages are sent from the Controller at the site to the nominated monitoring station in a standard format in accordance with a set of rules. Monitoring stations will have software that interprets messages received. The software will send notifications to nominated personnel at the site or display details on a workstation at the station in a form that is easy for an operator to action.
The monitoring company can notify relevant parties in accordance with an agreed action plan. This could be people from your site, your security technician, or a guarding company who will send someone to check your premises.
If Third-Party Monitoring is enabled, the Site Manager will not receive alarm incident notifications.
Actions taken by the monitoring station will depend on the response plan defined by the customer.
Possible actions are:
do nothing
monitoring station software sends an automated notification to nominated people at the site
telephone nominated personnel at the site one by one in an escalation sequence
call a guard out
contact police.
The required response by the monitoring station may depend on:
the day of the week and/or time of day
what happened
the value of property at the site
the level of trust the business owner has in the people who have access to the site
how much the business owner is prepared to pay monitoring for the service
whether the system is police graded and/or the alarm has been verified. The rules and requirements for calling the police vary by country and jurisdiction. If required, verification could be by someone at the premises, video verification, or following dual activation.
Messages are sent from the SMB system to the monitoring station in Contact ID format. This is a standard protocol used worldwide to communicate what is happening on a site to a monitoring station.
The message format is: ACCT MT Q XYZ GG CCC
Code mappings and the rules for formatting and determining which messages to send are fixed. The need or ability for a Technician to configure anything has been minimised.