Routing Ops

From IPitomy Wiki
Revision as of 15:16, 23 October 2013 by Mike Lunn (talk | contribs)
Jump to navigation Jump to search

The Routing Ops feature allows inbound calls to route based on any one of the following

  • Inbound CID
  • Number Dialed
  • Collected Digits

Routing Ops can be used in conjunction with a Group as a filter app, or you can set a Routing Op entry as a destination anywhere in the system. A Routing app basically consists of one or more ‘expressions’ that resolve to be either True or False. The Operation evaluates each expression sequentially in the defined order (priority). If an expression resolves as True, the caller is immediately routed to the configured route destination for that expression. If the condition is False, the Operation evaluates the next expression. If all expression evaluate to False, the Operation will perform the default behavior based on how the App was invoked (filter or destination). Note: A disabled Routing Operation skips all expressions and performs the ‘default behavior’ based on how the App was invoked.


File:Application-Routing Ops-.jpg


Group Method

If the app is invoked as a Filter for a Group, the default behavior is to do nothing (i.e. stay in the group as if the filter was never invoked). Specifically, the ‘Default Destination’ field configured on the Route Operations Edit page is ignored.


Destination Method

If the app is invoked as a ‘Destination’, the default behavior is to route to the 'Default Destination’ field configured on the Route Operations Edit page.


Building a Routing Op

File:Application-Routing Ops-Edit.jpg



Field
Function
Default
Name
Name of the Routing Op.  You should rename to something clear that explains what the route does.
Routing Application
Operation Type
Can be set to Match List of Numbers (single variable, exact match) or Table Lookup (multivariable, exact match or mathmatical functions).  Once set, this cannot be changed.
Match List of Numbers.
Enabled
Toggle the Op ON or OFF
No
Prompt & Collect Digits
Defines if the system will prompt the caller to enter digits before evaluating expressions.  When you select Yes, additional fields are displayed.
No
Default Destination
Where a call will go if it does not meet a filtered status. (Destination method only, not needed for Group method)
None
Prompt to Play
Set this to a recorded prompt instructing the caller what digits to enter.  Only used when Prompt & Collect Digits is set to Yes.
1-sec-silence
Number of Digits to Collect

Total number of digits to collect. Only used when Prompt & Collect Digits is set to Yes.

4

Number of seconds to wait if no digits are entered

How long the system will wait for digits to be entered. Only used when Prompt & Collect Digits is set to Yes.
10

Number of Attempts to Allow Before Routing to the Failover Destination

How many tries the system will give the caller to enter their digits before routing to the Failover Destination. Only used when Prompt & Collect Digits is set to Yes.
3
Failover Destination
Where the call routes if the user does not enter digits
None
Available Group Selections
Groups that can be chosen to use the Group method of Routing Ops
All Unselected Groups
Selected Groups
List of Groups that have been added to this Routing Op
None


Configuring Expressions: Match List Method

File:Application-Routing Ops-Match List-Add Expression.jpg


Field
Function
Default
Input Type
Caller ID: Route by the CID of the caller
Dialed Number: Route by the DID dialed by the caller
Collected Digits: Route by digits entered by the caller after connecting to the PBX
Caller ID
Use the Right Most
Total number of digits to use in the input parameter
10
Starting in position X
Starting from the left, how many digits to skip before reading to compare to parameter
0
Collect X Digits
How many digits to read moving right from the starting positition
10
Match Input Parameter
This is where you will enter the values that will be compared, resulting in a True or False
None
If the input parameter X matches a member of the list
This can be set to Matches or Does Not Match, depending on the functionality you want to result in a re-routing of the call.
Matches
Route to Destination
Set this to any destination on the PBX, and will trigger when the input data matches the parameters configured.
None


Configuring Expressions: Table Lookup Method

File:Application-Routing Ops-Edit-TableLookup.jpg


  • Once the Routing Op has been saved as Table Lookup method, a button reading Manage Data will appear.  Click this to access the advanced methods of defining expressions available to the Table Lookup operation.


File:Application-Routing Ops-Table-Creation.jpg


  • Clicking Manage Data will bring up options to manually enter data into a new table, or to load a CSV file with the parameters you wish to use.


File:Application-Routing Ops-Table-Creation-Manual.jpg


  • Selecting Manual method will bring you to the next page, allowing you to define if the table created should have 1, 2, or 3 columns.


File:Application-Routing Ops-Table-Creation-Manual-Populate.jpg


  • Which takes you to the next page, allowing you to define the expressions in each column, as well as the ability to create or remove rows, allowing you to add or delete parameters.


File:Application-Routing Ops-Table-Creation-CSV.jpg


  • If you choose to load a CSV file, the page above will display.  With this you get to define how many columns the table will have, where to import each CSV column into the Routing Ops table, and then allowing you to browse to and load the file.


File:Application-Routing Ops-Table-Add Expression.jpg


Regardless of whether the manual or CSV method were used to create the table, the same page will display when you back out to the Edit page for the Routing Op and click Expressions.

Field
Function
Default