JeraSoft Documentation Portal
Docs for all releases
JeraSoft Development is proud to announce a new major release of VCS v3.17.0. A focus of the latest version has been set primarily to rework and improve system functionality; however, a range of new features has been introduced to the system as well. The full list of changes is as follows:
In this version, a range of improvements has been implemented in the Rate Tables section:
Now, while adding a new rate for a target destination code, user can specify a Source Code and/or Source Code Name to make rate table customization even more agile and deliberate.
Screenshot: Src Code/Code Name
A detailed information about new rate table features can be found in the respective articles of the Rate Tables section of Jerasoft User Guide.
Starting from v3.17.0, VCS users can configure a CDR files and RADIUS / SIP Redirect Integration with FreeSWITCH v1.6 platform. Previously, there was a possibility to integrate only with FreeSWITCH v1.2 platform. More details about integration with FreeSWITCH can be found in the Jerasoft Integration Manual article.
As we've mentioned earlier, in VCS v3.16.0, a before type of Provisioning API handler was deprecated. With a release of a new version, it has been completely removed from the system. With a migration to a new version, all client's handlers with before type will be renamed to BEFORE:<handler name> (e.g. BEFORE:Extra handler) and their statuses will be changed to disabled. We highly advise all our customers to check if there are any before type handlers in their Provisioning API section. If such are present, we recommend to use staging system to test its integration prior to upgrading a production system.
The list of Client Portal changes includes the following:
Two additional columns: Origin and Src number have been added to Usage History: Detailed report. Moreover, the display of these columns can be configured manually in app-params.php, located in /opt/jerasoft/vcs/portal-backend/config/ folder. For instance, if you wish to remove Origin column from the report, simply delete 'origin' value from array for 'additionalColumns' key. In the same way, you can remove Src number column or both.Screenshot: Origin and Src number columns
A new feature, introduced to Traffic Processing section, implies a possibility to choose whether Src Party ID, Dst Party ID or both will be used for LNP dipping. User can specify it in LNP Direction field in case a target database is specified in LNP/MNP field.
Screenshot: LNP Direction field
As a part of the integration with TJA LNP database, in addition to current TJA (Routing Number) collector that changes Dst Party ID during the LNP dip, a new TJA (Owner) collector has been added. Instead of changing Dst Party ID, the new collector assigns the operator's name as a tag to the call during the LNP dip.
Screenshot: TJA (Owner)
Previously, while configuring Files Collector for a target gateway in Gateways section, you had to specify an exact path in From Path field. For instance, there are /var/cdrs folder with the latest CDR files and /var/archive_cdrs/ folder with outdated ones. If user needs to download CDR files from both folders, he can use ; (semicolon) to separate paths or /**/ for recursive download. New paths may have the following look: /var/cdrs/**/bill*; /var/archive_cdrs/bill*.
Screenshot: From Path field