Docs for all releases
Page History
...
To perform a number translation, press Add Rule button and fill the following fields (see screenshot below):
Screenshot: New Traffic Processing rule
Information block | Field | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General | Type | Specifies, at what stage a current translation rule will be applied: | ||||||||||||
| ||||||||||||||
Scr Code Deck | Identify a code deck that will be used for src codes or code names filtering | |||||||||||||
Dst Code Deck | Identify a code deck that will be used for dst codes or code names filtering | |||||||||||||
Order | Sets rules ordering, first matched rule will stop further number translations.
| |||||||||||||
Origin | Sprecify 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 parameters for a trafic 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 Match menu.
| |||||||||||||
General | ||||||||||||||
Service | Select a target from the drop-down list of all services, presented in Services section of your VCS | |||||||||||||
Gateway | Select from the drop-down list a respective VoIP gateway for which rule is applied | |||||||||||||
Tags (Any) | A rule will work if event has at least one of the tags, specified in this field | |||||||||||||
Tags (All) | A rule will work if event has all tags, specified in this field | |||||||||||||
Tags (Not) | A rule will work if 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, and if expression matches the number, the translation will occur in respective settings in Src Replace field | |||||||||||||
Src Prefixes (Any) | A rule will work if event has at least one of the src prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Src Prefixes (Not) | A rule will work if event has no src prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Src Prefixes Names (Any) | A rule will work if event has at least one of the src prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Src Prefixes Names (Not) | A rule will work if event has no 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, and if expression matches the number, the translation will occur in respective settings in Dst Replace field | |||||||||||||
Dst Prefixes (Any) | A rule will work if event has at least one of the dst prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Dst Prefixes (Not) | A rule will work if event has no dst prefixes (e.g., 010, 810), specified in this field | |||||||||||||
Dst Prefixes Names (Any) | A rule will work if event has at least one of the dst prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Dst Prefixes Names (Not) | A rule will work if event has no dst prefixes names (e.g., vodafone), specified in this field | |||||||||||||
Client | ||||||||||||||
Client | Specify a respective client
| |||||||||||||
Account | Specify a respective account | |||||||||||||
Code | Specify a code of destination (use * as a wildcard) | |||||||||||||
Action | Mode | Defines an action that will be excuted if traffic rule matches:
| ||||||||||||
Scr Replace | Replacement for matched rule. In order this field to work, Scr Match filter must be used in Match information block. | |||||||||||||
Dst Replace | Replacement for matched rule. In order this field to work, Dst Match filter must be used in 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 provider fro 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 LNP/MNP field. |
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Best Practice Example To get a better understanding how Src/Dst Match and Src/Dst Replace fields work, let's consider the following example: If our scr/dst number is 123#456, Src/Dst Match field is ^123#(.*)$ and Src/Dst Replace field is 789\1, then the resulting number will be 789456. That's because ^123#(.*)$ expression tells the system that from 123#456 number system must remember only (.*) part which stands for 456. Now, in Src/Dst Replace field we have 789\1, which means that instead of123#456 it musy insert 789 + add \1 that equalls (.*). Therefore, our resulting number will be 789+456= 789456. These translation rules use the PostgreSQL regular expressions syntax (based on POSIX regex with some extensions). For more information, please refer to the PostgreSQL documentation portal. In addition, in Src/Dst Replace field you can insert random number with fixed digit length using $rnd(xxx-yyy)$ variable, where xxx - start number and yyy - end number of the range. For example, $rnd(050-950)$ will be replaced by a 3-digit random number from 50 to 950. |
...