> 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/elevators/schindler/configure-schindler-call-by-id.md).

# Configure Schindler Call by ID

Configure Call by ID for Gallagher readers or Schindler terminals using synchronized Badge Numbers.

Configure Call by ID to send a credential identifier to Schindler. This method requires Schindler ID synchronization.

### Before you start

* Configure Schindler ID and confirm cardholder synchronization
* Choose either Call by ID or Call by Profile for the deployment
* Install a Schindler SAM card when terminals read Gallagher-encoded cards

### Configure Gallagher reader calls

1. Install the Call Manager Interface Plugin on the Middleware PC.
2. Configure the External System Item for the Schindler terminal.
3. Set the item's **Triggered Output** to `[CN]_[FC]`.
4. Configure an Action Plan to trigger the External System Item.

The output combines Card Number and Facility Code. Schindler matches it against synchronized cardholder data.

### Configure Schindler terminal calls

Schindler terminals use synchronized Badge Numbers for access decisions. They do not need the Call Manager Interface Plugin.

For Gallagher-encoded MIFARE Classic or DESFire cards, install a Schindler SAM card. The card must contain the site's MIFARE Site Key.

### Configure optional reporting

Install the Life/Live Reporting Plugin on the Middleware PC to receive Schindler events in Command Centre.

### Confirm the access flow

1. Present a credential at the Gallagher reader.
2. Confirm the Call Manager Interface Plugin sends the identifier to Schindler.
3. Confirm Schindler assigns the elevator and records its decision.

Use [Schindler middleware events do not reach Schindler](/knowledge-hub/products/integrations/elevators/schindler/schindler-middleware-events-do-not-reach-schindler.md) to verify the output string and Middleware logs.


---

# 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/elevators/schindler/configure-schindler-call-by-id.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.