Docs for all releases
Page History
...
This section allows a user to configure and perform number translations. Here, you can add and remove rules for traffic processing. The section is presented in a the form of a table of traffic processing rules with the following columns:
Screenshot: Traffic Processing section
Column Name | Description | |
---|---|---|
ID | Rules identification number | |
Type | Type of a rule | |
General | Depending on rule parameters, a table can display the following scope of details:
| |
Client | Depending on rule parameters, a table can display the following scope of details:
| |
Prefixes | Depending on rule parameters, a table can display the following scope of details:
| |
Action | Depending on rule parameters, a table can display the following scope of details:
| |
User | User name and time, when a rule was created/edited | |
Order | Specified order for rule execution |
...
Button/Icon | Description | |||
---|---|---|---|---|
Allows creating a new traffic processing rule | ||||
Allows importing a .csv file with a traffic processing rule(s) | ||||
Allows exporting a current list of rules in a .csv format | ||||
Indicates that a rule origin is origination | ||||
Indicates that a rule origin is termination | ||||
Indicates the Allow action of a rule | ||||
Indicates the Allow and Continue action of a rule | ||||
Indicates the Deny action of a rule | ||||
Allows editing existing rules in a section list | ||||
Allows deleting a traffic processing rule from the system |
...
In the top right corner of the section above the table, an Advanced Search drop-down menu is located. By clicking on a bluedownwards arrow downward arrow icon, a drop-down menu with the following structure is displayed:
...
Information block | Field | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General | Type | Specifies, at what stage a current translation rule will be applied: | ||||||||||||
| ||||||||||||||
Src Code Deck | Identify a code deck that will be used for SRC Src codes or code names filtering | |||||||||||||
Dst Code Deck | Identify a code deck that will be used for DST Dst codes or code names filtering | |||||||||||||
Order | Sets rules ordering . First matched rule will stop further number translationsthat works within the same rule Type.
| |||||||||||||
Origin | Specify the event origin:
| |||||||||||||
Notes | Specify additional informational about a rule | |||||||||||||
Expiration Date | Define a date when this rule will expire and will be removed from the system | |||||||||||||
Match | On the Match menu, select required select the required parameters for a traffic processing rule. To cancel any filter, click on the delete sign next to its name. You can start a quick search by typing filters' names in the field at the top of the Match menu.
| |||||||||||||
General | ||||||||||||||
Service | Select a target from the drop-down list of all services, presented in the Services section of your VCSJeraSoft Billing | |||||||||||||
Gateway | Select a respective VoIP gateway, for which rule is applied, from the drop-down list | |||||||||||||
Tags (Any) | A rule will work if an event has at least one of the tags, specified in this field | |||||||||||||
Tags (All) | A rule will work if an event has all tags, specified in this field | |||||||||||||
Tags (Not) | A rule will work if an event has no tags, specified in this field | |||||||||||||
Scr Party ID | ||||||||||||||
Src (Match) | In this field, you may indicate POSIX regular expressions syntax, by which a number will be analyzed. If an expression matches the number, the translation will occur in respective settings in the SRC Replace field. | |||||||||||||
Src Prefixes (Any) | A rule will work if an event has at least one of the SRC Src prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Src Prefixes (Not) | A rule will work if an event has no SRC Src prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Src Prefixes Names (Any) | A rule will work if an event has at least one of the SRC Src prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Src Prefixes Names (Not) | A rule will work if an event has no SRC Src prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Dst Party ID | ||||||||||||||
Dst (Match) | In this field, you may indicate POSIX regular expressions syntax (see best practice example below), by which a number will be analyzed. If an expression matches the number, the translation will occur in respective settings in the DST Dst Replace field. | |||||||||||||
Dst Prefixes (Any) | A rule will work if an event has at least one of the DST Dst prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Dst Prefixes (Not) | A rule will work if an event has no DST Dst prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Dst Prefixes Names (Any) | A rule will work if an event has at least one of the DST Dst prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Dst Prefixes Names (Not) | A rule will work if an event has no DST Dst prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Client | ||||||||||||||
Client | Specify a respective client
| |||||||||||||
Account | Specify a respective account | |||||||||||||
Code | Specify a destination code (use * as a wildcard) | |||||||||||||
Action | Mode | Defines an action that will be executed if a traffic rule matches:
| ||||||||||||
Scr Src Replace | Replacement for a matched rule. For this field to work, the Scr Match filter must be used in the Match information block. | |||||||||||||
Dst Replace | Replacement for a matched rule. For this field to work, the Dst Match filter must be used in the Match information block. | |||||||||||||
Set Service | Allows to change a specified service to another one while processing them | |||||||||||||
Tags Add | Here you can add tags that will be added for events matching this rule | |||||||||||||
LNP/MNP | Define a provider for the LNP/MNP service, which will be dipped for translation
| |||||||||||||
LNP Direction | Define, which Party ID(s) (Src, Dst, or both) will be used for LNP dipping. To enable this feature, you need to specify the LNP/MNP field. |
...
By clicking on the Export button, you can download a current list of rules in a .csv file.
Screenshot: Rules export