> 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/configuring-an-alarm-transmitter-dialler.md).

# Configuring an Alarm Transmitter/Dialler

### Introduction

This procedure enables you to create an Alarm Transmitter/Dialler in Gallagher Command Centre.

***

### Before you begin

Before you begin this procedure ensure you have:

* performed [Setting the Country Code](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/setting-the-country-code.md).
* created an output(s) for the Alarm Transmitter/Dialler (using the [Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md) procedure), if you want to receive visual or audible acknowledgements when Alarm Zone armed messages are received by the monitoring company.

  **Notes:**

  * More than one output can be configured for the Alarm Transmitter/Dialler, (e.g. an audio output and a visual output).
  * Ensure you set the output to pulse when activated.

***

### Configuration

To configure an Alarm Transmitter/Dialler, perform the following procedures in Gallagher Configuration Client:

1. In Command Centre, click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select either:

   **New\...RS232 Devices** > **Alarm Dialler**, or

   **New\...IP Alarm Transmitter**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure an Alarm Transmitter/Dialler:

<details>

<summary>Alarm Transmission tab</summary>

1. Click the **Alarm Transmission** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-397c442a78a2d40526ec74d4aea262c34d76c70a%2Fcid_alarmdiallingtab.png?alt=media)
2. Enter the zone identifier for Contact ID.

   **Notes:**

   * This field will accept 3 Hex digits 0-9, B-F.
   * The default of 000 can be left if you do not wish to indicate a specific zone or user information.

</details>

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-747cb9955044899983c0bb9d76541fe4d4f16c44%2Fcid_connectionstab.png?alt=media)

   This tab shows the Controller that this Alarm Transmitter/Dialler is connected to. This has to be configured from the **Alarm Transmission** tab of the Controller properties. Refer to [Assigning the Alarm Transmitter/Dialler to a Controller](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/assigning-the-alarm-transmitter-dialler-to-a-controller.md) for the procedure.

</details>

<details>

<summary>Backup Transmitters tab</summary>

1. Click the **Backup Transmitters** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8eaf4c00993449924064aaf1c61f925a56b9e67e%2Fcid_dialbackupstab.png?alt=media)

   A Backup Transmitter/Dialler can take over from an Alarm Transmitter/Dialler that is having trouble communicating due to any number of problems. Each Alarm Transmitter/Dialler can have up to two backup transmitters/diallers.

   **Notes:**

   * Backup Transmitters/Diallers can only be nominated for LAN connected Controllers.
   * A Transmitter/Dialler on a Dial-up Controller can not act as a backup for a LAN based Controller.
2. Click the drop-down menu box(es) and select the appropriate Alarm Transmitter/Dialler to be used as a backup transmitter/dialler.

</details>

7. Are you configuring an Alarm Dialler or an IP Alarm Transmitter?

   If an **Alarm Dialler**, go to Step 8.

   If an **IP Alarm Transmitter**, go to Step 9.
8. Click each tab in turn to continue configuring an Alarm Dialler, and then go to Step 10:

<details>

<summary>Dial Numbers tab</summary>

1. Click the **Dial Numbers** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-954579deec256fefd6cf91421e9b310df2c70225%2Fcid_dialnumberstab.png?alt=media)
2. Tick the checkbox under **Dialling Prefix** and enter the number required to dial out of the internal phone system.

   A maximum of eight digits can be entered.

   Each Dialler can be configured to dial up to three numbers in an attempt to communicate with an alarm monitoring station, as follows:

   <table><thead><tr><th width="156">Field</th><th>Description</th></tr></thead><tbody><tr><td>Phone Number 1</td><td>This is the first phone number that the Dialler will call when a Contact ID message needs to be sent.<br>(Maximum 32 digits)</td></tr><tr><td>Phone Number 2</td><td>This is the second phone number that the Dialler will call once all attempts on Phone Number 1 have expired.<br>(Maximum 32 digits)</td></tr><tr><td>Phone Number 3</td><td>This is the third phone number that the Dialler will call once all attempts on Phone Number 2 have expired.<br>(Maximum 32 digits)</td></tr><tr><td>Description</td><td>The Description fields for the phone numbers allow a text description of each number to be entered so the numbers can be easily recognised.<br>These descriptions will also appear in an audit trail rather than disclosing the actual called numbers.</td></tr></tbody></table>
