> 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/jacques-isolate-function.md).

# Jacques Isolate function

The Jacques Intercoms 'Isolate' function is an override option. It enables an operator to effectively ignore calls from a specified intercom for a pre-configured period of time.

**Note:** Some intercoms cannot be isolated, (e.g. Gallagher video terminal and monitoring station).

### Configuring the Isolate function

Perform the following procedures to configure and use this function:

Adding permissions for bridged or remote modes

If a workstation is in bridged or remote mode, you must also add permissions (capabilities) for the workstation to isolate intercoms, otherwise the override will not work.

1. Open HeidiSQL and click the **Data** tab.
2. Assign a tag to each intercom for each workstation that you want to enable the ‘Isolate’ override on.

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

Setting a time limit for isolating in Jacques

The length of time an intercom is isolated for, by default is 15000 milliseconds (15 seconds). However, this time is configurable as follows:

1. In HeidiSQL, ensure the **isolate-allowed** value is set to "1", which indicates it is allowed to be isolated.
2. Set the **isolate-duration** value to the time required.

   In the example below, Intercom 333 is allowed to be isolated and the isolation duration is 15 seconds.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-94564460f32a6ce6337e36231487fd4a01fb2480%2Fjacques_setisolatetime.png?alt=media)
3. Restart the **Jccpserver** service for the changes to take affect.

   **Note:** If you change the **isolate-allowed** value to "0", log out and back into Command Centre, the **Isolate** option will be greyed out for Intercom 333.

### Using the Isolate function

When configured (as above), the **Isolate/Deisolate** function is available for an Intercom from a Site Plan or Status tile, as follows:

1. Either:

   * on a Status Tile, click on the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-896b081fa28b003ad94ed8ff39ddc852cff42812%2Fhoverarrow.png?alt=media) beside the Intercom
   * on a Site Plan Tile, right-click on the Intercom's icon

   A context menu displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-de14615a1870332f0400cba2bbc6abe0afabaa41%2Fjacques_isolateoption.png?alt=media)
2. Click **Isolate** from the context menu.

   The red 'Ghost buster' overlays the Intercom icon to reflect its change of status to "The intercom endpoint is isolated", and the **Isolate** option changes to **Deisolate**.

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

   No calls can be made from Intercom. However, operators can still make calls to the Intercom.

   **Note:** Deisolate returns the Intercom to normal, (i.e. calls can be made from the Intercom again).


---

# 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/jacques-isolate-function.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.
