740 Matrix PRASAR UCS System Manual
• D's number is found in the CLI Based Routing Table
• The system checks the destination number stored against D's CLI.
• A's number is found as the destination extension.
• The system lands the call on A.
If D's number does not exist in the CLI Based Routing Table, the call will be routed according to the incoming
call management logic.
How to configure
For this feature to work, you must do the following:
• enter the numbers of the calling parties and the numbers of the corresponding destination extensions in
the CLI Based Routing Table. You can store up to 2000 numbers in the CLI Routing Table.
• enable CLI Based Routing on the desired trunks according to time zones in their “Trunk Feature Template”.
Creating CLI Routing Table
To apply this feature,
• On a sheet of paper, create a 5-column table, as illustrated below. Each calling party number in the CLI
table is stored a location index in the system. Enter the telephone numbers and names of the calling
parties and the corresponding landing destinations, that is, the Port Type and Port Number. The Port Type
may be SIP Extension, Routing Group, Virtual Extension or Voice Mail Auto Attendant.
• The 'Name' field is for identifying the entry. When placing a call on the destination extensions, both the
number and the 'Name' are presented in the CLI.
• Determine the method which the system should use to match the incoming CLI with the numbers in the
table, that is, Match from last digit of CLI or Match from first digit of CLI Based Routing Table.
Configuring CLI Based Routing using Jeeves
• Login as System Engineer.
Index Phone Number Name Port Type Port Number
1 2640459 MidasBiz Routing Group 0002
2 022281110001 Jet Set SIP Extension 0004
::
10 2640075 Bacchus Routing Group 0003
To Next Page
Loading...