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

# Jacques 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 Jacques.
{% endhint %}

The integration between Command Centre and **Jacques Intercom**. **From v7.40**, all integration components are merged into core code, so no separate installer is needed. A **licence string** is still required to enable the functionality.

* **v7.01** introduced the **Jacques Intercom Viewer**, letting an operator respond to a Jacques call from within Command Centre Premier. It lists calls made or forwarded to the workstation. Selecting one shows the intercom-specific Viewer Panel, or the default. The operator is **restricted from granting access (Open Door) until the call has been answered**.
* It introduced the **Camera (Jacques) tile**, addable to the Jacques Intercom Viewer, which shows a live feed from the Jacques intercom camera tied to the call event.
* **Group calls:** video of an unanswered call can multicast to **multiple Command Centre workstations at once** when group calls are configured.

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

## Networking protocols and ports

| Protocol/Port      | Flow                                     | Description                                                                        |
| ------------------ | ---------------------------------------- | ---------------------------------------------------------------------------------- |
| TCP/22             | To server                                | SSH/SFTP                                                                           |
| UDP/67, 68         | Server ↔ devices (or system ↔ 3rd party) | DHCP                                                                               |
| UDP/69             | Server ↔ intercom stations               | TFTP (firmware upgrades)                                                           |
| TCP/80             | To server                                | HTTP (Web Configuration)                                                           |
| TCP/123, UDP/123   | Server ↔ 3rd-party systems               | NTP                                                                                |
| TCP/1234, UDP/1234 | Multicast from server                    | Auxiliary channels, RTP (RFC3550); optional, if Audio Streaming (ASU) is installed |
| TCP/3306           | To server                                | MySQL                                                                              |
| UDP/5060           | Server ↔ 3rd-party SIP devices           | SIP                                                                                |
| UDP/5678, 5679     | Connected devices in call                | Audio Data, RTP (RFC3550)                                                          |
| UDP/19208          | Device ↔ server                          | Jacques Call Control Protocol (JCCP)                                               |

***

🔗 **Related**

* [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/jacques-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.