> 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/schindler-middleware-events-do-not-reach-schindler.md).

# Schindler middleware events do not reach Schindler

Diagnose Schindler Call Manager Interface events by checking Triggered Output strings and Middleware logs.

Use this procedure when a Gallagher reader event does not reach Schindler. It confirms the Call Manager Interface Plugin and its output string.

### Check the Middleware log

1. Open the Middleware log folder on the Middleware PC.
2. Open the FMF log.
3. Present a credential at the Gallagher reader.
4. Find the outbound `triggerEvent(...)` entry.

The default log folder is:

`C:\Program Files (x86)\Gallagher\FTCAPI\Middleware Framework\Log\FMF`

### Confirm the output string

Use the Triggered Output string to identify the configured method.

| Output string         | Expected method |
| --------------------- | --------------- |
| `[CN]_[FC]`           | Call by ID      |
| `[CN]_[FC]_[CI]_[BT]` | Call by Profile |

A Call by Profile deployment needs all four fields. A two-field string prevents the Middleware from retrieving the profile through REST.

### Interpret the log entry

The outbound entry contains the External System Item name, terminal identifier, and output string. Its presence confirms the plugin receives and sends the reader event.

`[BT]` identifies a Gallagher `Card` or `Mobile` credential. It is not Schindler's Badge Type.

### Next checks

* Confirm the External System Item is included in the Action Plan
* Confirm the Call Manager Interface Plugin is running on the Middleware PC
* Confirm the profile name exactly matches the Schindler profile for Call by Profile


---

# 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/schindler-middleware-events-do-not-reach-schindler.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.