3. Complete the **Redial Attempts** as required:

   <table><thead><tr><th width="156">Field</th><th>Description</th></tr></thead><tbody><tr><td>Maximum</td><td><p>(Range is 1-99, and default is 10 attempts)<br>This is the number of redials that the Dialler will attempt before moving onto the next phone number. If this number is set to 10, then a total of 11 calls will be made to the first phone number, (i.e. the first attempt and then 10 more attempts).<br>Once the redial attempts have expired then the Dialler will move to the next number on the list and the same rules will apply to that number, being that the first attempt will be followed by the number of redial attempts. Once all redial attempts have expired an alarm can be generated by an Action Plan. Events are held for 15 minutes, then the sequence starts again.<br>If you assigned a Backup Dialler(s) on the <strong>Backup Transmitters</strong> tab, then once all attempts have been made with this Dialler, the messages will be passed to the backup Dialler(s) for transmissions.<br><br><strong>Notes:</strong></p><ul><li>Each Dialler supports 255 events being held in the buffer, so if there are more than 255 events to be sent via Contact ID, the oldest events will be discarded. A message is generated however in the Event Log to advise the Date, Time and details of the discarded event(s) to provide a full audit trail.</li><li>A 15 minute wait period is started after all attempts at connecting to the security company's Contact ID receiver have failed. During this period, if further Contact ID alarms occur, no Contact ID events appear in Command Centres event viewer window and no further dialler activity is initiated.</li></ul><p>Take this functionality into account when you have no backup dialler, assign only one telephone number, and set the Redial Attempts Maximum to 0. If the dialler tries to report a Contact ID event and encounters say a busy line, subsequent Contact ID transmission attempts will be inhibited for 15 minutes.</p></td></tr><tr><td>Time Between Redials</td><td>This is the time value between calls that are made to the designated phone numbers.<br><br><strong>Note:</strong><br>This should be set according to your local telecommunications company specifications.<br>(Range is 1 second to 1 hour. The default is 30 seconds)</td></tr></tbody></table>

</details>

<details>

<summary>Dial Protocol tab</summary>

1. Click the **Dial Protocol** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-134410076e54955894d85c1f50cb707a9d76cb1c%2Fcid_dialprotocoltab.png?alt=media)
2. Complete the fields on this tab as required.

   <table><thead><tr><th width="158">Field</th><th>Description</th></tr></thead><tbody><tr><td>Message Type (MT):<br></td><td>This two digit sequence is used to identify the Contact ID message to the receiver. It may be transmitted as either 18 (which is the default and the preferred option), or 98 (optional).<br><br><strong>Note:</strong> New receivers will accept either an 18 or a 98, however some older receivers may not accept a 98.</td></tr><tr><td>Maximum wait for handshake (seconds):</td><td>This value determines how long the modem will wait for a connection and "handshake" from the alarm monitoring receiver. If no valid handshake is detected by the end of the wait time, (this could happen because of busy receiver telephone lines, or there was no answer at the called number), then an Alarm Dialling failure alarm can be generated and the system will retry again after the time between redials has elapsed.<br>(Range is 1 to 255 seconds. The default is 30 seconds.)</td></tr><tr><td>Maximum transmit attempts:</td><td>The number of transmit attempts to send the same Contact ID string to the receiver during the same call, before hanging up and redialling. The attempts counter is reset each time a valid kiss-off signal is received.<br>(Range is 1-4 attempts. Default is 4 attempts.)</td></tr><tr><td>Custom Initialisation String:</td><td><p>It is unlikely your site will need to enter an intialisation string, therefore it is important you leave this field BLANK. However there are cases where you may need to add an initialisation string, as follows:</p><ul><li>If your Contact ID receiver (normally located at the alarm monitoring company) happens to be on the same PABX as the Dialler, or</li><li>If you are experiencing problems with reliably receiving Contact ID messages at the receiver.</li></ul><p>In these situations, contact Gallagher Security Management Systems (Tech Support) for further instructions on entering an initialisation string.</p></td></tr></tbody></table>

