> 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/products/cc-software/configure/alarm-transmission/alarm-transmission-how-ip-monitoring-c.md). # IP monitoring Understand DC-09 and CSV alarm monitoring connections for Gallagher and third-party receivers. ### DC-09 with Gallagher IP Receiver software The flow when the monitoring centre runs the Gallagher IP Alarm Receiver: 1. An alarm is generated on an alarm zone on any controller (for example, Controller 3). 2. The message is sent to the controller hosting the IP transmitter (for example, Controller 1). 3. That controller uses its gateway information to route the traffic out through the site's router/firewall to the monitoring station's IP address. 4. The **Gallagher IP Alarm Receiver** at the monitoring centre decodes the message (and decrypts it if encryption is enabled), then sends it via RS232 to the monitoring server. ![DC-09 connection with the Gallagher IP receiver](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5adcf2fef19c9bf8c3eab03684873f754a9f3726%2FSECHUB-CCS-ALARM-ipmon-01-dc09-gallagher-receiver.png?alt=media) ![Relationship between Command Centre components and the DC-09 packet](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6fb85ea3cb4856df0ec866f1fddc16985e256a35%2FSECHUB-CCS-ALARM-ipmon-02-dc09-packet-relationship.png?alt=media) *** ### DC-09 without Gallagher IP Receiver software (direct to a third party) > ⚠️ **Supported only from v8.70.2078 (MR3), v8.80.1025 (MR1) and v8.90+.** To connect the DC-09 protocol directly to a monitoring facility that has IP DC-09 receiving capability: 1. In Configuration Client under **File / Server Properties** and/or the **Alarm Zone**, go to **Alarm Transmission** and add an **Account Prefix** other than 0s. * The monitoring station should supply the Account Prefix number. (The Account Prefix is an extension to the monitoring facility's account code.) * If they do not supply one, populate the field with **001** and advise the monitoring station of the value you applied. Any HEX ASCII characters other than 0 will work, but the monitoring station must know what it is. ![Account prefix field](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8903c9766a69aebb51ae05e7aa2f5e733602e6e7%2FSECHUB-CCS-ALARM-ipmon-03-account-prefix.jpg?alt=media) 2. On the IP Transmitter(s) under **Alarm Receivers**, the Transmitter ID can be set to anything. Adding the Account Prefix overrides this setting. ![IP transmitter alarm receivers](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e33e48cd533d165e37ad221295a483071eb17ef3%2FSECHUB-CCS-ALARM-ipmon-04-transmitter-id.jpg?alt=media) 3. Under the **Protocol** tab, **Encryption must be blank / unchecked**. ![Protocol tab with encryption unchecked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2006f1e817f661b2ede089593d4e998aa8846308%2FSECHUB-CCS-ALARM-ipmon-05-protocol-encryption.jpg?alt=media) This allows an IP Transmitter to connect to a third-party alarm receiver. ![Relationship between Command Centre components and the direct DC-09 packet](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e78b8ced6d35ee2102b65c434a2180fc3e6ad7fa%2FSECHUB-CCS-ALARM-ipmon-06-dc09-packet-direct.png?alt=media) > **Note:** Prefix = Line Card in DC-09. Many USA alarm monitoring companies call this **DNIS**. > **Note:** Encryption for this direct configuration is planned to be released in the future. > **Note:** After setting the prefix to a value other than 0, the Gallagher IP Receiver software can still be used, but not configured as before. The **ACCT** is sent in place of the Transmitter ID, so the software must be reconfigured to accept the ACCT value in the Transmitter ID field. A 4-character ACCT is prepended with two zeros, so an ACCT of 1235 would be entered as **001235** in the Gallagher IP Alarm Receiver configuration. *** ### CSV connection The CSV protocol does **not** require the monitoring station to have the Gallagher IP Monitoring software installed. The monitoring station needs to be able to accept CSV connections, which is often an add-on to the monitoring suite they use. ![CSV connection architecture](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d4adff99c044b5ef3e2a83e1119d8cad905b3d26%2FSECHUB-CCS-ALARM-ipmon-07-csv-receiver.png?alt=media) --- # 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/products/cc-software/configure/alarm-transmission/alarm-transmission-how-ip-monitoring-c.md?ask=&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.