Call Routing

The call routing table allows you manipulate how incoming calls are routed and processed based on the content of the caller ID, called ID, or SIP information (From, To, Agent, Contact or Identity).

To add a new entry in the routing table, click Insert. A new entry will be inserted at the top with the Order value set to the next available number. You can then click on each field to edit it.

To delete a routing entry, click on it to select it and then click Delete. The entry will be deleted from the table, without confirmation, but the deletion will not be permanent until you click Apply or OK.

To edit a routing entry, just click on the field you want to change. When finished, click Apply to save your changes or OK to save and then close the dialog.

When an incoming call is processed through the call routing table, each entry is checked in order based on the Order field, starting with 1 and ending with the entry with the highest value. To move an entry to a different place in the order, click on the Order field and use the list box to select the position you want. Selecting Top is the same as selecting 1 and selecting Bottom is the same as selecting the highest value. All other entries will be renumbered as needed to otherwise remain in the same order.

Check this box to enable the entry; remove the check to disable it. If this box is not checked, the entry will be skipped over when processing a call.

Select which field of the call data to use when checking if a call routing entry should be applied.

Enter the digits or characters to match. When applying a call routing entry against an incoming call, the system will compare the text entered in this field against the data in the selected Input Source in one of two ways:

Select the action to perform when the call routing rule is invoked. If relevant, fill in the Result field with the data required by the selected action.

The CSV Import command allows you to import from a CSV file formatted according to the old translation table format (from version 5.31 and earlier) and is provided for convenience for those who only want the simple substitution provided under the old system.

Note: In many cases, you can avoid translation altogether by adding a just two call routing rules, one with Input Source set to Caller ID and the other with it set to Called ID. In both cases, leave the Source contains field blank, the Action to take field set to Extension Search, and the Result field blank. For every call, the system will search the mailbox database for any mailbox where the Office Extension or an MWI address matches the caller (or called) ID and will replace the caller (or called) ID with that mailbox number before continuing to process the call.

The first line of the CSV file must be: SOURCE,RESULT. Each row after that is a single translation with the caller or called ID value on the left of the comma and the associated mailbox on the right. For each entry, the system will create two call routing rules: one for the caller ID and one for the called ID.

A third column is supported by DV2000 8.0.48 and above. This call is TYPE. This can be used when a full translation is not required allowing each column to specify if it's for Caller ID or Called ID. When adding this column use the following chart as the row value.

Example

SOURCE,RESULT,TYPE,
7101,1101,CALLED,

Consider the following simple example:

SOURCE,RESULT
7101,1101
7102,1102

On import, the system would create the following call routing rules, with the Order value set to the next available number and the Enabled box checked:

Note: Importing a CSV will not overwrite any existing rules; it will simply add the new ones, starting with the next available order value.

To import a properly configured CSV file, click CSV Import. A informational message will be displayed that briefly describes how the file must be formatted. Click Yes to continue, then use the Open dialog to select the file to import. Finally, click Open to import the file. All validly-formatted entries will be added to the call routing table as discussed above.

Beginning with DV2000 8.0.48 the entire call routing configuration can be exported allowing it to be imported on another system or saved for reference.

It's possible to either delete the called id or the caller id. These settings can be used to ensure the system doesn't integrate with a particular telephone number. For example in a hosted environment where the you may receive caller id from a 10 digit DID number and the called id from an extension number which matches a mailbox.

Another example might be there are multiple numbers which represent the DV2000 like hunt groups, DID numbers, or others extensions not used for registration.

This can be used to convert one number to another based on the source. In this example if the Caller ID contains 7101 it will be changed to 1234.

This action requires a matching value in the source column.

This special action performs some additional matching and searches in order to perform a given task. In this example we will demonstrate how to change the called ID based on a sub-string within the P-Asserted-Identity SIP field.

Using the # sign the system will match only up to that number of digits. If the source contains a prefix this prefix will be searched for in data before the system tries to perform a match.

1. System searches the string Hotel Operator>G 7101 Doe, Jane“ <sip:2800@192.168.11.67:5060> for the characters ”>G “.
2. If the characters are found, the system will then read up to the number of # in digits only.

The translation will work in other ways as well. Here the example sets the caller ID to only the first 3 characters and the second uses the last four of a telephone number.