> 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/configuration/integrate-verkada-intercoms-with-sip/configure-a-sip-fallback-extension.md).

# Configure a SIP Fallback Extension

Configure a Local SIP extension the intercom will call if it loses internet connection

A SIP fallback extension is a local SIP contact the intercom dials if it loses its network connection. The fallback extension does not need to be in the call list. When the intercom goes offline, it bypasses the call list and directly dials the fallback extension.

{% hint style="danger" %}
A fallback extension is required if your device is configured as an emergency intercom with a local SIP account enabled. A fallback extension is optional for non-emergency intercoms.
{% endhint %}

***

## Configuration

### Emergency intercoms

{% hint style="danger" %}
Follow the steps in [Configure an Intercom as an Emergency Phone](/intercom/configuration/add-and-configure-receivers-in-intercom/configure-an-intercom-as-an-emergency-phone.md) before you continue.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**Under Call > SIP Account, select:**

a. Click **Add Account** if this is your initial SIP integration.\
b. Click **Edit** if you have previously created a SIP account.
{% endstep %}

{% step %}
**Under Required, enter the following information:**

a. Sip Account Name\
b. Domain / Server\
c. User ID / Extension\
d. Offline SIP Fallback Extension\
e. Password / Secret

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

f. Click **Save**.
{% endstep %}
{% endstepper %}

### Non-emergency intercoms

{% hint style="danger" %}
Your intercom needs to be registered to your local SIP server to create a fallback extension. See [Integrate Verkada Intercoms with SIP](/intercom/configuration/integrate-verkada-intercoms-with-sip.md) for more information.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**Under Call > SIP Account, select:**

a. Click **Add Account** if this is your initial SIP integration.\
b. Click **Edit** if you have previously created a SIP account.
{% endstep %}

{% step %}
**Under Optional > Offline SIP Fallback Extension, enter your fallback extension.**

<div align="left" data-with-frame="true"><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-c09a0309fd0da58bcb6fd4a6808d1aecbab536e6%2Fb47e8a3aedcbb90b4f7857de945b3791e401d49c.png?alt=media" alt="" width="563"></div>
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}


---

# 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/configuration/integrate-verkada-intercoms-with-sip/configure-a-sip-fallback-extension.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.