# Overview

The **SIP Cause Codes** page maps SIP cause codes and dispositions to routing destinations or handling rules. Open it from **Configuration > Settings > SIP Cause Codes**.

The page works against the tenant currently selected in the top bar. The screenshots and demo rows were captured in the **Canistracci OIL** tenant.

<figure id="bkmrk-sip-cause-codes-list">![SIP Cause Codes list page in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/1xZsip-cause-codes-list.png)<figcaption>SIP Cause Codes list page in the Canistracci OIL tenant.</figcaption></figure>## Working with objects

<table id="bkmrk-taskhow-to-do-it-add"><thead><tr><th>Task</th><th>How to do it</th></tr></thead><tbody><tr><td>Add</td><td>Select the New SIP cause code rule action, complete the form, and select Save.</td></tr><tr><td>Edit</td><td>Open the SIP cause code rule from the list by selecting its name, number, or row action. Change the form and select Save.</td></tr><tr><td>Delete</td><td>Select the row checkbox and use Delete Selected, or open the SIP cause code rule and select Delete, then confirm.</td></tr></tbody></table>

## Page functions

<table id="bkmrk-actiondescription-ne"><thead><tr><th>Action</th><th>Description</th></tr></thead><tbody><tr><td>New SIP Cause Code</td><td>Opens the creation form for a new sip cause code.</td></tr><tr><td>Delete Selected</td><td>Deletes the selected rows after confirmation.</td></tr></tbody></table>

## List columns

<table id="bkmrk-columndescription-di"><thead><tr><th>Column</th><th>Description</th></tr></thead><tbody><tr><td>Disposition</td><td>Object setting shown by the form.</td></tr><tr><td>SIP Cause Code</td><td>Dialed value, identifier, or matching value used by the PBX.</td></tr><tr><td>Comment</td><td>Administrative note shown in lists and reports.</td></tr></tbody></table>

## Demo records

The tenant contains 1 documentation demo record for this page: 599 Docs Demo 1.

## Deleting records

Before deleting a SIP cause code rule, check references from call flows, destinations, schedules, reports, or provisioning objects. MiRTA PBX asks for confirmation before the delete is submitted.