# IP Alarms The IP Alarm Transmitter requires no additional hardware; only the Controller is required. {% hint style="danger" %} **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. {% endhint %} ### Configuring an IP Alarm Transmitter 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. 1. In the [SMB Installer Portal](https://app.halo.gallagher.com/installer/), click the **MONITORING** tab. 2. Enter the **Account Code** received from the monitoring station and click **SAVE**. The IP Alarm Transmitter item displays. 3. 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). 4. Click on the IP Alarm Transmitter to open its properties. The IP Alarm Transmitter lightbox displays. 5. 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. * **Note**: If using DC-09 SIA an Account Prefix is required. If the Account Prefix has a letter greater than F, do not enter the letter and only enter the numbers. 6. 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. 7. 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. **Note:** The Username and Password must not contain the following characters: < > & ‘ “ , 8. 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. 9. 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. 10. 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. 11. To enable [polling](#about-polling), select the time under the Polling field and enter how often a heartbeat will be sent to poll the receiver. Otherwise, select 'None'. 12. Click **OK** to complete the configuration. {% hint style="warning" %} If third-party monitoring is enabled, a GG Code field will appear. The GG code that is reported to the monitoring station can be configured. If the GG code is set to 00, the state change of the Area **will not be sent to the monitoring station.** {% endhint %} {% embed url="" %} ### **About Polling** 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 with an alarm transmitter 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. {% hint style="danger" %} 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). {% endhint %} **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. 1. 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.* 2. Click **Download**. The Monitoring Report downloads as a CSV file. 3. 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: 1. Log into the SMB customer app. 2. Select **Team** from the navigation bar. 3. In the search field, enter the CCC code. The user with the related CCC code appears in the search results. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.security.gallagher.com/smb/site-configuration/configure-monitoring/ip-alarms.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.