> 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-analog-dialler.md).

# Analog dialler

Connect and configure analog diallers, cellular diallers, PABX prefixes, and jumper settings.

The Analog Dialler uses an RS232 (serial) port to connect to a PSTN dialler that sends Ademco Contact ID over a phone line. There are **two hardware versions**:

| Part        | Firmware compatibility                            |
| ----------- | ------------------------------------------------- |
| **C200621** | Controllers running **v8.10 firmware or earlier** |
| **C200620** | Controllers running **v8.20 firmware or later**   |

If a site upgrades from v8.10 or earlier to v8.20 or higher, the **C200621 will continue to work** on the later versions of Command Centre.

***

### C200620 connection

The C200620 connects to the RS232 serial port of a 3000 or 6000 controller and to an analog telephone / POTS (Plain Old Telephone Service) line.

* Connect the **building incoming telephone line** to the **P3 "Line in"** connector.
* Connect **all other devices** to the **P2 "Line out"** connector.

This way, when the dialler activates it disconnects the other devices and is the only device left on the line. This is intended: you do not want other devices on the phone line interfering with the alarm system reaching the monitoring station. The dialler uses a relay to disconnect the output from the phone line.

![C200620 analog dialler connection](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b369d2fb9a213d30b76ff2d61a8d7ad819701c05%2FSECHUB-CCS-ALARM-analog-01-c200620-connection.png?alt=media)

![Analog dialler connection detail](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-402be38ee5b50f534938d7b8fe8b5e5d9aa1a767%2FSECHUB-CCS-ALARM-analog-02-connection-detail.png?alt=media)

> This device, like all analog diallers, has been known to have issues connecting to **digital telephone lines** and **some PABXs**.

***

### Connect a cellular dialler

A cellular unit is usually supplied by the monitoring centre, often pre-configured with an account code (but not always). Cellular units vary, so getting one working may take trial and error.

* Some do **not** have phone-line dial-tone emulation.
* Some cellular backup devices require the Analog Dialler to be connected.

***

### Configure phone lines with no dial tone

If the dialler must connect and dial **without waiting for a dial tone**, add a Custom Initialisation String of **`atX0`** or **`atX1`** in the dialler's **Dial Protocol** tab.

***

### Configure a PABX prefix number

In some countries this is referred to as the **DNIS** number. It is the entry you put into the Analog Dialler to get through a PABX to an outside line.

![PABX prefix / DNIS field](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-22b7c51eecd009b1b3c4c0be964894e3185b06d6%2FSECHUB-CCS-ALARM-analog-03-pabx-prefix-dnis.png?alt=media)

***

### "No response from modem"

If you get a "No response from modem" message, especially after installing a new analog dialler, the plugin sub-board jumper is the usual cause. There are two versions of the sub-board, set at assembly but occasionally missed.

**Check P7 on the dialler main board:**

| Sub-board part number            | P7 jumper position |
| -------------------------------- | ------------------ |
| `MT5692SMI-X-L-92.R1` or `SM H2` | **3V3**            |
| `MT5692SMI-92.R1`                | **5V**             |

![P7 jumper on 3V3](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-84eb13d8bf255729fedf32fad071c30c19a3355e%2FSECHUB-CCS-ALARM-analog-04-p7-jumper-3v3.png?alt=media)

![MT5692SMI-X-L-92.R1 sub-board](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d281400cf01e5f07fe03f43041e4cce9667823df%2FSECHUB-CCS-ALARM-analog-05-subboard-mt5692-x-l.png?alt=media)

![MT5692SMI-92.R1 sub-board (5V variant)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1d13c7756a26b185636e30b2727083fa3031d6a7%2FSECHUB-CCS-ALARM-analog-06-subboard-mt5692-5v.png?alt=media)

![SM H2 sub-board](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d1ac4db530b46bc75d67a37c3944c75b61edcd41%2FSECHUB-CCS-ALARM-analog-07-subboard-sm-h2.png?alt=media)

**Check P6 on the dialler main board:** the main board has an option for a P6 jumper. If a jumper is present, **remove it**. P6 is only used during the manufacturing process and should not be present in the field.

![P6 jumper location](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ddd1ee2a31503ab6f2aabfdcbaacb296d014e2fb%2FSECHUB-CCS-ALARM-analog-08-p6-jumper.jpg?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-analog-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.