Skip to main content

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

SectionDescription
InformationCore identity and routing fields for the object.
VoiceVoice calling behavior, caller handling, recording, and voice-specific limits.
ParametersAdditional runtime parameters used by the object.

Information

Information section on the edit form.
Information section on the edit form.

Core identity and routing fields for the object.

Voice

Voice section on the edit form.
Voice section on the edit form.

Voice calling behavior, caller handling, recording, and voice-specific limits.

Parameters

Parameters section on the edit form.
Parameters section on the edit form.

Additional runtime parameters used by the object.

Main fields

FieldDescription
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.
confirmObject 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 campaignsObject 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

TaskHow to do it
CreateSelect the new action from the Call, SMS, and Fax Campaigns list, fill the required fields, and select Save.
EditOpen the existing campaign, update the needed fields, and select Save.
DeleteBefore 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.