DIDs

Overview

The DIDs page manages inbound telephone numbers assigned to the selected tenant, including voice, fax, SMS, privacy, recording behavior, and routing destinations. Open it from Configuration > DIDs.

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

Display modes

The DIDs page can be shown in DataTable mode or jqGrid mode. Use the display mode toggle in the toolbar to switch between them.

DataTable mode

DIDs page in DataTable display mode.
DIDs page in DataTable display mode.

DataTable mode shows the standard table with search, sorting, page-size selection, row checkboxes, and bulk actions.

jqGrid mode

DIDs page in jqGrid display mode.
DIDs page in jqGrid display mode.

jqGrid mode shows the same DID records in an advanced grid with column filters and grid toolbar actions.

Working with DIDs

TaskHow to do it
AddSelect the New DID action, complete the form, and select Save.
EditOpen the DID from the list by selecting its name, number, or row action. Change the form and select Save.
DeleteSelect the row checkbox and use Delete Selected, or open the DID and select Delete, then confirm.

Page functions

ActionDescription
Outbound CallerID RegexsOpens the DID caller ID rewrite rules used for outbound caller ID presentation.
Outbound DIDsOpens the outbound DID management view.
New DIDOpens the creation form for a new DID.
Bulk DIDsOpens the bulk DID creation tool.
Delete SelectedDeletes selected rows after confirmation.
CSV/XLS UploadOpens import tools for bulk DID data.
Enable jqGridSwitches the table display mode for advanced grid controls.
DivertOpens the divert action for selected DIDs when available.

List columns

ColumnDescription
NumberThe inbound number or matching value.
Admin CommentInternal administrator note for the DID.
CommentTenant-facing or operational note for the DID.
Max ChannelsMaximum simultaneous channels allowed for the DID.
RecordingRecording policy shown for inbound calls on the DID.
CallerID PrefixPrefix applied to inbound caller ID number or name.
Unconditional forwardDestination used when unconditional forwarding is enabled.
Inbound Call RatesRate profile applied to inbound calls.
ActionRow-level actions available for the DID.

Demo records

The tenant contains documentation demo DID records such as Docs Demo DID 1 and Docs Demo DID 2.

Create and Edit DIDs

Use Create and Edit DIDs to add or maintain inbound numbers for the selected tenant. The same form is used for new DIDs and existing DIDs: a new DID starts with tenant defaults, while an existing DID opens with the saved values.

The screenshots use the Canistracci Oil tenant.

Creating and editing

ActionDescription
CreateOpen Configuration > DIDs and select New DID. Fill the required fields and select Save.
EditOpen an existing DID from the DIDs list. Update the required fields and select Save.
DeleteWhen delete permission is available, open the DID and select Delete, or delete selected rows from the list. Confirm only after checking destinations and call-flow references.

Information

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

Use this section for the DID identity, channel limits, privacy behavior, emergency caller ID behavior, branch or department classification, inbound call rate, provider, and administrator notes.

BlockPurpose
NumberSets the DID number. Depending on system format settings, the number can be entered as country, area, and number fields or as a single value.
Comment and admin commentStores visible and internal notes for list views and administration.
Max ChannelsLimits simultaneous use of the DID. Empty means unlimited; zero disables usage.
CNAM and privacyControls caller-name lookup and whether inbound caller ID is hidden.
Emergency caller IDMarks the DID for emergency caller ID use and stores emergency notes when enabled.
Branch, department, rate, and providerClassifies the DID and links it to inbound rating or DID provider data when those options are available.

Voice

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

Use this section for voice-call forwarding, recording, caller ID prefixes, and the main inbound destination.

BlockPurpose
Unconditional ForwardRoutes all inbound calls to the selected destination when enabled.
RecordingControls whether inbound calls are recorded and whether callers or called parties can start or stop recording.
Email recording and minimum sizeSends matching recordings to configured recipients and suppresses very small recordings when a minimum size is set.
Transcript, summary, and sentimentEnables AI processing for recorded calls when the tenant supports those services.
Caller ID prefixesAdds prefixes to inbound caller ID number or name before the call is delivered.
DestinationSelects the normal inbound destination for calls to the DID.

Fax

Fax section on the DID edit form.
Fax section on the DID edit form.

Use this section for inbound fax detection, fax routing, store-and-forward behavior, direct print or storage destinations, fax identity, and post-receive actions.

BlockPurpose
Receive FaxControls whether the DID never receives faxes, autodetects faxes, forces fax handling, stores and forwards, or sends faxes to print/storage.
Fax Routing ProfileSelects the routing profile used for outbound faxes when this DID is used as caller ID.
Forward or print/storage targetSets the forwarding number or external print/storage target used by the selected fax mode.
Fax station and headerSets the station ID and header text shown on fax documents.
Fax ProtocolSelects T.38, G.711, or mixed fax protocol behavior.
Email, store, and success destinationControls fax delivery by email, whether received faxes are stored, and where the call continues after a successful fax.

SMS

SMS section on the DID edit form.
SMS section on the DID edit form.

Use this section for SMS reception protocol, message field mapping, message delivery, storage, and routing destination.

BlockPurpose
ProtocolSelects whether the DID supports SMS and how inbound SMS data is received.
IMSI and field mappingMaps inbound SMS source, destination, body, and MMS link fields for custom payloads.
Email and storeControls notification delivery and whether messages are stored.
DestinationSelects the destination used when an inbound SMS is received.

Third party integration - Additional fields

Third party integration additional fields section on the DID edit form.
Third party integration additional fields section on the DID edit form.

Use this section for additional tenant-specific or integration-specific DID fields. The visible fields depend on the enabled integrations and custom template options.