> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/intercom/fr/configuration/wire-a-doorbell-chime-to-an-intercom.md).

# Raccordez un carillon de sonnette à un interphone

Raccordez un carillon de sonnette traditionnel et des transformateurs à votre interphone Verkada

Les interphones Verkada comprennent un relais de sortie que vous pouvez utiliser pour déclencher une sonnette/un carillon.

### Configuration requise

* 1 carillon de porte ou plus
* 1 transformateur de sonnette
* Fil de sonnette

***

## Configurer une sortie de carillon

{% stepper %}
{% step %}
**Dans Verkada Command, allez dans Tous les produits > Interphone.**
{% endstep %}

{% step %}
**Sélectionnez votre interphone et cliquez sur Paramètres.**
{% endstep %}

{% step %}
**Sous E/S > Sortie, sélectionnez Carillon. Le relais de l’interphone changera d’état et un carillon tiers pourra être alimenté.**
{% endstep %}
{% endstepper %}

### Câblez votre interphone

{% stepper %}
{% step %}
**Retirez le bornier ou le faisceau de câbles de l’arrière de votre interphone.**
{% endstep %}

{% step %}
**Raccordez la sortie COM du bornier à l’une des vis de borne du transformateur de sonnette.**
{% endstep %}

{% step %}
**Pour chaque sonnette, raccordez les bornes Front et Trans à la borne NO de l’interphone et à l’autre borne du transformateur de sonnette, respectivement, comme indiqué.**
{% endstep %}

{% step %}
**Réinsérez le bornier.**
{% endstep %}
{% endstepper %}

***

{% hint style="warning" %}
Si vous avez plusieurs sonnettes, câblez-les en parallèle.
{% endhint %}

#### Câblage du faisceau de câbles TD33

<div align="left" data-with-frame="true"><img src="https://2615340941-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-9faab6125c15094c2f4b7ff5408f022c58ec2691%2F6d3e614b39f9906a94f7e10ea432542e9e2dea1c.png?alt=media" alt=""></div>

#### Câblage du bornier TD52/53/63

<div align="left" data-with-frame="true"><img src="https://2615340941-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-17927d1f7352919b1d00777ea68f72f85a77043b%2F659cdb1c10a72f7a2ca03b06fb6080ce6e1e4c44.png?alt=media" alt=""></div>


---

# 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.verkada.com/intercom/fr/configuration/wire-a-doorbell-chime-to-an-intercom.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.