Tariscope Version History
Version | Database version | Date | Changes |
4.6.5 | 235 | 16.09.2024 |
1. An icon for importing new prices for services from an Excel file has been added to the "Services" page. This feature is relevant only for Tariscope Provider users, and it allows you to quickly add new prices for many services. |
4.6.5 | 235 | 16.08.2024 | 1. Changes have been made to the MD 110 parser. If for a call with Condition Code = 'I' there is no information about the route by which this call was made, a conditional 0-route is automatically created. Also, for a call with Condition Code = 'I', the fields NumberA and NumberB were changed places. 2. Changes have been made to the Avaya parser (Definity, Aura). Fixed a bug where the first CDRs were not handled correctly on a new day when the call date and time is the end of the call and the calculated start date of the call should be the previous day. Before this change, the start date of the call corresponded to the end date. |
4.6.5 | 235 | 06.08.2024 |
1. Changes have been made to the Asterisk parser. If the dialed phone number contains characters that are other ones than numbers, they are deleted. This allows you to correctly process calls, for example, to voice mail. |
4.6.5 | 235 | 13.06.2024 |
1. This update may only be relevant for Tariscope Provider users. When adding a new subscriber manually, if he is not assigned the value of a personal number, then the personal number will be equal to the subscriber ID (ID). |
4.6.5 | 235 | 11.06.2024 |
1. Improved parser for Unify OpenScape Business (Mitel). This may be relevant for Tariscope Provider users. Previously, CDR data from this PBX was processed, which was separated by a '|' separator. Now CDR data is also processed, where there is no separator between the fields. |
4.6.5 | 235 | 28.05.2024 |
1. Improved parser for Unify OpenScape Business X. In previous versions, it processed CDR records of Compressed format, which contained the symbol "|" to separate the fields. |
4.6.5 | 235 | 02.05.2024 |
1. Fixed an error that occurred when opening the subscriber's Personal account. |
4.6.5 | 235 | 23.04.2024 |
1. Fixed a bug where filtering options were not applied correctly in a call view created by a non-Tariscope admin user. |
4.6.5 | 234 | 14.03.2024 |
1. Parser for SBC (Ribbon Communications) was updated. If the SBC in the Radius attribute of NET-Calling-Number does not contain an extension, but it is present in the SIP address of the packet with Radius attributes, then Tariscope uses the extension from the SIP address instead of the value of the NET-Calling-Number attribute. |
4.6.5 | 234 | 01.02.2024 |
1. The Radius Accounting server in Tariscope Observer sends the Accounting-Response packet immediately after receiving the Accounting-Request packet from the Radius Accounting client. Previously, such sending was performed after some data processing, which could lead to disconnection of the client, which thought that there was no response. |
4.6.5 | 234 | 04.01.2024 | 1. Fixed an error that occurred when exporting a view for services to an external file, if the Personal Account field was not selected for display. |
4.6.5 | 234 | 21.12.2023 |
New features and fixes |
4.6.4 | 233 | 27.11.2023 |
1. A new Tariscope database updates (233) have been created, which includes: |
4.6.4 | 232 | 27.10.2023 | 1. A new database update (232) was created, which allows you to avoid the removal of tax charges when transferring phone numbers from one subscriber to another. 2. Added a new data source, Radius Accounting Server, which currently can only work with the SBC (Ribbon Communications) parser. If you have phone systems that pass CDR data through the Radius accounting server and would like it to work in Tariscope, please contact our support team. 3. Fixed an error in working with Hotel systems. Also fixed script for interaction with PMS Opera. 4. Changes were made to the report forms: Subscriber-expenses-per-month.rdl and subscriber-expenses-per-day.rdl. In previous reporting forms, confusing results could occur if Tariscope had been used for more than 5 years. To install updated forms of reports, before installing Tariscope, you should delete existing these forms of reports located in the folder C:\ProgramData\Tariscope\Reports\en (or ua or ru)\Generalized |
4.6.4 | 231 | 25.09.2023 | 1. Changes have been made to the SI3000 parser, which allows you to avoid some freezes in its operation when processing some informational elements of AMA files. |
4.6.4 | 231 | 22.09.2023 |
1. Added the 231 database update. It changes the data type of the TxPackets and RxPackets fields of the CallsSI table from INT to BIGINT. The CallsSI table is used to store all fields from the AMA files of the SI3000. Accordingly, this update may be relevant only for users with PBX of this type. |
4.6.4 | 230 | 18.09.2023 |
1. Added the 229_230 database update. It includes the changes in the ab_engine_gettelephone procedure. With some system settings, the error: "Cannot add call: exception: Violation of PRIMARY KEY constraint 'PK_TelephonesNewCache' could occur". |
4.6.4 | 229 | 24.08.2023 | 1. Fixed an error ("Error converting data type bigint to int") that could occur when processing CDR data from any telephone systems. The error occurred when the call ID exceeded the maximum value of type INT. A bug fix was made in the ab_engine_tariffcall stored procedure. 2. Fixed an error ("Cannot insert the value NULL into column 'ProviderID") that could occur during CDR data processing in the ab_engine_gettelephone stored procedure. |
4.6.4 | 228 | 04.08.2023 |
1. The function of importing non-working (damaged) DNs (extensions) from an external file into the Tariscope database has been added. During import, recalculation is automatically performed periodic services that are tied to these DNs. |
4.6.4 | 227 | 10.07.2023 |
1. Fixed a parser error for SI3000 (Iskratel): “ThrowKeyNotFoundException exception: The given key 'CallReleaseCause' was not present in the dictionary” that could appear in call records of AMA files containing 30 minute parts of a call lasted more than 30 minutes. |
4.6.4 | 227 | 05.07.2023 |
1. Improved operation of transferring phone numbers from one subscriber to another. The date specified by the user is the date from which the phone numbers belong to the new subscriber. For the subscriber from whom the phone numbers are transferred, the date of termination of validity of the numbers is the previous date. Added the possibility of entering separate comments for the first and second subscribers, which are added to the description of phone numbers and to the services that are linked to these numbers. |
4.6.4 | 226 | 30.06.2023 |
1. New methods have been added to the Tariscope API, which are mostly intended for users of the Tariscope Provider, who are telecommunications service providers. |
4.6.3 | 226 | 11.06.2023 |
1. Added the ability to process phone numbers that are specified in E.164 format, starting with '+', in the Cisco Unified Communications Manager (CUCM) parser. |
4.6.3 | 226 | 19.05.2023 |
1. A new function has been added that may be useful to telecommunication service providers: a transfer of extensions (DNs or internal phone numbers) from one subscriber to another. Both extentions and services assigned to these extensions are transferred. Recalculation is performed for calls and periodic services, if they have been charged. Extensions can be transferred within the current month. |
4.6.3 | 225 | 18.04.2023 | 1. The option to fix the toolbar when scrolling the page has been added to the Rates page, which makes it easier to work with rates when there are a lot of them. |
4.6.3 | 225 | 13.04.2023 |
1. Fixed an error in the display of the "Subscribers" page, when the list of subscribers is not displayed without applying a tree or displaying subscribers by phone numbers. |
4.6.3 | 224 | 27.03.2023 | 1. Fixed a bug in views for services where these views for users with extended rights did not contain any information. When creating a new view for services, the selection of data by PBXs was changed to the selection of data by groups of subscribers. 2. In the window for editing the parameters of the subscriber's extension, the error of displaying the calendar when selecting the dates of connection or disconnection of the extension has been corrected. |
4.6.3 | 224 | 14.03.2023 |
1. The ability to specify a name with which an entry will be created in the personal accounts of subscribers when charging for calls has been added to the wizard for importing codes and tariffs. |
4.6.3 | 224 | 09.02.2023 | 1. Fixed an error related to the incorrect calculation of the subscriber's account balance at the end of the month when there are no charges for the month or payments. |
4.6.3 | 223 | 06.02.2023 |
1. Fixed an error that could occur on the Service page when saving the service cost due to date localization. |
4.6.3 | 222 | 01.02.2023 | 1. Fixed an error that could appear when the cost of the service was stored. |
4.6.3 | 222 | 12.12.2022 |
Master of import of telephone codes and rates System variables Script of subscriber restrivtion 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 |
4.6.2 | 221 | 28.08.2022 |
1. Improved import of phone codes (area and country codes) and rates to the Tariscope system from external files, for example, Excel format. |
4.6.2 | 221 | 11.08.2022 |
1. The Tariscope report forms for the following groups were completely redesigned: Generalized, Detailed, For telecom operators. Several old reporting forms have been removed; some new reporting forms have been added. Each report has a description and a picture with an example of how it looks. |
4.6.1 | 221 | 25.04.2022 |
1. Fixed errors when importing information about subscribers from 3CX to Tariscope. Previously, all subscribers were added, regardless of whether they were in the Tariscope database or not. For added subscribers, instead of a phone number, its ID from the 3CX database was added. |
4.6.1 | 221 | 18.02.2022 |
1. On the Reports page, the ability to download any form of an RDL report located in an arbitrary location on the computer has been added. In previous versions, report forms were loaded only from the default folder. |
4.6.1 | 221 | 11.02.2022 |
1. When exporting a SQL query, the query results continue to be displayed on the page. They disappeared in the previous build. |
4.6.1 | 221 | 02.02.2022 |
1. Added saving the history of calls information transferred to PMS Opera (Oracle). A new report form has been created that allows you to get data on the number and amounts of charges for calls transferred to the hotel system. |
4.6.0 | 219 | 04.01.2022 | 1. In Tariscope Tasks, due to the fact that with a large number of simultaneously generated reports, errors could appear, multithreading is temporarily disabled. |
4.6.0 | 219 | 28.12.2021 |
1. The parser for PBX Coral 6000 v16.8 with variable configuration of SMDR fields was added. |
4.6.0 | 219 | 20.12.2021 |
1. Fixed manual switching of the restriction status. Relevant for licenses with the restriction feature. |
4.6.0 | 219 | 07.12.2021 |
1. Added a new Observer script for the function of restricting individual subscribers on 3CX v18. |
4.6.0 | 218 | 25.11.2021 |
1. The import of information about subscribers' payments into Tariscope has been improved. Now, to associate a payment with a specific subscriber of the Tariscope system, the fields are used in the following priority order: subscriber ID, account ID, full name of the subscriber, his phone number (extension). |
4.6.0 | 217 | 22.11.2021 |
1. Added the ability to process CMR files from CUCM with separated fields for the originator and terminator of the call. |
4.6.0 | 216 | 17.11.2021 | 1. Due to the change in the API in 3CX version 18, changes have been made to the Online call monitoring mode. |
4.6.0 | 215 | 15.11.2021 |
1. Due to the change in the API in 3CX version 18, changes have been made to the Tariscope Observer script to implement the restriction feature. 2. Fixed a bug in the stored procedure related to the restriction feature. |
4.6.0 | 214 | 03.11.2021 |
1. Fixed bug related to using HTTPS. |
4.6 | 214 | 21.10.2021 |
1. Added the ability to enter email addresses ending with the "underscore" character. |
4.6 | 214 | 19.10.2021 | 1. Added obtaining SSL certificate for work over HTTPS from Windows storage. 2. Added import of Observer profiles from XML format for porting from version 4.5.x. In version 4.6, the Observer service profile is stored in json format. 3. The error of restoring the database backup has been fixed. 4. Fixed error displaying the processing time of the last call (last CDR file), as well as the real interval in the Observer table. |
4.6 | 213 | 05.10.2021 |
1. Linux support. The main feature of the new version of the Tariscope system is the ability to install it on servers with both Windows OS (Windows 10 or Windows Server 2019/2016) and Linux OS. Supported Linux versions include: Alpine, CentOS, Debian, Fedora, OpenSUSE, Red Hat, SLES, Ubuntu. All existing Tariscope users with warranty support can upgrade to the new version of Tariscope 4.6. |
4.5.5 | 212 | 18.08.2021 |
1. Changed the type of origSpan and destSpan fields of the CallsCCM table of the Tariscope database to bigint, because the int type was not enough for some CUCM users. The CallsCCM table is used to store all CDR fields from CUCM. |
4.5.5 | 211 | 27.07.2021 |
1. Added the ability to save a subscriber's login for access to a personal account using the active directory (AD), if the login does not match his email address. |
4.5.5 | 209 | 08.07.2021 |
Tariscope Personal Area Tariscope administrator views Bug fixes |
4.5.5 | 208 | 03.06.2021 | 1. Fixed a bug of the previous installation on 05/28/2021. There were no files for the Tariscope server in it. The problem may have occurred during a clean installation. |
4.5.5 | 208 | 28.05.2021 |
1. Fixed a bug related to a one-time charging of a daily service when periodic services are charged through the Tariscope Tasks. Now a daily service is charged for every day of the month. |
4.5.5 | 207 | 24.03.2021 | 1. Added the ability for Tariscope Tasks to save reports, using in any field of the Abonents table, for example, to display the account number of the subscriber in the file name, you must specify: %AccountId. |
4.5.5 | 207 | 26.02.2021 | 1. Fixed handling of active calls for 3CX and Asterisk. |
4.5.5 | 206 | 02.02.2021 |
1. In some cases, telecom operators schedule daily services, for example, only on working days. Therefore, such an ability was added in Tariscope to charge such services only on working days. |
4.5.5 | 205 | 27.01.2021 |
1. Added the ability for a subscriber to have any number of addresses. |
4.5.5 | 204 | 20.01.2021 |
1. Tariscope Personal Area is fully integrated into the Tariscope system. The interface of the Personal Area has been updated. The payment system in the Personal Area has been updated. |
4.5.4 | 203 | 21.12.2020 |
1. Added Tariscope API integration. It is an implementation of the REST API for integrating third-party applications with Tariscope. It may be relevant, for example, for telecom operators to receive data from Tariscope into the accounting system. |
4.5.4 | 202 | 15.12.2020 |
All additions and corrections of this release relate only to the Tariscope Personal Area. |
4.5.4 | 202 | 10.12.2020 |
1. Added the function of tracing the rating process of the selected call in the view for calls. This allows you to identify and then eliminate the causes of incorrect billing. |
4.5.4 | 201 | 30.11.2020 |
1. Added the ability to maintain the history of rate plans for subscribers and numbers/IP addresses, if rate plans are assigned for them (relevant only for the Tariscope Provider edition). |
4.5.4 | 199 | 12.11.2020 |
1. A new script has been added to the installation package, which allows to process information about calls and services from the csv file of the operator Lifecell (Ukraine). This may be relevant for users who have corporate mobile numbers from Lifecell. |
4.5.4 | 199 | 05.11.2020 |
1. A new report has been added to the Statistical reports group: Longest external calls. |
4.5.4 | 199 | 02.11.2020 |
1. Fixed editing of payment or charges for a month. |
4.5.4 | 198 | 12.10.2020 |
1. Added a new subsystem: Work order. It is intended for telecom operators using Tariscope Provider. Allows you to set tasks (work orders), monitor their implementation. |
4.5.3 | 197 | 01.10.2020 | 1. Tariscope could send many requests to the Tariscope website to get information about the current software version. This has now been fixed. |
4.5.3 | 197 |
22.09.2020 |
1. In the Tariscope Tasks, on the task page for generating a report, when you select 'Subscribers' or 'Groups' as the 'Source', a button has been added to clear previously selected subscribers or groups. |
4.5.3 | 197 | 17.09.2020 |
1. Fixed Tariscope operation when using prefixes. In some cases, they were not applied. |
4.5.3 | 195 | 27.08.2020 | 1. Fixed a bug related to the use of prefixes for the correct rating of calls. |
4.5.3 | 194 | 18.08.2020 |
1. When creating a new view in Tariscope, a selection of view fields was added, which allows you to immediately create a view with the desired set of fields and in the required order. Previously, all new views used a default list of fields, which could then be changed. |
4.5.3 | 194 | 14.08.2020 |
1. Added a new type of views: Рrovider summary view. This view is intended primarily for telecom operators, providing them with information for any period necessary for mutual settlements. |
4.5.3 | 193 | 10.08.2020 |
1. Added the page notifying that the Tariscope system server (TSMAIN service) is not working. In previous versions, there was no such notification, which did not allow the user to independently deal with the problem. |
4.5.3 | 192 | 24.07.2020 |
1. Added a fraud detection subsystem, SoftPI Guardian, which includes the "Analysis by Direction" component. The subsystem is supplied as an optional feature. It is not included in the base license. |
4.5.3 | 191 | 16.07.2020 |
1. Added the Tariscope Watchdog subsystem for tracking the receipt of information about calls (CDR) from PBX based on the model of calls. A notification is sent to the administrator if new call information is missing for more than the predicted time period. |
4.5.3 | 190 | 26.06.2020 |
1. For users of the Tariscope Provider edition, the ability to predict the amount of month charges to the customer using artificial intelligence has been added. |
4.5.2 | 189 | 24.06.2020 |
1. To the Alcatel OmniPCX Enterprise (OXE) settings the Extended duration information switch was added. It allows you to use different duration fields from the CDR file. When the switch is disabled, the Duration field is used, which includes the call duration of the call and ring duration. When the switch is enabled, the EffectiveCallDuration field is used, which includes only the call duration. Depending on whether your CDR has data in the EffectiveCallDuration field, you should enable or disable this switch. |
4.5.2 | 189 | 19.06.2020 | Fixed a bug related to license parameters. |
4.5.2 | 189 | 16.06.2020 |
1. When creating a new call view to set data filtering options, the possibility of multiple choice for the call source and call purpose has been added: |
4.5.2 | 189 | 12.06.2020 |
1. Two new widgets have been added to the dashboard: Request to database (tabular) and Call statistics+. |
4.5.2 | 189 | 29.05.2020 | 1. In the Chrome browser, starting with version 83, and other browsers running on its engine, when the Tariscope pages were opened, the page can be distorted. This has been fixed in the current version. |
4.5.2 | 189 | 20.05.2020 |
1. Added support for HTTPS. Tariscope can work both over HTTP and over HTTPS. |
4.5.2 | 189 | 05.05.2020 |
1. A new type of task has been added to the Tariscope Tasks: a group of tasks. Tariscope Tasks performs tasks by the group in the order of their assignment. Various options for task groups are possible: |
4.5.2 | 188 | 24.04.2020 |
1. Added the script, fraud.vb, to detect the fraud. |
4.5.2 | 188 | 21.04.2020 |
1. Added the ability to set the folder location for temporary Tariscope files. Previously individual clients may have had problems with certain operating modes, for example, exporting data to Excel, if they did not have administrator rights to this folder. Now the user can change the location of the folder to the place where he is guaranteed to have access rights. To set the location of this folder, select Advanced options → Database info → "Tariscope temp folder" button on the toolbar. |
4.5.2 | 188 | 15.04.2020 |
1. Fixed a dialog box for setting the order and visibility of fields to display in views. Previously, the order of the fields was not saved when you re-open this dialog box. |
4.5.1 | 187 | 10.04.2020 |
1. Added the ability to easily identify calls between subscribers of different PBXs of the user. You can assign the following call types for such calls: internal, corporate or any others. |
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. |
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. |
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: |
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. |