Page History

...

Information block

Field

Description

General

Type

Specifies, 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

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 translationsthat works within the same rule Type.

Panel

borderColor	#ffffb3
bgColor	#ffffb3
borderWidth	2px

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

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 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
borderWidth	2px
borderStyle	solid

Tip

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

General

Service

Select a target from the drop-down list of all services, presented in the Services section of your VCS

Gateway

Select a respective VoIP gateway, for which rule is applied, from the drop-down list

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. 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
borderWidth	2px

Attention

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

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:

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 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

Panel

borderColor	#ffffb3
bgColor	#ffffb3
borderWidth	2px

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 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.

...

Versions Compared

Old Version 7

New Version Current

Key