> 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/configuration-client/site-installation/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-a-call-manager-external-system.md).

# Configuring a Call Manager External System

### Introduction

This topic describes how to create a Schindler Call Manager External System.

**Note:** Operators require the "Edit Site" operator privilege to be able to add, modify, and delete External Systems.

***

### Before you begin

Request Schindler integrators to create the Call Manager Interface in Schindler, and provide the TCP/IP Port Number of the Schindler Call Manager Interface shown in the Port field.

***

### Configuration

To configure a Call Manager External System, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...External System**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure a Call Manager External System:

<details>

<summary>API Setup tab</summary>

1. Click the **API Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-879539568b2e0da6c19d1e1b2f87d60709c726e1%2Fschindlercallmanager1.png?alt=media)
2. Select the appropriate **Controller** from the drop-down list.

   **Note:** Only standard Gallagher Controllers will work, (i.e. Gallagher UltraSec Controllers will not work).
3. Select the appropriate External System server from the **Server** drop-down list.
4. Click the **Unique** radio button in the 'Identity' section of this screen and type in a unique identity string. This field is limited to a maximum of 64 characters.

   **Note:** Should you have more than 100 terminals, click the **Same as** radio button and link the identity of this terminal to be the same as another by selecting a terminal from the drop-down list.

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

   **Note:** This tab only appears if the 'Identity' on the **API Setup** tab is set to 'Unique'.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-899902238ccb8c6f2936523e4507c8377a85a0c3%2Fschindler_callmanager2.png?alt=media)
2. Select the **SchindlerID Call Interface** middleware plug-in from the **System Type** drop-down list.

   The 'Configuration' section this tab becomes populated accordingly.
3. Enter the Schindler server IP address in the **IP Address** field.
4. Enter the TCP/IP Port Number of the Schindler Logging Task Interface in the **Port** field. Range 0-65535.
5. If required, enter a **Card Badge Expiration Time**. Range 1-600 seconds.

   If a user badges his/her card, this information is sent from the Controller to the Middleware Framework. The time between the information being sent, is checked by the Middleware Framework. If this time exceeds the Card Badge Expiration Time, the terminal is not enabled and an event is logged, as it assumes a network delay has occurred and the person may no longer be at the terminal.

</details>

7. Click the **Icons** tab if you want to change the Icon Set for this external system.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
8. Click the **Notes** tab if you want to add a note(s) about this external system.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/site-installation/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-a-call-manager-external-system.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.