</details>

<details>

<summary>Dial Schedule tab</summary>

1. Click the **Dial Schedule** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6f8d99d6a221ec070de86197194a1f08fd57ffbc%2Fcid_dialscheduletab.png?alt=media)
2. If you want to check for dial tone on the line on a regular basis, tick the **Periodic Dial Tone Check** checkbox and select the time from the drop-down list for the frequency of the check.

   **Notes:**

   * The checks can be as frequent as 1 minute or as intermittent as 24 hours. (The default is 1 hour)
   * If an Alarm Dialler fails a “Periodic Dial Tone Check”, an alarm will be generated.
   * The line is not broken during these dial tone checks, and an alarm is raised if there is no dial tone on the line when it is checked. You can use an Action Plan to annunciate these alarms to Command Centre, and optionally send them out from another Dialler on the system.
   * It is recommended that Diallers are connected to a dedicated phone line, or at least a line that is used infrequently by other devices on that line. In the case of a shared line, the Contact ID Dialler must be the first device that can break or use that line.
   * If there is more than one Alarm Dialler on your system, unique periodic tests must be sent from each Dialler. The periodic dial test works as follows:
     * **ACCT:** If an Alarm Zone is assigned to the Dialler **and** the Alarm Zone overrides the site ACCT code, **then** the periodic test dial will use the Alarm Zone's ACCT code, **otherwise** the periodic test dial will use the site's ACCT code.
     * **GG:** If an Alarm Zone is assigned to the Dialler, **then** the periodic test dial will use the Alarm Zone's GG code, **otherwise** the periodic test dial will have a GG code of "00".
     * **CCC:** The periodic test dial will use the zone identifier (CCC) that has been assigned to the Alarm Dialler.
3. The timer test can also be configured on this tab by ticking the **Periodic Dialling** checkbox and then setting the frequency of the tests by clicking the appropriate radio button.

   <table><thead><tr><th width="156">Option</th><th>Description</th></tr></thead><tbody><tr><td>Dial daily at:</td><td>Selecting this option will mean that a Periodic dial will occur at the same time each day. Always set it for a time of the hour or half hour to avoid overloading the monitoring station at these times. If you change the periodic dial time, notify the monitoring station of the new test time. The time will automatically adjust for daylight savings.<br><br><strong>Note:</strong><br>Remember that this is based on the time at the Controller, not at Command Centre.</td></tr><tr><td>Dial every:</td><td>Select this option if you require more frequent periodic test dials. This means that a periodic dial will occur at the interval specified, starting at the time that has been specified.<br>Time intervals allowed = 30 minutes, 1, 2, 3, 4, 6, 8 or 12 hours.<br>Anytime can be entered in the start time. Daylight savings corrections will be applied when the Controllers clock is updated.</td></tr></tbody></table>

   The timer test (also known as the ‘periodic test’ or ‘24 hour’ test), is an indication to the monitoring station that the alarm system is capable of sending Contact ID. Most systems send one test per day. The signal is fixed in its format and will be sent with a 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 your account number).

   If a test is not received action is taken by the monitoring station staff, which may include phoning the site to check that the phones are working.
4. Tick the **Skip periodic dial following successful alarm dial** checkbox if required.

   By enabling this feature, the periodic dial will get skipped when 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 after the periodic dial interval (or at the same time of day tomorrow), depending on how it is configured.

</details>

9. Click each tab in turn to continue configuring an IP Alarm Transmitter, and then go to Step 10:

<details>

<summary>Protocol tab</summary>

