Release 3.28

JeraSoft presents a major release of JeraSoft Billing 3.28 introducing new features and functional improvements. Please find a complete revision list below.

Major updates

Origin based rates

Following growing market demand, we have implemented a significant improvement to how our system processes Origin-based rates (OBR). Starting from the v3.28 of JeraSoft Billing, you will be able to process rate files that contain "Origins" and import OBR a lot easier than before. Moreover, with the current approach, the system will save space in your Rate Tables when importing such Rates.

Origins & Origin Decks

In the scope of this improvement, we have introduced a new entity to the system – Origin Decks. It is located in the Configuration drop-down menu.

An Origin Deck is a set of Origins that include one or several prefixes. Different prefixes (codes) can be present in several Origins at the same time. Origins are an essential entity in the new OBR approach. Currently, you can populate your Origin Decks manually or via Rates Import.

You can find more detailed information on Origin Decks management in the Origin Decks guide.

note

Origins are cached. After creating, updating, deleting, or importing origins, the Cache Manager should be restarted to apply the changes, so that origins will be used during the identification or routing.

OBR Rates in the system

All of the daily rate management tasks support Rates with defined Origins:

1. You can assign an Origin Deck to the Rate Table.
2. You can manually add Rates with defined Origin.
3. You can filter Rates list by Origin Names.
4. You can export filtered Rates with the ability to add separate sheets with OBR and Origins.
5. You can notify customers about OBR changes – the Rates Notification tab in Reseller settings supports adding separate sheets with OBR and Origins to a rate file.
6. You can import rate files with Origins both within a rates sheet and from a separate sheet. Import process is the same as for Codes: by using "Update Deck" option in the Advanced Import settings for Origin Decks.
7. You can use Rates Simulation tool for OBR: if Src Party ID is set, Rates are matched by Origin. If none are found, regular rates (without specified origin) are shown.
8. You can query Summary Report, Orig-Term Report, and xDRs Report filtering and/or grouping by Origin Name.

note

Currently, the OBR will not be processed in Rates Generator and Rates Analysis.

Call flow adjustments

The rate identification and routing decision stages of call processing have been adjusted taking into account OBR. Here are some important things to note:

1. OBR Rates have a higher priority than regular Rates.
2. If there are OBR Rates for a specific destination, regular Rates will never apply.
3. Unlike the source codes, all matching origins will be used during call identification regardless of the match length. For example, assuming you have origins “44” and “442” defined, the number “442031299126” will match both of them.

API comparison tool

We continue improving our API reference making sure each new update goes smooth. With v3.28 we are adding a convenient tool to quickly review changes between API versions. The output will provide a comparison view, including new or removed endpoints as well as changes in the existing ones. The tool supports API versions as of v3.27.

Rerating

By popular demand, we have added a new Rerating Queue section to the Rerating interface with detailed process status. This new section provides insights on the progress of the scheduled rerating requests, as well as some other additional info.

Active Sessions

After aligning the Active Sessions report with the unified system framework, it became visually different from the previous versions' interface, which has introduced delays in monitoring for some cases. To overcome this, we have provided our users with more control over how the report is built.

A new field was added to the Output section of the query settings block: "Details". With this new functionality, you can have additional columns in your report ("Info", "Originator details", "Terminator details", "Orig Src Party ID", "Orig Dst Party ID", "Term Src Party ID", "Term Dst Party ID"). They will be used for grouping (just like "Group By" columns), but behave like regular output columns.

Minor updates

Report Queries

To simplify Report Queries management, we have reworked how they are visible and editable by different Users in the system. The Visibility setting has been removed. The updated logic is the following:

User type	Read	Write
Users wo/Reseller limit	Any Report Query	Any Report Query
Supervisors (w/Reseller limit)	Own + same/child Resellers	Own + same/child Resellers
Users w/Reseller limit	Own + same Reseller	Own only

You can read more on this in the User Guide.

note

1. Reports execution using Report Queries in GUI will fetch data according to the permissions of a User who queries the report, not according to the Report Queries’ owner.

2. When sending reports to email and using Monitoring, all recipients will receive the same data (according to the permissions of the Report Query’s owner).

The Report Query's owner will be the User who created it.

Subscriptions

For bulk Subscriptions management, we have added Mass Edit option with the following actions:

• Delete - remove selected Subscriptions (only inactive Subscriptions can be deleted)
• Stop renewal - stop renewal at the end of current period, today, immediately, or on a specific date

Client's capacity

To extend our capacity control functionality, we have added the Total Capacity limit that combines inbound and outbound capacity for a Client:

Accounts

Src Party ID control

We have added an ability to control Src Party ID used during calls origination based on DIDs owned by a customer. Specifically, we allow to:

1. Reject a call if Src Party ID doesn't belong to the customer;
2. Overwrite Src Party ID to the one owned by a customer;
3. Allow calls with any Src Party ID.

Routing to vendors' IP

We now allow ANI-identified termination Accounts to be included in the routing with a specific vendor's IP.

A new field was added to the Accounts settings for termination: "Routing IP". The IP address specified here would be used in the routing responses from the billing system to the equipment.

This way you can have multiple ANI-identified Accounts with the same routing IP.

Tax providers - Compliance Solutions

To expand our exemption capabilities for Compliance Solutions, we have added support for full list of exemption options according to the tax engine documentation. You can now select the needed exemption from the list in the Taxes Profile settings:

Please review our User Guide for full list of exemption codes.

Invoice Templates

We have reviewed the full list of Invoice variables to align their namings with the typical accounting terms. You can check the updated variables in the Invoice Template PDF form.

Number Portability

The "JeraSoft LNP Common" collector has been reworked to support the Routing Number (RN).

Traffic Processing

In line with making LNP processing more versatile, we have added the LNP Actions block to Traffic Processing Rules.

With the help of this functionality, you can define, which actions should be applied to an event after LNP dipping. The system can:

• Add an Owner as a tag to the event;
• Prepend a Prefix to the selected LNP Party ID;
• Replace LNP Party ID with a Routing Number.

Rates

To enhance daily Rates management, we have restricted ordering possibilities. From now on, you can order the Rates list only after the Rate Table is selected.

Rate import files cleaning

We have added the possibility to control the rate import files cleaning process separately. Use the "Delete imported files after" setting in the Settings section of the system to specify when these files will be removed. The default is "345 days".

Events Log

The identification error messages from Calculator service have been reworked to display more useful data for further analysis. You can access full list of parameters by clicking the button.

Statistics Manager

We have improved the statistics packages processing while restoring old statistics in the system.

DID Management

Following the addition of Custom Fields for DIDs, we have improved the speed of exporting DIDs when using custom fields.

Deprecations

Additive Rates

The Additive rate policy is marked as DEPRECATED and will be fully removed in the next release.