Skip to end of metadata
Go to start of metadata
In this article

LNP/MNP Processing in JeraSoft Billing

LNP/MNP functionality in JeraSoft Billing allows managing the ported numbers using external databases.

Please note that you need to have access to external databases to use it with our system.

There can be 2 database types to use for obtaining the external data:

DB TypeConnection with JeraSoftDB
1With the file integrationThrough a Data Source, Number Portability Gateways, and Traffic Processing rules

JeraSoft LNP CommonNumuriLithuanianTJA (Routing Number)TJA (Owner)

2Without the file integrationOnly through Traffic Processing rules. Doesn't require a Data Source or Number Portability GatewaysBroadvox, PCT, Vera Networks

Depending on the database you use (with/without the file integration), the system will perform different steps to get the ported number and route it according to the Traffic Processing rule. Therefore, configurations will differ based on the database.

Figure 1: LNP/MNP processing scheme

Note

When the database is local and has both ranges and single numbers present in it, we always select the most recent record by date (regardless of whether it is a single number or a range).

Configuration Use Cases

Billing by the routing number

In this use case, we will set up the simple process of billing and routing the call based on the routing number (using TJA (RN) database as an example).

Step 1 - Create a Data Source to connect JeraSoft to TJA (RN) database

Go to the Data Source section, and create a Data Source with a required connection type.

Info

Connection types you may use:

IMAP - to import files from your mail server; for this type, the format of the file must be .csv.zip;
Web (Numuri) - to download files in web mode; for this type, the format of the file must be .csv;
FTP - to connect to a server;
SSH -  to connect to a server.

Step 2 - Set up the Number Portability Gateway

In the Gateways tab of the Number Portability section, open the gateway settings of the TJA (RN) collector. Select a preconfigured Data Source for the gateway.

At first, downloaded files will be displayed in the Downloads History tab. After being parsed by the Files Collector tool, numbers will be displayed in the Number Portability tab:

Screenshot: Number Portability section

Step 3 - Set Traffic Processing rules to dip for the routing number

For this, go to the Traffic Processing section, and create two new Traffic Processing rules - one for Origination and one for Termination - using the settings below:

Information blockFieldValue
GeneralStage

After Client, so that the rate for the routing number will be used (a number that is stored in the LNP/MNP database) 

Originorigination/termination respectively
FiltersAccountSelect Originator/Terminator Account respectively
Dst Match^372(.*)$ - this POSIX syntax indicates that if the DST number starts with 372, this rule will work
ActionsModeAllow
LNP/JurisdictionLNP/MNPtja.ee (Routing Number)
LNP PartyDst Party ID

Screenshot: Origination TP Rule

Screenshot: Termination TP Rule

After all of the needed rules will be configured, you can test the setup by doing a Routing Analysis

Screenshot: Routing Analysis section

Please also note that Origination and Termination Rates, Routing Plan, Routings Analysis for this example case use the numbers including the prefix 372. This is applicable only to TJA (Routing Number) database.

Billing by the original number

In this use case, we will set up the process of billing the calls based on the original number, and use the dipped number for routing (using the JeraSoft LNP Common database as an example).

Step 1 & 2 - Same as previous

Step 3 - Set Traffic Processing rules to dip the database

For this, go to the Traffic Processing section, and create two new Traffic Processing rules - one for Origination and one for Termination - using the settings below:

Information blockFieldValue
GeneralStage

After Rate - so that the rate for the original number will be used for billing; the routing number will be used for routing

Originorigination/termination respectively
FiltersAccountSelect Originator/Terminator Account respectively
Dst MatchIndicate a pattern here in POSIX syntax for this rule
ActionsModeAllow
LNP/JurisdictionLNP/MNPJeraSoft LNP Common
LNP PartyDst Party ID

These rules will dip the internal database if they match statistics respective to the filters specified. The number will be translated after the rating stage, which means the routing will be conducted using a translated number. 

After all of the needed rules will be configured, you can test the setup by doing a Routing Analysis.

Returning of the original number

If there is a need to revert all LNP/MNP processing before sending the number further to a vendor for any of the cases, please enable the respective option in the Traffic Processing rule in question:

Screenshot: Reverting LNP/MNP processing

For versions 3.21&older

To revert any processing done on the number before sending it further to a vendor, you will need to perform backward translation after routing has been done. The system supports defined variables for original numbers: $src_lnp_original_number$ $dst_lnp_original_number$. The following rule needs to be configured for Origin: termination:

FieldValueReason
TypeAfter Routing

To return an original number to the vendor after the Routing Table has been generated.

Match
Src Match^.*$To match all the numbers.
Dst Match^.*$
Action
ModeAllowTo allow such traffic for further routing.
Src Replace$src_lnp_original_number$This placeholder replaces the translated source number with an original one that it was before dipping.
Dst Replace$dst_lnp_original_number$This placeholder replaces the translated destination number with an original one that it was before dipping.

Editing the Number Range

In order to edit the Number Range:

  1. Go to the Number Portability section.
  2. Click the button for the desired range to make changes.

Screenshot: Number Portability section