Docs for all releases
Page History
...
Information block | Field | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General | Stage | Specifies at what stage a current translation rule will be applied: | ||||||||||||
| ||||||||||||||
Order | Sets rules ordering that works within the same rule Stage.
| |||||||||||||
Origin | Specify the event origin:
| |||||||||||||
Company | Specify a Reseller for this rule to be executed under. Default - all resellers | |||||||||||||
Notes | Specify additional information about a rule | |||||||||||||
Expiry Date | Define a date when this rule will expire and will be removed from the system | |||||||||||||
Src Deck | Identify a code deck that will be used for Src codes or code names filtering | |||||||||||||
Dst Deck | Identify a code deck that will be used for Dst codes or code names filtering | |||||||||||||
Filters | Select the required parameters for a traffic processing rule on the Filters menu. 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 Filters menu.
| |||||||||||||
General | ||||||||||||||
Service ID | Select a target from the drop-down list of all services, presented in the Services section of your JeraSoft 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. | |||||||||||||
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, by which a number will be analyzed. | |||||||||||||
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
| |||||||||||||
Account | Specify a respective account | |||||||||||||
Dst Code | Specify a destination code | |||||||||||||
Dst Code Name | Specify a destination code name | |||||||||||||
Src Code | Specify a source code | |||||||||||||
Src Code Name | Specify a source code name | |||||||||||||
Parties ID Translations | Type | Define a type of translation:
| ||||||||||||
Order | Specify the order of translation
| |||||||||||||
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 Replace field. | |||||||||||||
Replace | Replacement for a matched rule. | |||||||||||||
Actions | Mode | Defines an action that will be executed if a traffic rule matches:
| ||||||||||||
Add Tags | Here you can add tags that will be added for events matching this rule | |||||||||||||
Set Service | Allows to change a specified service to another one while processing them | |||||||||||||
LNP / Jurisdiction | LNP/MNP | Define a provider for the LNP/MNP service, which will be dipped for translation
| ||||||||||||
Revert LNP | Allows returning original numbers to vendors after routing:
| |||||||||||||
LNP Party | 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. | |||||||||||||
US NANP | Define if NANP processing will be used for LNP dipping:
| |||||||||||||
Routing Blocks | Block Clients | Specify, which termination Clients to block for the originator, specified in the Filters block | ||||||||||||
Block Accounts | Specify, which termination Accounts to block for the originator, specified in the Filters block |
...