Tariscope System Version History

Version	Database version	Date	Changes
4.5.1	186	02.03.2020	1. Added the ability to specify the priority for queries in the RDL report (using the Timeout field). The default value is 0. It is the lowest priority. In separate reports, there is a need for database queries to be executed in a specific order. 2. Added logging of requests to the Kestrel server where Tariscope is running. The log is located in the folder: C: \ ProgramData \ Tariscope \ Kestrel By default, logging is enabled. The period for creating a new log is set in the Tariscope Start program. 3. Added the ability to keep relationships between a specific charged service and invoice where the service was included. For the case when you need to recreate an invoice, added buttons to delete invoice numbers for all subscribers, one subscriber, one service, one invoice. 4. Fixed localization in the Tariscope Personal Area. 5. Fixed a bug in the Tariscope Personal Area when opening the configuration file (WebConfig) after reinstalling the Personal Area. 6. The replacement of the configuration file of the Tariscope Personal Area with the default one when reinstalling or updating the account has been fixed.
4.5.1	185	25.02.2020	1. For SSH and SFTP client data sources of the Tariscope Observer, support has been added for the authorization method - Keyboard Interactive Authentication. It may be useful for obtaining CDR data from Avaya Aura. 2. In the CDR field settings for Avaya Aura (S8xxx, Definity), Alcatel OmniPCX Office and Siemens Hipath 4000, for convenience, the fields are sorted by parameters: Enable / Disable and the first position of the field. 3. If the computer with Tariscope does not have an Internet connection, an icon appears on the Tariscope toolbar. Clicking on the icon leads to the message that you can not use the online functions of Tariscope.
4.5.1	185	07.02.2020	1. A new widget has been developed that allows you to monitor the current status of Tariscope Observer services. 2. A new integration was added to Tariscope. A CDR file from a 3CX Phone System provides calls information on a transfer call in one line with a total call duration for all its participants. Such information does not allow you to analyze how much each of the participants of the transfer call spoke with the subscriber. Now Tariscope system can receive such data from 3CX that provides complete information about transfer calls. 3. Fixed some errors in localization. 4. Fixed widget settings for missed calls. 5. The error related to the configuration of route parameters has been fixed. It was not possible to reset the access code for the route. 6. The function of converting time to local for the 3CX parser has been fixed. Previously, it was always turned on, and user settings were ignored.
4.5.1	185	29.01.2020	1. Added the ability to set the number of services when charging a one-time service. Previously, we could add only one one-time services or a total amount for several services. 2. In the service view, a display of the number of charged services is added. Previously, only minutes were displayed for a specific call direction. 3. Added saving the number of charged periodic and one-time services to the Tariscope database. 4. Added a new widget that displays statistics of missed calls. Various display forms of this widget are supported: - Pie chart. - Text mode. - Only received calls. - Only missed calls. 5. An informational message was added to the last calls page in the Tariscope Observer, which allows you to quickly go to the views page to get information about all the required calls, not just the last ones. 6. Fixed bug when receiving a list of Observers and active calls for Asterisk if the Tariscope database is installed on a remote server. 7. Report generation fixed. Previously, if the report had an optional parameter, the subscriber ID, and it was not set, then the report was not generated.
4.5.1	184	27.01.2020	1. Tariscope Observer Remote Services Server and a system for working with it were added. Remote Tariscope Observers can be located on any PC running Windows 10, 8.1, 8, Server 2016, 2019, which has a connection with the PC where Tariscope Web Administrator was installed. The following modes of work with the Remote Observer have been created: - settings - setup scripts - start / stop - create / delete / rename - log download - list of recent calls. 2. Added the ability to enter any serial port number for the data source of Observer service. 3. Added a message that appears if the report has not been generated. Previously, the 404 page was appeared. 4. A new widget was added that allows you to display the resource usage by Tariscope applications. In simple mode, the widget only displays the resource usage by Tariscope applications. In advanced mode, it displays the resource usage by Tariscope applications with other software running on the server. 5. The script for processing CDR data received from the operator Bandwidth.com (USA) was updated. 6. Added support of paper sizes from A0 to A10 for manual generation in rdl reports. 7. Added a link to SoftPI's LinkedIn page. 8. Added a link to the Tariscope software update history page on the site. 9. Fixed an export of telecom providers' settings to an external file. 10. Improved interface for: 10.1. subscribers and their numbers so that the toolbar is always visible when scrolling. 10.2. subscriber documents. New subscriber documents are always displayed on top (the list is displayed from new to old). 11. Fixed the display of the last processed calls by Observer. Previously, the first 50 calls were sometimes shown, instead of the latest 50 calls. 12. In the Tariscope Tasks, an information window was added for the report generation task. It contains a description of the parameters which are used for the name of the report. 13. Fixed some errors in localization. 14. Fixed the reaction to clicking icons on the toolbar when viewing the Observer log. Earlier, when clicking on some of the icons, a request was sent to start the Observer service. 15. Fixed the work with routes and gateways. Previously, an application could stop working if an telecom provider that was deleted was assigned to a route (gateway). 16. The problem with charging one-time services has been fixed. Previously, if the description of the service was not indicated, then the service was not charged. 17. Fixed the hanging up the Tariscope Web Administrator application when deleting large nodes. 18. Fixed the process for deleting telecom providers from Tariscope.
4.5	183	10.01.2020	1. Fixed bug when creating a new service if the number of taxes in the Tariscope system was more than 1000. 2. Fixed bug with receiving files via FTP. Previously, the date of the received files did not contain a year, as a result of which at the beginning of the year the last year’s files could be re-processed with the date of the current year. 3. Fixed bug with call duration for Alcatel-Lucent OXE. Before, the duration of calls also included the ring time. 4. Fixed bug with updating subscribers' data during rerating. Data was not updated if rating parameters were not configured. 5. Fixed display of the Tariscope database size in the widget of the dashboard. At times, the 0th value of the Tariscope database was displayed. 6. Fixed password recovery for the Tariscope Personal Area. 7. Fixed bug with incorrect search for phone codes. 8. Information has been added on the About page. Added system requirements, contacts and links. 9. The list of widgets displayed on the dashboard is sorted alphabetically. 10. The Tariscope database was updated to the version of 183.