1. Click the **Protocol** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2dd63b73199f78fe1e7c6076c6ca14aa90914ba9%2Fipalarmtransmitter_protocoltab.png?alt=media)
2. Select the appropriate **Protocol** from the drop-down list, i.e. either DC-09 (default) or CSV.

   **Notes:**

   * The CSV protocol extends the existing 4-digit Account Codes to 6-digit Account Codes, which are supported on Controller 6000s.
   * The protocol cannot be changed once the item has been saved.
3. Which protocol did you select?

   <table><thead><tr><th width="84">If...</th><th>then...</th></tr></thead><tbody><tr><td>DC-09,</td><td><p>the <strong>Enable encryption</strong> section displays.<br>If you want to use an encryption key, check the <strong>Enable Encryption</strong> checkbox and populate the <strong>Encryption Key</strong> field with a 64 character hexadecimal string.<br><br><strong>Notes:</strong></p><ul><li>This can be done by either manually typing in a string, or by clicking the <strong>Generate</strong> button which will automatically populate the field with a random hexadecimal string and enable the <strong>Apply</strong> button. If the <strong>Apply</strong> button is clicked now, the 64 characters are converted to 64 X's.</li><li>When an encryption key is entered, this is sent across DCOM to the server. As it would be possible for someone on the network to capture the packet as it passes along the network, it is recommended that this only be done on the workstation that runs directly on the server PC.</li><li>Keys exported by earlier versions than vEL8.00 of Command Centre cannot be imported.</li></ul></td></tr><tr><td>CSV,</td><td>the <strong>Enable Authentication</strong> section displays.<br>If you want to enable authentication, check the <strong>Enable Authentication</strong> checkbox and enter the <strong>Username</strong> and <strong>Password</strong> that will be used by the third party to authenticate the data received.</td></tr></tbody></table>

</details>

<details>

<summary>Alarm Receivers tab</summary>

1. Click the **Alarm Receivers** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7102854312c512cd5c4e3df98f15f9b67f2af454%2Fipalarmtransmitter_3.png?alt=media)
2. Tick the checkbox beside the **Receiver** you wish to use.

   Each IP Alarm Transmitter can be configured to transmit to three receivers in an attempt to communicate with an alarm monitoring centre, as follows:

   <table><thead><tr><th width="139">Field</th><th>Description</th></tr></thead><tbody><tr><td>Receiver 1</td><td>This is the first receiver that the IP Alarm Transmitter will transmit to when a message needs to be sent.</td></tr><tr><td>Receiver 2</td><td>This is the second receiver that the IP Alarm Transmitter will transmit to once all attempts on the Primary Receiver have expired.</td></tr><tr><td>Receiver 3</td><td>This is the third receiver that the IP Alarm Transmitter will transmit to once all attempts on Receiver 2 have expired.</td></tr></tbody></table>
