> 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/integrations/intercoms/austco-intercoms.md).

# Austco Intercoms

{% hint style="danger" %}
This is a legacy integration. For new sites, use the [SIP Integration](/knowledge-hub/products/integrations/intercoms/sip-integration.md) unless the site already runs Austco.
{% endhint %}

Gallagher's Austco integration has a core part and a customised part.

* **Core feature** (merged from **v7.10**): lets an operator respond to an intercom call event from within Command Centre Premier. The operator is **restricted from granting access (Open Door) until the call event has been acknowledged**. It introduces the **Austco Intercom Viewer**, which lists unprocessed call events for configured intercoms. Selecting an event shows the intercom-specific Viewer Panel, or the default Panel.
* **Customised feature** (added **v7.30**, requires a **custom installer**): allows calls to be **cancelled** from either the Austco Console or Command Centre.

**Versions supported:** v7.90 to v8.50.

***

🔗 **Related**

* [Commend Intercoms](/knowledge-hub/products/integrations/intercoms/commend-intercoms.md). Another legacy vendor integration.
* [SIP - BAS-IP Device Setup](/knowledge-hub/products/integrations/intercoms/sip-integration/sip-bas-ip-device-setup.md). The current, vendor-agnostic path.


---

# 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/integrations/intercoms/austco-intercoms.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.