Docs for all releases
Page History
...
You can combine both routing rules (dynamic and static) while creating a routing plan , and also assign separate rules to each destination. Here you can find a list of created routing plans.
Screenshot: Routing Plans section
Column | Description | |
---|---|---|
ID | ID number of a routing plan | |
Name | Name of a routing plan | |
Reseller | Name of a reseller , a corresponding routing plan has been assigned to as an owner | |
Code Deck | Name of code deck that has been applied to a corresponding routing plan | |
Rules Hunting | A respective hunting rule that has been applied to a routing plan | |
DR Order | A name of dynamic routing order that has been selected to organize routing rules | |
Rules | A number of rules specified in a respective routing plan |
Functional buttons/icons, icons presented in the section , are as follows:
Button/Icon | Description | |
---|---|---|
Allows to create a new routing plan | ||
Allows to copy an existing routing plan to the section | ||
| Allows deleting a routing plan from the system |
Advanced Search
In the top right corner of the section above the table, an Advanced Search drop-down menu is located. By clicking on downward arrow icon, a drop-down menu with the following structure is displayed:
...
Screenshot: Routing Plans window
Information Block | Fields Description | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General Information | General routing plan information | |||||||||||||||||||||||||||||||||||||||||||||
Name | Title of a routing plan | |||||||||||||||||||||||||||||||||||||||||||||
Reseller | Define the reseller/owner of a current routing plan | |||||||||||||||||||||||||||||||||||||||||||||
Additional Routing Plan | Specify a DR plan, which will be additional for a current plan | |||||||||||||||||||||||||||||||||||||||||||||
Code Deck | Select a Code Deck if you wish to have names of your code to be specified in the Code Name field | |||||||||||||||||||||||||||||||||||||||||||||
Origination Limits | Define the company or companies, which will have access to this routing plan (also this restriction will be extended to their sub-companies). If there is no specified company, the following routing plan is available for all companies. | |||||||||||||||||||||||||||||||||||||||||||||
Termination Limits | Select the company or companies, which will have a limit in termination for vendors who use it (sub-companies are not included) | |||||||||||||||||||||||||||||||||||||||||||||
Rooting Loop Protection checkbox | Excludes originating client from the list of terminators. If it is unchecked, it will be possible to route calls between different accounts of the same client. It is enabled by default. | |||||||||||||||||||||||||||||||||||||||||||||
Rules Processing | Options of rules processing | |||||||||||||||||||||||||||||||||||||||||||||
Rules Hunting | Select a hunting mode (the way how rules will be executed). They are as follows:
By default, the longest only option is set. | |||||||||||||||||||||||||||||||||||||||||||||
DR Order | Specify a method of routes sorting in a routing table. The options are:
By default, the by code/appealoption is set. | |||||||||||||||||||||||||||||||||||||||||||||
Match Increments | Define if the system should check whether Customers' increments proportionally overlap Vendors' increments:
| |||||||||||||||||||||||||||||||||||||||||||||
PM | Define a Profit Margin value for a current rule here. It can be specified either as a percent value (e.g., 16%), or in a system currency (e.g., 5 for 5 USD). | |||||||||||||||||||||||||||||||||||||||||||||
Vendor Limit | Determine the number of allowed routes for the same vendor to use (if a vendor has multiple accounts). You can set the limit only for accepted account routes, not including the accounts blocked by the term groups. If the field is left empty, the number is unlimited. |
...
Once a routing plan has been created, routing rules are to be determined (see screenshot below). To do that, click on a routing plan's name and you will enter Routing Rules tab, then , click the Add rule button and fill in the following fields:
Screenshot: Routing Rules tab
Field | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Priority | Define a priority of rule execution if two or more rules have similar code or code name specified | ||||||||||||
Code | Enter a code, which will be used in a current routing rule, use * as a wildcard. If a DID type for a current routing rule is selected, you may specify a code:
By default, the Full DID option is selected. | ||||||||||||
Code Name | If you have a code deck assigned to this routing plan, a corresponding code name, specified in the Code field, will be displayed automatically. If no code deck is attached, the field will remain empty. | ||||||||||||
Type | Select a type of routing for a current rule:
| ||||||||||||
Terminator/Policy | If you selected static type, you may specify a termination client/account here; if you selected dynamic type, specify routing policy for the current rule | ||||||||||||
PM | Define a Profit Margin value for a current rule here.
| ||||||||||||
Params | A number of additional parameters available by clicking the icon (see screenshot below) |
| Specify a time profile from the list|||||||||||
| Set minimum and maximum length of destination number that will be matched by this routing rule | ||||||||||||
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Attention Please note that after changing balancing value, it is needed to restart SIP and/or RADIUS daemons. |
- Originator Tags
You can specify respective originator tags here. If nothing is specified, it works for all.
- all - applies for originators if all specified tags are present.
- any - applies for originators if at least one of the specified tags is presented.
- Terminator Tags
- Time Profile
- Balancing
Define the percentage or proportion amount of traffic, which will be sent to a respective vendor who participates in balancing
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Attention Please note that after changing balancing value, it is needed to restart SIP and/or RADIUS daemons. |
Info |
---|
Among the rules of the same priority, balancing will not be performed if the value is 100 or more in the Balancing field. |
- Number Length
- Min ASR
- Min ACD
checkbox
If this field is checked,
it means that rule search will be stopped when matched with the current one and all the consecutive rules will not be executed for a current call. The logic will be respected even if the rule marked with "Stop Hunt" will be rejected due to some reason during routing.
Info |
---|
If Stop Hunt is enabled, but the rule was rejected due to "Orig Tags" mismatch or "Reseller Mismatch" reasons, the option will be ignored to continue looking for routes, which are filtered based on originator. |
Screenshot: Routing rules settings
Import/Export tab
The Import/Export tab allows a user to either upload desired routing rules (choose a file on a computer through a form and click Process) , or download current routing plan rules in a .csv file by clicking the Process button (see screenshot).
...
Screenshot: Routing Plan tab
Knowledge Base Articles
...