Versions Compared

Old Version 2

changes.mady.by.user Anastasiia Kovalinas

Saved on

compared with

New Version 3

changes.mady.by.user Anastasiia Kovalinas

Saved on

Key

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

...

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:

...

Column NameDescription
IDRules identification number
TypeType of a rule
General

Depending on rule parameters, a table can display the following scope of details:

  • Name of service, the rule is created for
  • Gateway, specified in a rule
  • Tag(s), indicated in a rule
Client

Depending on rule parameters, a table can display the following scope of details:

  • Client's name, specified in a rule
  • Client's account, defined in a rule
  • Indicated Code
Prefixes

Depending on rule parameters, a table can display the following scope of details:

  • POSIX regular expression for Src number (Src Match)
  • POSIX regular expression for Dst number (Dst Match)
  • Src Prefixes (Src P Any/Src P Not)
  • Src Prefixes Names (Src PN Any/Src PN Not)
  • Dst Prefixes (Dst P Any/Dst P Not)
  • Dst Prefixes Names (Dst PN Any/Dst PN Not)
Action

Depending on rule parameters, a table can display the following scope of details:

  • Replacement for a matched rule for Src number (Src)
  • Replacement for a matched rule for Dst number (Dst)
  • List of tags, added  added during traffic processing rule execution
UserUser name and time, when a rule was created/edited
OrderSpecified order for rule execution

...

In the top right corner of the section above the table, an Advanced Search drop-down menu is located. By clicking on a blue downwards arrow downward arrow  icon, a drop-down menu with the following structure is displayed:

...

Information blockFieldDescription
General


TypeSpecifies, at what stage a current translation rule will be applied:
  • Initial - execute this rule before a Client is identified
  • After Client - execute this rule after client identification but before rate identification
  • After Rate - execute this rule after rate identification but before routing
  • After Routing - execute this rule after routing
Src Code DeckIdentify 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.

Panel
borderColor#ffffb3
bgColor#ffffb3
borderWidth2px

(warning)   Attention

Note that this field indicates the order of rules execution only within a specified type. It means that a rule with the Initial type and order 1 will be executed before any other rule of the same type with order ≥ 2. However, such rule will be executed prior to a rule with the After Rate type and order 0, even though the latter has a higher order, due to the fact that Initialis the 1st on the types list.


Origin

Specify the event origin:

  • Origination
  • Termination
NotesSpecify additional informational about a rule
Expiration DateDefine 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.

Panel
borderColor#ccffcc
bgColor#ccffcc
borderWidth2px
borderStylesolid

Tip

If, for instance, the Client filter is empty, it means that this rule will implicate all clients.


General
ServiceSelect a target from the drop-down list of all services, presented in the Services section of your JeraSoft Billing
GatewaySelect 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 prefixes (e.g., 010, 810), specified in this field
Src Prefixes (Not)A rule will work if an event has no 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 prefixes names (e.g., vodafone), specified in this field
Src Prefixes Names (Not)A rule will work if an 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. If an expression matches the number, the translation will occur in respective settings in the Dst Replace field.
Dst Prefixes (Any)A rule will work if an 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 an event has no 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 prefixes names (e.g., vodafone), specified in this field
Dst Prefixes Names (Not)A rule will work if an event has no Dst prefixes names (e.g., vodafone), specified in this field
Client
Client

Specify a respective client

Panel
borderColor#ffffb3
bgColor#ffffb3
borderWidth2px

(warning)   Attention

Please be advised that any traffic processing rule can have either the Client or Account field.


Account Specify a respective account
CodeSpecify a destination code (use * as a wildcard)
ActionMode

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

  • Allow - allow a current event to proceed. Stop further traffic processing rules within this type of rule;
  • Allow and Continue -allow a current event to proceed. Search for the next traffic rule;
  • Deny - deny a current event.
Src ReplaceReplacement for a matched rule. For this field to work, the Scr Match filter must be used in the Match information block.
Dst ReplaceReplacement for a matched rule. For this field to work, the Dst Match filter must be used in the Match information block.
Set ServiceAllows to change a specified service to another one while processing them
Tags AddHere 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

Panel
borderColor#ffffb3
bgColor#ffffb3
borderWidth2px

(warning)   Attention

In the VCS 3.17.0, a new feature regarding TJA database has been added. Starting from this version, while creating a new rule, in the LNP/MNP field, a user can select either tja.ee (Routing Number) or tja.ee (Owner). The difference is as follows:

  • tja.ee (Routing Number) - if a traffic processing rule executes, 372+Original Number will be substituted by 372+Routing Number, specified in the TJA database.
  • tja.ee (Owner) - if a traffic processing rule executes, 372+Original number will remain unchanged. Instead, a Dynamic Tag indicating an owner of the number will be added to the call.

Please find more about TJA database here.


LNP DirectionDefine, 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.

...