DIDs

DIDs (Direct Inward Dialing) are telephone numbers, and the configuration in the DID section defines the behavior of those phone numbers.

Edit DID

General

  • Destination
PBXware destination to which DID will transfer all calls.
(E.g. Extensions)
  • Value
Destination value to which all DID calls will be transferred
(E.g. If 'Destination'='Extension', set the extension number here(e.g. 1002). In case 'Destination'='IVR', set the IVR extension number here)

TIP: If using 'Fax to E-mail' as 'Destination', set the 'Value' field to an email address (email@domain.com) or extension number (1002). If an extension number is used, the fax will go to the email address associated with the extension. The email which arrives to the specified address will contain both TIFF and PDF versions of the FAX

Advanced Options

 

General

  • Operation Times:
Set the DID operation time
  • CLI Validation & Routing
Configure Validation & Routing
  • Greeting
Greeting which is played when calling this DID
When uploading a greeting for DID, the name of the sound file must start with 'greeting-did-'
  • Strip N digits
Here you can set the number of digits which will be stripped from the beginning of the incoming call.
(E.g. 3)
  • Replace Caller ID
Replaces the caller id with the custom data provided here. This is used when you want all incoming DID calls to have this value displayed as a caller id information. Along with the custom data, you can use the '%CALLERID%' variable, which displays the calling party phone number.
NOTE: Please make sure you enter this information as it is written down, otherwise, it will not work properly.
(E.g. Providing a 'USDID' here, will display 'USDID' on your phone display, for all calls coming through this DID. Providing 'USDID %CALLERID%', will display 'USDID 55510205' on your phone display, where 55510205 is calling party phone number).
  • Queue Priority
Set the Queue priority
(E.g. If this DID redirects all calls to the queue, set '1' here to give all calls over this trunk the highest queue priority).
  • Custom Ringtone
If you are directing calls to an extension on which a supported UAD is registered, you could set a Custom Ringtone with which the phone will ring.
  • Record Call
If this option is turned on the incoming call on this DID will be recorded. When this option is turned on, a complete call will be recorded, whenever it goes or whatever happens to it
(Option buttons)
  • Notify on Not Answer
If set to ‘Yes’ - any calls that are not answered on this DID will be logged for the next notification e-mail.
(Option buttons)

Operation Times

Set the system open/closed times. Depending on the time when the call is received, the call can be redirected to different destinations.

  • CSV Upload
Click on this button to upload Operation Times configuration from csv file
  • CSV Download
Click on this button to download Operation Times configuration to csv file
  • Download CSV Template
Download CSV Template button will present you with a file that already contains necessary headers which should help you create CSV file easier
  • Enable operation times
Enable operation times
(E.g. Yes, No, Inherit)

Default Destination

  • Default Destination
PBXware MT extension to which all calls are redirected during the closed time hours
(E.g. 1000)
  • Is Voicemail
Choose if Default Destination is voicemail

Greeting

  • Greeting:
Greeting sound file played to callers during the closed times
(E.g. greeting-***)

Options

  • Closed dates Sets the specific date/s when all calls are redirected to the 'Default Destination'. If the 'Destination' field in the Closed dates is set, calls will not go to the 'Default Destination' but to this number.
  • Custom Destinations: Redirects all calls received during non-working hours (e.g. weekend) to the PBXware MT extension provided here.
  • Open dates: Sets the working hours during which the DID is to redirect calls as set in the DID Add/Edit window. If any call is received during the hours not set here the call is redirected to 'Default Destination'.

CLI Validation & Routing

 

This option is used to fine tune the functionality of the DID by adding rules which send the calls to different destinations based on Caller IDs. For example, if the caller's ID begins with 203, you can send all those calls to the IVR, if the CallerID is specifically number 063456789 then send that call to extension 4444 etc...

Once you click on CLI Validation & Routing button on Edit DID page, new window with following option will be shown:

  • CSV Upload
Click on this button to upload CLI Validation & Routing configuration from csv file
  • CSV Download
Click on this button to download CLI Validation & Routing configuration to csv file
  • Download CSV Template
Download CSV Template button will present you with a file that already contains necessary headers which should help you create CSV file easier
  • Caller ID
The Caller ID which is matched in the rule.
(E.g. 063456789)
(Display)
  • Destination
The type of destination to which the call will be directed.
(E.g. IVR)
  • Extension
Extension of the destination or selection where the call should go.
(E.g. 2222)
  • Match Type
How the Caller ID is matched.
(E.g. If we set Match explicitly to ‘yes’ here will be written ‘Explicit Match’. If we set this option to ‘No’ or ‘Not Set’ here will be written ‘Begins With’.)
  •  Edit
Edits the CLI Validation & Routing configuration
  • Delete
Deletes CLI Validation & Routing Rule from the system

Add/Edit CLI Validation & Routing Rule

  • Caller ID
The Caller ID which is matched in the rule.
(E.g. 063456789)
  • Destination
The type of destination to which the call will be directed.
(E.g. Queue)
  • Extension
Value of the destination or selection where the call should go.
  • Match Explicitly
Is Caller ID going to be matched 'explicitly' or with 'begins with'.
(E.g. Yes, No, Not Set)
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Getting Started: Admin Portal

Atlas Networks includes full support and managed move-add-change management for all voice...

Extensions

Extensions Extensions are the individual user accounts of the system, and can be thought of as...

Powered by WHMCompleteSolution