# SIP Integration: Cisco Unified CM

You can easily add a Verkada intercom to Cisco Unified Communications Manager (Unified CM) just as you can add any other third-party advanced SIP device. Learn how to [get started with a Verkada intercom](https://help.verkada.com/intercom/get-started-with-verkada-intercom).

Once completed, you can receive calls from your TD52 on your SIP devices and initiate talk-down calls to your TD52 from your SIP devices.

***

## Integrate your intercom to Cisco Unified CM

{% stepper %}
{% step %}

#### Add your TD52 as an end user.

a. In the Cisco Unified CM portal, navigate to **User** **Management** > **End User** > **Add New**.\
b. Create a **User ID**, **Password**, and **Self-Service User ID** (This will be the TD52’s extension you will use in step 3.) *We recommend setting the Last Name as the User ID*.\
c. Ensure that your **Digest Credentials** are the same as the password you defined.\
d. The PIN is irrelevant for the integration to work, but must be set to *something.* As long as the field is non-empty we’re ready to move to the next step.

<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-40a46d46ef6c05334261b9e08ceb0525cbe857fd%2Fcc4c406ee27e6c8ae4e4871afa572cf437d6c741.png?alt=media" alt="" width="534"></div>
{% endstep %}

{% step %}

#### Add your TD52 as a device.

a. In the Cisco Unified CM portal, navigate to **Device > Phone > Add New.**\
b. For phone type, select **Third Party SIP Device (Advanced)**.

<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-4af170317e4f60e3cb860a38b9d879502495deb1%2F998e4c97dbbd8bcdc8534057a1b7d40e1844a7e4.png?alt=media" alt="" width="415"></div>

c. After saving, you’ll be directed to the device’s configuration page. Navigate to the **Device Information** section.

<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-4c53f8dc17b0229f58a7ec153175060f62b5f724%2F3f7037c06fefa80c5aa04333f0490b73ccd9b5c6.png?alt=media" alt="" width="400"></div>

d. Enter the media access control (MAC) address of your TD52. Find the MAC address on the back of the device or, in the device’s settings. Copy the rest of the settings shown above, making sure you select the **Owner User ID** that corresponds to the end user you created in step 1.\
​\
e. Scroll down to **Protocol Specific Information** and copy the settings (as shown below). Be sure to select the **Digest User** that matches the end user you created in step 1 and the **Owner User ID** you created in step 2.

<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-b69a73b4fdddaf27d0f06b6c953258edcf411235%2F948a235991b37b3f234aae60a7287aaa57728984.png?alt=media" alt="" width="401"></div>
{% endstep %}

{% step %}

#### Click **Save**. The Association window should appear on the left side of the screen.

<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-ba580a053f20002f41852b639f0d21e6fd355abb%2F000a31e5801ff1c5dea9ae13679ba645f282bfa4.png?alt=media" alt="" width="518"></div>

a. In the **Association** window, click **Add a New DN** and navigate to the **Directory Number Information** section.

<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-d63afe7d56bb9c12716cd66d86d336609697f224%2Fb2e692ab22a85a7a8cfa6ab0402385cd909566fe.png?alt=media" alt="" width="534"></div>

b. Copy the extension (defined in step 1) and paste it in to the **Directory Number** field.
{% endstep %}

{% step %}

#### Enable SIP functionality in Command.

a. Navigate to your TD52’s Settings page and scroll to the **Call** section.

<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-ef6e790c516be3250110d77a51e6f660d19f98d2%2F32da63ae8555debea9965276bd71474f2daf2f44.png?alt=media" alt="" width="294"></div>

b. Click **Add Account**. You should be redirected to the SIP Account configuration menu.

<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-40f545545a583da6bae5fa092b33cfa37c01fa27%2F766ad78642a39880f233630fbbddee8f921a5b5b.png?alt=media" alt="" width="398"></div>

c. Verify that your **Authentication Username** exactly matches the **End User ID/Owner User ID/Digest User** that you configured in steps 1, 2 and 3.\
d. In the **Domain/Server** field, type your SIP domain. **Note**: The default port is 5060, but you can change it by appending a custom port number; for example, cucm.example.com:5061.\
e. Fill in the **User ID** and **Password** fields with the values created in step 1 and click **Save**. If provisioning was successful, you’ll see a green checkmark under **SIP Account** in the **Device** settings.

<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-c79e29055deaa3a0e3bbf19fd8d7b74e8d2b0b5c%2F8377785c0b86807e11d257a53db278c2bf7705c9.png?alt=media" alt="" width="293"></div>
{% endstep %}

{% step %}

#### Add SIP extensions as receivers.

a. Navigate to your TD52’s **Receivers** tab.

<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-8bc41f61d24cd9f6e0d84b9381271c6865cc00cc%2Ffe7a01033a6fb815a634873ab67a54f0bea00178.png?alt=media" alt="" width="317"></div>

b. Click the plus (**+**) icon and select **SIP Phone**.\
c. Enter the extension of the recipient you want to add to the call list. When someone presses the call button, the call will be routed to the specified SIP extension. Alternatively, to call the intercom from your SIP device, simply dial its 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-e4b9c1397490341bb959deae2e575fbb3b1a54ff%2Fc6230c6afab35548cd276c35a25443aad67574c7.png?alt=media" alt="" width="363"></div>
{% endstep %}
{% endstepper %}

***

## Troubleshooting

#### Unlock Not Working (DTMF Mismatch)

There is a common issue where video and audio work well, but unlocking by pressing 0-9 does not. Customers often try to fix this by turning on MTP (Media Termination Point), which then breaks video.\
​\
This happens because Cisco phones are often configured to use DTMF payload 101, while the Verkada intercom negotiates for DTMF payload 121. Turning on Media Termination Point fixes this DTMF mismatch but breaks video.

Instead, make sure MTP is off for both devices. Apply the following SIP profile to both the phone, and the Verkada intercom in CUCM:

![](https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-29cb643337496827757530ca15addbb10ae09d46%2F4908f123bf454363ea7578bc488411c2c1a623e8.jpg?alt=media)

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=pgUM7Jwglng).
{% endhint %}

{% hint style="success" %}
**Need more help?** Contact [Verkada Support](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/need-help/contact-verkada-support).
{% endhint %}
