Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#ccffcc
bgColor#ccffcc
borderWidth2px
borderStylesolid
Best Practice Example

To get a better understanding of how the Src/Dst Match and Src/Dst Replace fields work, let's consider the following example:

If our Src/Dst number is 123#456, the Src/Dst Match field is ^123#(.*)$ and the Src/Dst Replace field is 789\1, the resulting number will be 789456. That's because the ^123#(.*)$ expression tells the system that from 123#456 number it must remember only the (.*) part, which stands for 456. Now, in the Src/Dst Replace field we have 789\1, which means that instead of 123#456, it must insert 789 + add \1 that equals (.*). 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 the Src/Dst Replace field you can insert random number with fixed digit length using the $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.

Creating a new Orig/Term Rule

To perform a translation for a specific pair of Originator and Terminator, switch to the Orig/Term Rules tab, click the Add Rule button, and fill in the following fields:

Screenshot: New Orig/Term rule

Image Removed

...

Select the required parameters for a traffic processing rule on the Match menu:

...

Specify a respective Origination client

...

Defines an action that will be executed if a traffic rule matches:

  • Allow 
  • Allow and Continue
  • Deny 

Rules Import

A user can import a .csv file containing a list of traffic processing rules. To import the file, click the Import button and a pop-up window with the following structure will appear:

...