# Custom Destinations # Overview The **Custom Destinations** page defines reusable routing destinations for special actions, custom dial strings, wait steps, AI flows, and other call-flow functions. Open it from **Configuration > Custom Destinations**. The page works against the tenant currently selected in the top bar. The screenshots and demo rows were captured in the **Canistracci OIL** tenant. The **SETQUEUETIMEOUT** type sets a temporary timeout override for the next Queue destination reached by the same call. After that Queue application is executed, MiRTA PBX clears the override and later queues use their configured timeout.

![Custom Destinations list page in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/7sKcustom-destinations-list.png)

Custom Destinations list page in the Canistracci OIL tenant.

## Working with objects

Task	How to do it
Add	Select the New custom destination action, complete the form, and select Save.
Edit	Open the custom destination from the list by selecting its name, number, or row action. Change the form and select Save.
Delete	Select the row checkbox and use Delete Selected, or open the custom destination and select Delete, then confirm.

## Page functions

Action	Description
New Custom Destination	Opens the creation form for a new custom destination.
Delete Selected	Deletes the selected rows after confirmation.

## List columns

Column	Description
Type	Mode selector that changes the behavior of the object.
Name	Display name used in lists and references.
Parameter	Object setting shown by the form.
Action	Object setting shown by the form.

## Demo records The tenant contains 1 documentation demo record for this page: Docs Demo Wait 1. ## Deleting records Before deleting a custom destination, check references from call flows, destinations, schedules, reports, or provisioning objects. MiRTA PBX asks for confirmation before the delete is submitted. # Create and Edit Custom Destinations Use this page when creating a new custom destination or editing an existing custom destination from **Configuration > Custom Destinations**. The form screenshots below are separated by block where the application exposes separate sections. Complete the required values, review routing or destination references, and save the record. ## Add and edit form

![Custom Destinations add/edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/UvAcustom-destinations-form.png)

Custom Destinations add/edit form.

## Main fields

Field	Description
Type:	Mode selector that changes the behavior of the object.
Name:	Display name used in lists and references.
Queue timeout:	Timeout in seconds to use for the next Queue destination only. Leave the custom destination out of the flow when the queue should use its configured timeout.
Phone number:	Dialed value, identifier, or matching value used by the PBX.
Dial timeout:	Timing value used by the service.
CallerID Number:	Dialed value, identifier, or matching value used by the PBX.
CallerID Name:	Display name used in lists and references.
Add diversion header:	Object setting shown by the form.
Diversion header CallerID Number:	Dialed value, identifier, or matching value used by the PBX.
Min silence time (ms):	Object setting shown by the form.
Silence threshold:	Object setting shown by the form.
Caller buddy language:	Caller ID or caller matching value.
Called buddy language:	Language or voice selection used for prompts, transcription, or speech synthesis.
Generative Artificial Intelligence:	Object setting shown by the form.
API key:	Object setting shown by the form.
Model:	Object setting shown by the form.
System Content:	Object setting shown by the form.
User Content:	Object setting shown by the form.
Assistant Content:	Object setting shown by the form.
Functions:	Object setting shown by the form.
Greeting Message:	Object setting shown by the form.
Temperature:	Object setting shown by the form.
Max Tokens:	Object setting shown by the form.
Realtime Voice:	Language or voice selection used for prompts, transcription, or speech synthesis.
Turn Detection:	Object setting shown by the form.
Semantic VAD eagerness:	Object setting shown by the form.
Server VAD threshold:	Server, host, or node selection used by the object.
Prefix padding (ms):	Dialed value, identifier, or matching value used by the PBX.
Silence duration (ms):	Object setting shown by the form.

## Type-specific fields The **Type** selection controls which settings are shown below the common fields. Simple destination types appear immediately. When a destination needs current PBX data—for example DIDs, queues, media files, campaigns, phonebooks, voicemails, conference rooms, flows, or AGI scripts—MiRTA PBX loads those fields on demand.

Action	What happens
Open an existing custom destination	The fields for its saved type load automatically and retain the current selections.
Change the Type	The previous type-specific fields are hidden and the fields for the newly selected type are displayed after their choices have loaded.
Return to a type already selected on the page	Its previously loaded fields are reused without requesting the same lists again.
Save while fields are loading	The Save controls remain unavailable until loading finishes, preventing an incomplete type-specific configuration from being submitted.
A loading error is shown	Select another type and then select the required type again, or reload the page, to retry.

Wait for the type-specific fields to appear before entering values. Only the selected type’s fields are submitted with the custom destination. ## Set Queue Timeout Select **Set queue timeout for caller** to set the timeout used by the next Queue destination reached by the call. The value is stored in seconds and is consumed once; after that, later queues use their normal configured timeout.

![Custom destination form for setting the next queue timeout.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/custom-destination-setqueuetimeout.png)

Custom destination form for setting the next queue timeout.

Field	Description
Queue timeout	Seconds to pass to the next Queue application instead of the selected queue’s stored timeout.

## Saving and deleting

Task	How to do it
Create	Select the new action from the Custom Destinations list, fill the required fields, and select Save.
Edit	Open the existing custom destination, update the needed fields, and select Save.
Delete	Before deleting a custom destination, check call-flow, destination, schedule, report, provisioning, or integration references. Use the row delete action or the form delete action when available, then confirm.