New version of Tariscope 4.6.3

Ми повстанем з руїн, як і сонце стає після ночі,
згине морок московії наче в поганому сні,
і розквітне земля, і засвітяться очі дівочі,
і польються країною нашою наші пісні.

SoftPI is pleased to announce the release of a new version of the billing system of Tariscope 4.6.3. This version contains all the updates that were made during July - December 2022 for version 4.6.2, as well as some fixes.

Master of import of telephone codes and rates

The phone codes and rates import wizard allows you to import into the Tariscope database the phone codes and rates that are used to charge for phone calls made. This wizard has been around for a long time in Tariscope. But several new features have been added to it.

1. Added currency selection to be applied to rates (Figure 1) that are imported. Previously, the default was the currency that was set as the primary currency. But rates in some countries, in that case also in Ukraine, for international calls, as a rule, are set in US dollars. Accordingly, previously, after importing tariffs, it was necessary to change the currency for all international telephone codes. Now it is enough to select the necessary currency in the import wizard.
2. Added rate plan selection (Figure 1) for which rates are imported. As Tariscope users know, the same rate can have different costs for different rate plans. This application allows you to immediately set the desired rate plan for all imported rates.
3. Added selection of call cost rounding (Figure 1), which is used in rates. Previously, the default was rounding to minutes, which is used in most countries. But in Ukraine, the call is rounded to the second. This is the current default choice, but you can change it during the setup wizard if necessary.
4. Fixed the calculation of updated rates after import. In the previous version, the number was specified, which was equal to the number of phone codes being imported. Now, if the same rate is used for several codes, it is counted as one added.
5. The rate update date has been fixed. Previously, the wrong value was used in a number of cases.

Figure 1

Synchronization with Active Directory

1. In the Tariscope system, there has long been the possibility of receiving data about subscribers from the Active Directory. To do this, a Tariscope database synchronization profile with Active Directory was created, where the synchronization parameters were specified. But there was no possibility to adjust these parameters. This capability has now been added (Figure 2), which simplifies the administration of the Tariscope system.
2. In previous versions of Tariscope, only standard attributes could be imported from AD. Tariscope 4.6.3 added the ability to import any additional attributes created by the AD administrator. For this, their list should be added to the AdditionalADAttributes system variable. This makes it possible, for example, to create attributes for the connection and disconnection dates of an employee and import them into the corresponding fields of the Tariscope database.
3. Added the ability to import the cn attribute into any Tariscope database fields. In previous versions, this attribute could only be imported to the FullName field of the Tariscope database.
4. Fixed import of some standard attributes that were not stored in the Tariscope database before.

Figure 2

Subscriber search

For the Subscribers page, which displays a tree of subscribers, the possibility of searching for a subscriber by any of his numbers has been added. In previous versions, the search among phone numbers was performed only by the main phone number. This possibility may be relevant for telecommunication operators, where subscribers have a large number of telephone numbers.

Reports

1. Reworked reports from the General, Detailed, Provider groups. In previous versions of RDL reports, it was not taken into account that the report parameter, which had the DateTime format, was displayed in UTC format in the report. Therefore, for example, the filter overlay in the report for a certain period was shifted to the time zone value. To install the updated reports of this version, you must remove any reports that you did not develop yourself, and then install version 4.6.3. If you have developed RDL reports yourself that contain a DateTime parameter, you should check whether the time zone is taken into account for these parameters.
2. Fixed an error when configuring report settings. Previously, the parameters of the report margins, its orientation and size were not saved. Now, when configuring the parameters of a new report, the parameters of the margins, the orientation of the report, and its size are automatically substituted. These parameters are also stored in the user's cookies. Accordingly, if cookies are disabled, this function will not work.

System variables

1. When creating a system variable, the Description field has been added where you can specify its purpose.
2. Added the ability to edit system variables.
3. Added system variable of AdditionalADAttributes to enter a list of AD attributes added by the user.

Script of subscriber restriction for Observer

Updated script for restricting subscribers for the Avaya PBX using the SSH protocol (setcos-avaya-ssh.cs). The restriction function works only for those users who have it included in the license.

Routes and gateways

An error related to the removal of the value from the Access Code position of the Transit Call Rates window, which is called from the Routes and Gateways page, has been fixed. The error was due to the fact that the deletion was not saved.

Update 222 Tariscope database

1. Added the SecondsToTimeFormat function used in some RDL report forms. It is intended for counting seconds in the format HH:MM:SS.
2. Added the AdditionalADAttributes value for the Key field of the Settings table.
3. The description field is added to the ab_saveproperty stored procedure.
4. Added the description parameter for the ab_mc_setmaincurrency stored procedure when calling the ab_saveproperty procedure.
5. Added the TimeZoneAdd function, which converts a date from UTC time to local time, taking into account the time zone. This function should be used for DateTime parameters in RDL report forms because they use UTC time.

Update to Tariscope 4.6.3

The new version of Tariscope 4.6.3 is available to all users of the Tariscope system who have warranty (technical) support.

Users whose warranty (technical) support period has expired must purchase either technical support or an upgrade of the system version to use Tariscope 4.6.3. Both options are equivalent in features and price.

The price of the Tariscope 4.6.3 system remains the same as the price of the Tariscope 4.6.2.