Docs for all releases
Jurisdictional billing in the USA supports domestic long-distance calls — phone calls made outside a certain local call area. For correct processing of such calls, JeraSoft offers Jurisdictional Billing Module, which supports jurisdictional routing in the USA with several features and solutions, including billing and routing over NPA NXX codes and support of LNP dipping from multiple vendors or over own database.
Jurisdictional Billing Module is based on the LERG database and determines a jurisdiction of calls doing the following steps (for versions before 3.20.0 JeraSoft Billing):
- Parsing LERG database from Iconectiv provider to the internal format (jurisdictional_table);
- After the client identification process, identifying NPA-NXX for both Source and Destination numbers and finding out the jurisdiction of the call through the internal jurisdictional table;
- Setting a tag combination to the one of the following:
Starting from version 3.20.0, JeraSoft Billing system allows not only LNP dipping but also processing the calls inside the USA through NANP. Our NANP Processing functionality allows checking the US phone numbers through the North American Numbering Plan. It is available for those clients who have access to the LERG database.
In order to use US Jurisdictional Billing & Routing, you have to populate LERG/LCA databases. JeraSoft does not provide these database files within initial deployment. You have to get your own access to these databases. The required files are:
- LERG 6
- LERG 8
- LCA Clusters
These files have to be uploaded to the following location on the JeraSoft Billing server: /opt/jerasoft/vcs-data/jurisdictional_files/
To apply full processing using our Jurisdictional Billing Module, you need to create a Traffic Processing Rule with the NANP Processing option enabled (you can view TP rules examples in USA Routing & Billing Configuration article).
If your business case only demands interstate/intrastate identification, you do not need to have access to LERG/LCA databases. For the system to process your calls correctly, you need to configure the following:
- Make sure the Jurisdictional Manager is on in System→System Services section.
- Create a file named nanp.csv in /opt/jerasoft/vcs-data/jurisdictional_files. Make sure that this file has vcs:vcs permissions.
- Wait till the next run of the Jurisdictional Manager or trigger it manually. It will populate the system with NANP data.
- Create two Traffic Processing rules: one for origination, and one for termination, with the following settings:
NANP Processing: Enabled
While in older versions the system sets tags in combinations only, starting from 3.20.0 JeraSoft Billing applies tags separately. The list of area tags the system assigns is as follows:
IntraLATA— the local calling area inside a LATA (Local Access and Transport Area);
InterLATA— refers to calls between two LATAs (long-distance call);
Intrastate— calls within the same state;
Interstate— calls between two states;
IntraMTA— calls within MTA (Major Trading Area);
InterMTA— calls between 2 MTAs (Major Trading Area);
local— calling within your local exchange.
If your vendor sends you rates for tag combinations, you will need to set them in separate Traffic Processing rules. You can specify tag combinations like
interstate-intraLATA, interLATA-intrastate, etc. in the field Add Tag while creating a Traffic Processing rule.
Although, starting from JeraSoft Billing v.3.22.0, the system automatically connects 'interLATA/intraLATA'-type tags to paired tags, adding 3 tags in total to every defined state or lata.
Please ensure the Jurisdictional Manager from System Services is working.
For more information about getting this Module please contact with JeraSoft Support Team.