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


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:

Major Updates

Rate Tables

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

    (warning)   Attention

    Please note that rates with Src Codes are not used when termination tariffs are chosen for Dynamic Routing. This functionality is going to be reworked in the upcoming releases.

  • Introduction of Src Code/Code Name columns led to an expansion of rate table parameters, namely adding Src Code Deck field. Now, user can assign Src Code Deck and Dst Code Deck separately.
    Screenshot: Rate Table parameters
  • Additional settings that have been introduced to importing process now allow users to set billing increment, remove dash, split source code name and update code deck:
    1. Billing Incrementbilling increment defines the way events are billed and can include two parameters: minimum volume and tariffication interval or three parameters: minimum volume, tariffication interval and grace volume. In this field, you select from a drop-down list of predefined variants the order these parameters are recognized by the system during import.
      Screenshot: Billing Increment

    2. Remove Dash - if enabled, this field determines that a dash in codes, written as 1201-1205, will be removed and these codes will be imported as a single 12011205 code. Otherwise, they will be imported as separate 1201, 1202, 1203, 1204, 1205 codes.
    3. Split Src Code Name - this option is used only in case source code names contain underscore symbol. If you select By underscore value, USA_Ohio Src Code Name will be imported as Ohio. Otherwise, the whole name will be preserved during import.
      Screenshot: Remove Dash and Split Src Code Name

    4. Update Code Deck - select the way you want both Src and Dst Code Decks to be updated with new/existing code names from current import file.
      Screenshot:Update Code Deck


  • Moreover, users can specify a type for each sheet of the import file. 
    Screenshot: Sheet type

A detailed information about new rate table features can be found in the respective articles of the Rate Tables section of Jerasoft User Guide.

FreeSWITCH v1.6 Integration

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.


Minor Updates

Provisioning API 

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.

Client Portal

The list of Client Portal changes includes the following:

  • Previously, on Payments History page, user could view history of both payments and charges. Now, there are separate pagesPayments History and Charges Historyfor each type of transactions.
    Screenshot: Payments History


    Screenshot: Charges History



  • customer-params.json.sample in /opt/jerasoft/vcs/portal-backend/config/ folder has been renamed to customer-params.default.json. Currently, default values for Client Panel are taken from customer-params.default.json, while customer values - from customer-params.json, as it was in previous versions. However, in case both files have identical keys, values from customer-params.json will be used.

  • If Refill Balance page is missing in Billing & Payments section of your Client Panel, it is due to one of the following reasons:
    1. A role, assigned to a user, lacks permits to read this page;
    2. This page is restricted by VCS license;
    3. No payment gateway has been configured for target reseller in Payment Gateways section.

  • 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
     

Traffic Processing

A new feature, introduced to Traffic Processing section, implies a possibility to choose whether Src Party IDDst 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

Number Portability

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)

(warning)   Attention

Please note that LNP update file format of TJA (Owner) collector differs from that of TJA (RN).

Gateways

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



  • No labels