> 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/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration.md).

# Intercom Viewer Configuration

The Intercom Viewer licensable feature enables an operator to place an intercom call or respond to an intercom call from within the Command Centre Client. The Intercom Viewer lists the intercom call events for the intercoms configured for the Viewer, where the call event has not been processed. Selecting a call event displays either the Viewer Panel configured specifically for the intercom for which the call event was generated, or the default Panel.

### Components

This integration has been tested using the following Commend software and hardware:

<table><thead><tr><th width="256">Software</th><th>Commend Native Hardware</th></tr></thead><tbody><tr><td>Commend Server: VirtuoSIS<br>(GE300 and GE800 are compatible)<br>Minimum firmware version PRO800 5.0</td><td><ul><li>Master: EE900A and Commend Intercom Client</li><li>Cell station: 100094-3</li><li>Door station: 100094-2</li></ul><p><strong>Note:</strong> Commend advises that all IoIP (Intercom over IP) devices produced by Commend should function with this integration. For further information please contact Commend.<br><strong>Third Party SIP Hardware</strong></p><ul><li>SIP Server: Grandstream</li><li>SIP Video Phone: T-CCS-SIP-MS1-W</li><li>SIP Video Door Intercom: T-CCS-SIP-DSV1</li></ul><p><strong>Note:</strong> Commend advises that not all SIP intercoms will function with this integration. Gallagher recommends that you contact Commend to understand if your intercoms are compatible.</p></td></tr></tbody></table>

### Licensing

The 'Intercom Viewer' is enabled by one of two licensable features, i.e. your licence file must contain either of the following options:

<table><thead><tr><th width="175">Feature</th><th>Licence options</th></tr></thead><tbody><tr><td>Commend Intercom</td><td><p><code>[Features]</code><br><code>CommendIntercom=1</code></p><p><code>[Limits]</code><br><code>Commend Intercom Systems=1</code><br><code>Commend Intercom=X</code> (Where <code>X</code> is the number of intercoms required)</p></td></tr><tr><td>SIP Integration</td><td><p><code>[Features]</code><br><code>SIP=1</code></p><p><code>[Limits]</code><br><code>SIP Devices=X</code> (Where <code>X</code> is the maximum number of SIP Device items your site can have configured)<br><code>SIP Services=X</code> (Where <code>X</code> is the maximum number of SIP Service items your site can have configured)</p></td></tr></tbody></table>

To configure the Intercom feature, perform the following procedures:

[Creating the Intercom Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration/creating-the-intercom-viewer.md)

[Configuring the Intercom Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration/configuring-the-intercom-viewer.md)

[Configuring Tiles](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration/configuring-tiles-for-intercom-panels.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/command-centre-client/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration.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.