3. Complete the **Receiver** fields as required:

   <table><thead><tr><th width="139">Field</th><th>Description</th></tr></thead><tbody><tr><td>IP</td><td>This is the IP address of the receiver. This will be provided by the alarm monitoring centre.</td></tr><tr><td>Port</td><td>This is the port number of the receiver. This will be provided by the alarm monitoring centre.</td></tr><tr><td>Enable polling</td><td>This is the heartbeat time used to poll the receiver.</td></tr><tr><td>Transmitter ID</td><td>If required, you can configure a transmitter ID, so that the receiver can monitor and identify the channels separately.<br>This field is pre-populated with a unique suggestion, formed from the site wide ACCT code plus a unique 2 digit identifier.<br><br><strong>Note:</strong> If you selected CSV protocol on the <strong>Protocol</strong> tab, the <strong>Transmitter ID</strong> fields will not appear, as they are redundant when configuring Alarm Receivers with CSV protocoI.</td></tr><tr><td>Transport</td><td>The available transport options are WAN/LAN or Wireless. For the Wireless transport option, the IP Address/Port combination will need to be allowed through any firewall that is configured between Command Centre and the Alarm Receiver via the cellular provider.<br><br><strong>Note:</strong> If you use the Wireless option and need to update the Intercel Sam3G+ module to use a different connection profile than the 3 preloaded profiles, refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/configuring-an-alarm-transmitter-dialler/changing-the-connection-profile-on-the-intercel-sam3g-module.md">Changing the Connection profile on the Intercel Sam3G+ module</a> for the procedure.</td></tr></tbody></table>

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-42d99e7fd078884ada32f1b08ff3f6b8b4fc6d8f%2Fipalarmtransmitter_5.png?alt=media)
2. Enter the number of attempts before trying the next receiver.

   This is the number of retries that the IP Alarm Transmitter will attempt before moving onto the next IP address. If this number is set to 10, then a total of 11 transmissions will be made to the first IP address, (i.e. the first attempt and then 10 more attempts).

   Once the retry attempts have expired then the IP Alarm Transmitter will move to the next IP address on the list and the same rules will apply to that IP address, being that the first attempt will be followed by the number of retry attempts. Once all retry attempts have expired an alarm can be generated by an Action Plan. Events are held for 15 minutes, and then the sequence starts again.

   If you assigned a backup transmitter(s) on the **Backup Transmitters** tab, then once all attempts have been made with this IP Alarm Transmitter, the messages will be passed to the backup transmitter(s) for transmissions.

   **Notes:**

   * Each IP Alarm Transmitter supports 255 events being held in the buffer, so if there are more than 255 events to be sent via Contact ID, the oldest events will be discarded. A message is generated however in the Event Log to advise the Date, Time and details of the discarded event(s) to provide a full audit trail.
   * A 15 minute wait period is started after all attempts at connecting to the offsite alarm receiver have failed. During this period, if further Contact ID alarms occur, no Contact ID events appear in Gallagher Command Centre's event viewer window and no further transmission activity is initiated.

     Take this functionality into account when you have no backup transmitter, assign only one IP address, and set the Retry Attempts Maximum to 0. If the IP Alarm Transmitter tries to report a Contact ID event and cannot, subsequent Contact ID transmission attempts will be inhibited for 15 minutes.
3. If you selected the Wireless transport option on the previous tab, (i.e. the **Alarm Receivers** tab), you can select a Wireless **Frequency Band** incase the reception on one band is very low, but the modem will not select a higher strength band. The options are 'Automatic' or '3G only'.

   **Note:** When the Frequency Band is changed, the band may not change until the next update (approximately 2 minutes).

</details>

10. Did you create an output for the Alarm Transmitter/Dialler so you will receive visual or audible acknowledgements when Alarm Zone armed messages are received by the monitoring company?

    If **yes**, then click the **Outputs** tab.

    If **no**, go to Step 12.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d02d381259067c1d6669589636279ea36e1e037c%2Fcid_outputstab.png?alt=media)
11. Open the **Hardware** List Window, and drag and drop the Alarm Transmitter/Dialler output(s) previously created into the grid.

    **Note:** If backup Alarm Transmitters/Diallers are used they must have their own outputs configured.
12. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Alarm Transmitter/Dialler.

    For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
13. Click the **Icons** tab if you want to change the Icon Set for this Alarm Transmitter/Dialler.

    For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
14. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Alarm Transmitter/Dialler.

    For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
15. Click the **Notes** tab if you want to add a note(s) about this Alarm Transmitter/Dialler.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
16. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

An Alarm Transmitter/Dialler has been created in Command Centre.

***

### Next

[Assigning the Alarm Transmitter/Dialler to a Controller](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/assigning-the-alarm-transmitter-dialler-to-a-controller.md)

### In This Section

* [Changing the Connection profile on the Intercel Sam3G+ module](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring/configuring-an-alarm-transmitter-dialler/changing-the-connection-profile-on-the-intercel-sam3g-module.md)


---

# 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/configuring-an-alarm-transmitter-dialler.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.
