> 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/command-centre-client/using-command-centre/licensable-features/jacques-intercom-feature/monitoring-an-intercom.md).

# Monitoring an Intercom

An operator can monitor an intercom from:

* a Jacques Intercom item configured in Command Centre (located on a Site Plan tile or Status tile), or
* a Jacques Intercom Viewer.

When monitoring an intercom, audio is transmitted from the intercom to the workstation intercom, but there is no audio or visual output at the intercom. There is no indication at the intercom that it is being monitored.

**Notes:**

* Some intercoms cannot be monitored, e.g. video endpoint units and master units. Gallagher has tested monitoring the VSL-351 units.
* If your Jacques Intercom Server is not configured to allow an intercom to be Call connected and Monitoring connected simultaneously, or intercoms are configured to only ring one parent master intercom (workstation), operators may experience the scenario where a call cannot be processed at the workstation that receives the call because another workstation (that does not receive the call) is monitoring that intercom. Refer to the Jacques Support Portal to configure your Jacques Intercom Server so that intercoms can be Call connected and Monitoring connected simultaneously (*"Digital audio recorder (DAR) reference manual"*), or ring all master intercoms (*"Set up bridge calling in the intercom system database"*).
* The **Monitor** button remains enabled when the Jacques Intercom System is offline or the workstation Jacques Configuration is incorrect.

1. Open the Jacques Intercom Viewer.
2. Click the **Monitor** button.

   The Monitor Intercom pop-up displays with a list of possible destinations.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-67a085c4cbac2b912a8fa4f379cbfd6a16bcf057%2Fjacquesmonitor_popup.png?alt=media)

   **Notes:**

   * The **Monitor** button is always enabled, unless the workstation is in remote mode, (i.e. the **Stop taking Calls** button was clicked, and is now called **Start taking Calls** ).

     **Note:** Whether the workstation intercom starts up in remote mode or not is determined by the Jacques Intercom Server and not by Command Centre Client, (i.e. the state of the **Stop taking Calls** button is not remembered as an operator or workstation preference in Command Centre).
   * This list excludes the workstation Intercom you are calling from.
3. Highlight the Intercom you want to monitor and click the **Monitor** button.

   You are returned to the Jacques Intercom Viewer. The workstation starts monitoring the Intercom and the connection appears in the list.

   You can now open a door or hang up the monitoring connection.


---

# 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/command-centre-client/using-command-centre/licensable-features/jacques-intercom-feature/monitoring-an-intercom.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.
