> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/ip-alarms-receiver-software.md).

# IP Alarms Receiver Software

### Introduction

The IP Alarms Receiver Software runs on a Windows PC in a remote alarm monitoring centre. The IP Alarms Receiver Software performs the following tasks:

* Listens on a socket for incoming socket connections.
* Accepts a connection from a Gallagher Controller.
* Reads data from an open socket connection to a Gallagher Controller.
* Decrypts and decodes the received message.
* Forwards the message to the alarm monitoring system (via the serial port).
* Waits for a reply from the alarm monitoring system acknowledging receipt of the message.
* Sends an acknowledge message to the Gallagher Controller if the message was successfully sent to the alarm monitoring system and acknowledged by the alarm monitoring system.
* Closes the socket, if not already closed by the Gallagher Controller
* Regularly checks to see if any remote station has not been heard from for too long and generates heartbeat alarms as required.

For further detail on installing and using the IP Alarms Receiver Software, refer to the current **IP Alarms Receiver Software Release Note** located in the `'Utilities\IP Alarm Receiver'` directory of the Gallagher Command Centre installation files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/ip-alarms-receiver-software.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
