> 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/understanding-contact-id.md).

# Understanding Contact ID

### Contact ID

Contact ID is a DTMF (Dual Tone Multi-Frequency) protocol for transmitting event/alarm occurrences to remote alarm monitoring stations over telecommunications.

Contact ID requires a suitable modem device and uses an analog phone line. It requires exclusive use of the phone line when it is transmitting data.

**Note:**

Contact ID is not currently supported on digital phone systems or over a GSM network.

The form of the message sent to the alarm monitoring station is as follows:

**ACCT MT QXYZ GG CCC**

<table data-header-hidden><thead><tr><th width="140.11114501953125"></th><th></th></tr></thead><tbody><tr><td><strong>ACCT</strong></td><td>Four digit Account number (0-9, B-F)</td></tr><tr><td><strong>MT</strong></td><td>Two digit Message Type used to identify the Contact ID message to the receiver.</td></tr><tr><td><strong>Q</strong></td><td>Event Qualifier which gives specific event information as follows:<br>1 = New Event or Opening<br>3 = New Restore or Closing<br>6 = Previously reported condition still present</td></tr><tr><td><strong>XYZ</strong></td><td>Event Code (3 Hex digits 0-9, B-F), which is mapped to an existing Event group in Command Centre.</td></tr><tr><td><strong>GG</strong></td><td>Group or Partition number (2 Hex digits 0-9, B-F).<br>00 can be used to indicate that no specific group or partition information applies</td></tr><tr><td><strong>CCC</strong></td><td>Zone number (Event reports) or User number (Open/Close reports).<br>3 Hex digits 0-9, B-F.<br>000 can be used to indicate that no specific zone or user information applies.</td></tr></tbody></table>

For every alarm that is sent off site using Contact ID, a restoral event will also be sent to the monitoring station to indicate that the alarm condition has been attended to. See [Events with Restorals](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/events-with-restorals.md) for a list.

**IMPORTANT:**

There are a number of events that are exclusive to Command Centre and play no part in the Controller based Contact ID, and therefore will never provide Contact ID alarms.

Sites can choose to send multiple transmissions of the same alarm occurrence, (i.e. alarm floods) via Contact ID, or to send just one and then wait for an Alarm Zone Set/Unset before sending another. The multi-breaks option (see [Alarm Flooding](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-flooding.md) for details) determines how repeated alarm messages will be sent via Contact ID to a remote alarm monitoring company.

### IP Alarm Monitoring

IP Alarm Monitoring uses another means of transmitting the alarms between the Controller and alarm receiving centre, (i.e. an IP Alarm Transmitter). The IP Alarm Transmitter uses TCP/IP to transmit messages to an alarm monitoring centre.

Messages are transmitted using the Offsite Alarm Transmission Protocol. This protocol uses the Contact ID ANSI\SIA DC-09 message format. Encryption can be enabled or disabled.

Messages are received by the IP Alarms Receiver Software. The IP Alarms Receiver Software forwards the messages via a serial port, using the Ademco 685 protocol, to the alarm monitoring system in the alarm monitoring centre.

**Notes:**

* While you can have digital cameras and Contact ID on the same Controller, the transmission error rates increase if you are doing rapid image triggering. Therefore, if you require rapid image triggering on a Controller, you should not have Contact ID on the same Controller.
* An online help file listing all the event/alarm messages in the system can be accessed via the **Help** menu bar in Command Centre, and will provide you with explanations of what each of the Contact ID messages mean.
* A Contact ID Assignment Report is available, which provides a list of all the possible Contact ID strings that can be sent from a Dialler to a remote monitoring station. See [Contact ID Assignment Report](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/contact-id-assignment-report.md) for further detail.
* The "Edit Site" and "View Site" operator privileges are required for working with the Contact ID functionality.
* When using the Find Tool to locate items, those with Alarm Dialling configuration will have additional search criteria available on the **Alarm Transmission** tab, determined by what you select in the "Look in" field on the **General** tab, as follows:

  <table><thead><tr><th width="252.22222900390625">Selection in the "Look in" field on the General tab</th><th>Field that appears on the Alarm Transmission tab</th></tr></thead><tbody><tr><td>All items</td><td><strong>User or Zone Identifier (CCC)</strong> field *</td></tr><tr><td>Cardholder</td><td><strong>User Identifier (CCC)</strong> field *</td></tr><tr><td>any hardware item or site item (excluding Alarm Zone)</td><td><strong>Zone Identifier (CCC)</strong> field *</td></tr><tr><td>Alarm Zone</td><td><strong>Group Identifier (GG)</strong> field.<br>If a GG code is entered in this field, the search results will display the Alarm Zones that have been assigned that GG. If the GG value is left blank, then it will not be used as a search criterion.</td></tr></tbody></table>

  \* If a CCC code is entered in this field, the search results will display the cardholders or items that have been assigned that CCC. If the CCC value is left blank, then it will not be used as a search criterion.


---

# 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/understanding-contact-id.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.
