Call, SMS, and Fax Campaigns

Overview
The Call, SMS, and Fax Campaigns page creates outbound voice, SMS, or fax campaigns with scheduling, state, retry, and destination behavior. Open it from Configuration > Call/SMS/FAX Campaigns.
The page works against the tenant currently selected in the top bar. The screenshots and demo rows were captured in the Canistracci OIL tenant.
Call, SMS, and Fax Campaigns list page in the Canistracci OIL tenant.
Working with objects
Task
How to do it
Add
Select the New campaign action, complete the form, and select Save.
Edit
Open the campaign 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 campaign and select Delete, then confirm.
Page functions
Action
Description
New Campaign
Opens the creation form for a new campaign.
Delete Selected
Deletes the selected rows after confirmation.
Find
Searches for the number or record entered in the find field.
List columns
Column
Description
Name
Display name used in lists and references.
Tech
Object setting shown by the form.
Start
Object setting shown by the form.
End
Object setting shown by the form.
Calls Running / Max
Object setting shown by the form.
Max Attempts
Object setting shown by the form.
# Numbers/Max
Dialed value, identifier, or matching value used by the PBX.
State
Mode selector that changes the behavior of the object.
Demo records
The tenant contains 1 documentation demo record for this page: Docs Demo Campaign 1.
Deleting records
Before deleting a campaign, check references from call flows, destinations, schedules, reports, or provisioning objects. MiRTA PBX asks for confirmation before the delete is submitted.

Create and Edit Call, SMS, and Fax Campaigns
Use this page when creating a new campaign or editing an existing campaign from Configuration > Call, SMS, and Fax Campaigns.
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.
Form sections
Section
Description
Information
Core identity and routing fields for the object.
Voice
Voice calling behavior, caller handling, recording, and voice-specific limits.
Parameters
Additional runtime parameters used by the object.
Information
Information section on the edit form.
Core identity and routing fields for the object.
Voice
Voice section on the edit form.
Voice calling behavior, caller handling, recording, and voice-specific limits.
Parameters
Parameters section on the edit form.
Additional runtime parameters used by the object.
Main fields
Field
Description
Name:
Display name used in lists and references.
CallerID:
Select a fixed tenant DID or 
RANDOM - (Use a random DID). Random selection is performed separately for every campaign attempt.
CallerID Name:
Display name used in lists and references.
Tech:
Object setting shown by the form.
Type:
Mode selector that changes the behavior of the object.
Start:
Object setting shown by the form.
End:
Object setting shown by the form.
Week Time condition:
Object setting shown by the form.
Max # of campaign numbers:
Dialed value, identifier, or matching value used by the PBX.
Dial timeout:
Timing value used by the service.
On connect callerid name:
Display name used in lists and references.
confirm
Object setting shown by the form.
Confirm message:
Object setting shown by the form.
Max Channels:
Object setting shown by the form.
Check queue for free agents:
Object setting shown by the form.
Allowed channels for each of the free agents:
Object setting shown by the form.
Min num of free agents:
Object setting shown by the form.
Max Attempts:
Object setting shown by the form.
Sum other campaigns
Object setting shown by the form.
Delay Between Attempts:
Timing value used by the service.
Always Record:
Recording behavior or recording delivery setting.
Email recording to:
Email address used for notifications, delivery, or mailbox access.
Minimum Size (bytes):
Object setting shown by the form.
Fax quality:
Object setting shown by the form.
Page size:
Object setting shown by the form.
Page rotate:
Object setting shown by the form.
File in PDF or TIFF format:
File upload or file name used by the object.
Message:
Object setting shown by the form.
Saving and deleting
Task
How to do it
Create
Select the new action from the Call, SMS, and Fax Campaigns list, fill the required fields, and select Save.
Edit
Open the existing campaign, update the needed fields, and select Save.
Delete
Before deleting a campaign, check call-flow, destination, schedule, report, provisioning, or integration references. Use the row delete action or the form delete action when available, then confirm.
Random Caller ID
In the CallerID selector, choose 
RANDOM - (Use a random DID) to select a caller ID independently for each campaign attempt. The option is supported by voice, fax, and SMS campaigns.
The random pool contains DIDs assigned to the selected tenant and verified outbound DIDs. Tenant DIDs use the number formats enabled by the global DID format settings. MiRTA PBX does not generate an arbitrary telephone number.
A new number is selected for every attempted destination.
The configured CallerID Name is not randomized.
If the pool is empty, the tenant Default External CID Number is used.
For fax campaigns, the selected DID is retained for DID-specific fax metadata lookup.
For SMS campaigns, the selected DID becomes the message sender.
A campaign CallerID Regex rule or a provider caller ID modification can subsequently replace the selected number.
Only use numbers accepted by the outbound provider and permitted for the tenant. API-managed campaigns can enable the same behavior by setting 
ca_callerid, or its 
callerid alias, to 
RANDOM.

Campaign Numbers
The Campaign Numbers page manages the destination numbers attached to a selected voice, SMS, or fax campaign. Open it from Configuration > Call/SMS/FAX Campaigns by selecting Manage numbers for the campaign.
The page uses the tenant selected in the top bar. The screenshots below use fictional campaign data for documentation.
Campaign Numbers grid with the paste icon in the bottom toolbar.
Working with campaign numbers
Task
How to do it
Add one number
Use the grid add control, enter the phone number and optional fields, then save.
Edit
Select the existing row and use the grid edit control.
Delete
Select one or more rows and use the grid delete control, then confirm.
Bulk import
Select the paste icon in the bottom grid toolbar, paste the numbers, and select Import.
Bulk paste import
The paste icon opens a modal window designed for large lists copied from a text file, spreadsheet, or CRM export. Paste one phone number per line for a simple import.
Paste phone numbers modal with one number per line.
When pasting from a spreadsheet, MiRTA PBX reads tab-separated columns in this order:
Column
Imported field
1
Phone number
2
Description
3
Disposition
4-13
Custom fields F1 through F10, when those fields are used by the campaign type.
Import behavior
Blank lines are ignored.
The campaign maximum number limit is enforced during import.
If the limit is reached, MiRTA PBX imports the allowed rows and reports how many rows were skipped.
Each imported number is recorded in activity logging as an insert.
The paste shortcut directly on the grid uses the same bulk import behavior.
The import does not remove duplicates automatically; use Remove Duplicates after import when needed.
Related actions
Action
Description
CSV/XLS Import
Opens the structured file import workflow for campaign numbers.
CSV Export / XLS Export
Exports the current campaign number list when export permissions are enabled.
Remove Duplicates
Removes duplicate campaign number entries from the selected campaign.
Enable Auto-Refresh
Refreshes the grid periodically while campaign processing is active.