Page tree
Skip to end of metadata
Go to start of metadata

DID list allows you to create multiple DID lists and associate a name to each group. You can then use this information to perform routing decision by a query from the dialplan.

Create a DID file

The first step to setup the DID list is to create a csv file. The first row of the file is the field names (did). Each addition row is an entry to the DID list. Save the file with csv extension.

In the above example, we have 5 DIDs.

Submit the DID file

Go to "Configuration" -> "Routing" -> "DID List"

Click the "Upload" button.

Select the csv file generated above and click "Add".

Confirm the file name, the total number of DID entries.

Enter the list name for this file and click "save".

The uploaded file will be displayed. You can upload multiple csv files, duplicate DID entries to the same List will be rejected.

Apply the changes from WebUI.

If this is an initial setup for DID List, please restart "Netborder Session Controller" service from 

"Overview" -> "Dashboard" -> "Control Panel"

If you are adding additional DID List file with DID List perviously configured, restarting "Netborder Session Controller" is not necessary.

DID List configuration is now completed.

DID Query from Basic Call Routing

In a Basic Call Routing dialplan, add a Condition as follows:

(1) Select DID action

Select on of the following from the first drop down box

"Known Destination Number" - To find the destination number (in Request URI user part) of the call in the DID list.

"Known From Number" - To find the From number (in SIP From header) of the call in the DID list.

"Known To Number" - To find the To number (in SIP To header) of the call in the DID list.

(2) Select DID list

Select a DID List from the List drop down.

(3) Specify match action

Enter either ^true$ or ^false$ in the expression field.

^true$ - It is a match if the number is found in the DID list.

^false$ - It is a match if the number is NOT in the DID list.

This option enable you to use matching/unmatching DID in nested diaplan condition.

In the above example, a search of the From number is performed on DID list "List1". If the number is NOT in the list, the actions in "Actions to perform if condition matches" will be performed. If the number is found in the DID List1, he actions in "Actions to perform if condition doesn't matches" will be performed

DID Query from Advanced Call Routing

When routing a call using Advanced Call Routing, you can make a query to see if a DID belong to a list and use the result to route the call.

To see if DID 1235 belongs to DID list1, add the following to the dialplan.

    <action application="set" data="did_result=${did_list(List1 1235)}"/>

The variable did_result will be "true" if the DID exists in the list, otherwise "false".

You can also create a condition as follow:

    <regex field="${did_list(List1, ${destination_number})}" expression="^true$">

This condition matches if the destination number is found in DID List1.

  • No labels