Bulk DID Module User Guide
- Nathaniel Halbrooks
In PBX GUI software version 13+, this module is deprecated in favor of Bulk Handler. The two modules are not compatible. Please use Bulk Handler in 13+.
Overview
The Bulk DIDs module allows you to easily import all your inbound routes from a CSV. This will save you time if you need to set up routes for 20 or more phone numbers.
Logging in
From the top menu click Applications
From the drop down click Bulk DIDs
Exporting DIDs
You can choose to export all your existing DIDs to CSV. This will allow you to modify anything on each DID and re-import them.
Pressing the “Export DIDs” button on the main page should allow you to download the CSV of all your current DIDs.
You can now open this file in a CSV-friendly program, like Microsoft Excel, and make changes or add new entries.
CSV Fields Expand source
The table below explains each column in the CSV file. You can change the column order of the CSV file as you like, however, the column names must be preserved.
# | Field | Default | Allowed | Field Details | Description |
|---|---|---|---|---|---|
1 | action |
| add, edit, del |
| Add, Edit, or Delete an Inbound Route. |
2 | DID |
|
| DID Number | The incoming DID to match |
3 | description |
|
| Description | Provide a meaningful description of what this incoming route is |
4 | destination |
|
| Destination | The context, extension, priority to go to when this DID is matched. Example: app-daynight,0,1 |
5 | cidnum |
|
| Caller ID Number | Define the Caller ID Number to be matched on incoming calls. Leave this field blank to match any or no CID info. In addition to standard dial sequences, you can also put Private, Blocked, Unknown, Restricted, Anonymous and Unavailable in order to catch these special cases if the Telco transmits them. |
6 | pricid |
| CHECKED | CID Priority Route | This effects CID ONLY routes where no DID is specified. If checked, calls with this CID will be routed to this route, even if there is a route to the DID that was called. Normal behavior is for the DID route to take the calls. If there is a specific DID/CID route for this CID, that route will still take the call when that DID is called |
7 | alertinfo |
|
| Alert Info | ALERT_INFO can be used for distinctive ring with SIP devices. |
8 | grppre |
|
| CID Name Prefix | You can optionally prefix the Caller ID name. ie: If you prefix with "Sales:", a call from John Doe would display as "Sales:John Doe" on the extensions that ring. |
9 | mohclass | default |
| Music On Hold Class | Defaults to "default" |
10 | ringing |
| CHECKED | Signal Ringing | Some devices or providers require RINGING to be sent before ANSWER. You'll notice this happening if you can send calls directly to a phone, but if you send it to an IVR, it won't connect the call. |
11 | delay_answer |
|
| Pause Before Answer | An optional delay to wait before processing this route. Setting this value will delay the channel from answering the call. This may be handy if external fax equipment or security systems are installed in parallel and you would like them to be able to seize the line. |
12 | privacyman |
| 1 to enable | Privacy Manager | If no Caller ID is sent, Privacy Manager will asks the caller to enter their 10 digit phone number. The caller is given 3 attempts. The number of digits and attempts can be defined in privacy.conf. If a user has Call Screening enabled, the incoming caller will be asked to enter their CallerID here if enabled, and then to say their name once determined that the called user requires it. |
13 | pmmaxretries |
| 1 to 10 | Max attempts | Number of attempts the caller has to enter a valid callerID, only valid if privacyman is set to 1 |
14 | pmminlength |
| 1 to 15 | Min Length | Minimum amount of digits callerID needs to contain in order to be considered valid, only valid if privacyman is set to 1 |
15 | cidlookup |
| Number | CID Lookup ID | Number representing the index id for Caller ID Lookup Source |
16 | langcode |
| Language Code | Valid Language Code | A valid Asterisk language code such as 'en', 'fr' or 'sv' |
17 | faxdetect |
| yes or no | Detect Faxes | Attempt to detect faxes on this DID |
18 | faxdetectiontype |
| dahdi, nvfax, sip | Fax Detection type | Type of fax detection to use |
19 | faxdetectiontime |
| 2 to 10 | Fax Detection Time | How long to wait and try to detect fax. Please note that callers to a Dahdi channel will hear ringing for this amount of time (i.e. the system wont "answer" the call, it will just play ringing). |
20 | faxdestination |
|
| Destination | Where to send the call if we detect that its a fax. |
Importing DIDs
You can import a new CSV of DIDs at any time. To do this, we suggest you start by exporting at least one DID created on your PBX so you can see the proper CSV format. The top of the CSV file will show each field that you can define information for. These fields are the same fields you will see in the Admin GUI of the PBX, and each field is explained in the Inbound Routes module user guide.
The only column in the CSV that is not a field in your Inbound Routes module is the action field. The action field lets you define what action you want to take for each entry. Your options are:
add - If the entry is a new DID, you would set this to “add.”
del - If you want to remove the entry from the PBX, you would set this to “del.”
edit - If you want to edit the entry from what it has now for settings, you would set this to “edit.”
To import your new CSV, click on the “Choose File” option and pick the CSV you want to import from your local computer. Then press the “Load File” button when done.