Tariscope Version History

1. For the restriction function in Tariscope with 3CX v20, programs have been developed for Windows and Linux.
2. 4 new methods have been added to the Tariscope API: tariffs.plans, tariffs.details, tariffs.time and services.list.
3. New forms of statistical reports have been added:
3.1. Daily costs of a subscriber.
3.2. Daily costs of a group of subscribers.
3.3. Daily costs of a PBX.
3.4. Daily costs of a communication node.
4. The Tariscope database has been updated to version 236. The update applies to the BankAccount field in the Abonents table, as well as the stored procedures ab_engine_limiting_clearabonentdebit and ab_engine_limiting_clearalldebit.
5. Fixed the transfer of time from the calendar box when specifying the date and time of the report form.
6. All report forms have been redesigned. To install them in the system, you must delete the previous report forms before installation.
7. Added a more convenient display of the results of searching for subscribers by their extension.
8. Fixed an error in the PBX Creation Wizard.
9. Modified the parser for Unify OpenScape Business X.
A detailed description of the new Tariscope version 4.6.7 can be found in the article.

 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.
2. Fixed an error in CDR processing from Unify OpenScape Business, where the CDR field separator '|' is used. No CDR records were processed if their length was less than 80 characters. CDR records longer than 50 characters are now processed.
3. Fixed an error that could occur when updating the Subscribers page after importing information about damaged phone numbers. The error was due to double saving of imported data.

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.
2. Changes have been made to the Avaya Aura parser. Due to the lack of information in the CDR about the route through which the outgoing unanswered call was made the call parameters were incorrectly determined. Now this problem is solved.

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).
In previous versions, in such cases, the personal number (AccountId) had the value NULL, which could affect, for example, the export of a view for services.

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.
2. Due to the change in the format of call data from Kyivstar, the script that imports this information into the Tariscope database has been changed. The new script is called “Kyivstar-2024.cs”.
3. The mode of manual input of information about payments from subscribers in Tariscope has been changed. Previously, if a subscriber did not have a phone number or IP address (the FirstDN field was NULL), this subscriber was not included in the list when searching for subscribers for data entry. Now all subscribers are displayed.

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.
CDR records that do not have this symbol are still being processed.

1. Fixed an error that occurred when opening the subscriber's Personal account.
2. Improved operation of the parser for the Unify OpenScape Voice (OSV). The definition of the value of the fields Originator and Terminator of the call has been changed.

1. Fixed a bug where filtering options were not applied correctly in a call view created by a non-Tariscope admin user.
2. The settings of the Notifications and mailing page has been improved, which allows you to use the e-mail address specified there to send e-mails, when, for example, the e-mail address for sending is not specified in the script. If, for example, an e-mail address is specified in the script, then the mailing will be to this address, as well as to the e-mail address specified in the settings of the Notifications and mailing page.
3. Sorting by the From field has been added to the ab_mc_dnplanedetails stored procedure. This allows the user to see the data sorted on the Numbering plan page by the "From" field.
4. Updated some third-party DLLs that had vulnerabilities.

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.
2. Fixed an error that occurred when opening the subscriber's settings page, if this subscriber had one of his DNs previously marked as damaged, and later the DN was disconnected.
3. Changed the time from 00:00:00 to 23:59:59 in the date of disconnection of the subscriber, extensions and services assigned to the subscriber. This time (00:00:00) did not affect the correctness of the billing of services to the subscriber, but it did affect the calculation of the cost of calls on this day.
4. Fixed a bug where filtering options were not being implemented correctly in a call view created by a user who is not a Tariscope administrator.

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.
2. Fixed an error that occurred when importing information about damaged DNs (extensions), if the list of such DNs contained a DN that did not exist in the Tariscope database. All DNs that followed a non-existent DN were not imported.

New features and fixes
1. Import from an external file of simultaneous charging of one-time services to subscribers.
2. Import from an external file of non-working phone numbers
3.New forms of reports for communication operators
4. НNew forms of reports for communication operators
5. New parser for receiving CDRs from SBC (Ribbon Communications)
6. New parser for receiving CDRs from Terratel voice gateways
7. Saving Tariscope presets for working with an SSL certificate
8. Fixed toolbar when scrolling
9. Changing the subscriber ID field to the personal account ID
Read more in the article.

1. A new Tariscope database updates (233) have been created, which includes:
1.1. Creation of the CallSessions table, which is intended to store the session for calls from SBC (Ribbon Communications). This prevents duplicate calls in Tariscope.
1.2. A new AccountID field has been added to the viAccountHistory database view, which contains the subscriber's personal number. This allows you to display this number in the view for services in Tariscope.
2. Fixed an error when displaying a view for services, if fields that could contain null values were selected for display.
3. The error of displaying the value of the subscriber's ID instead of his personal number in the field of personal number, in the view for services, has been corrected.

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.
2. Changes have been made in the SI3000 parser, which allows you to avoid some errors when processing AMA files.
3. Added SBC (Session Border Controller, Ribbon Communications) parser. The data for the parser is obtained from the Radius accounting server. Only calls with the Stop attribute are processed.

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".
2. In the parcer of MD110, now it is processed two formats of call duration: ssss and h:mm:ss.
3. In the parcer of SI3000:
3.1. Fixed a creation of two records when it was processed records that belong to the call with duration > 30 minites.
3.2. Fixed an error ‘The given key ‘StartDateTime’ was not present in the Dictionary’.
3.3. Fixed an error 'Error converting data type nvarchar to bigint’. It was occured when calling or called numbers have a letter prefix. Such prefixes are removed if their length is up to 3 characters.

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.
2. Added a new report form: Non-working DNs. This report allows you to get a list of DNs entered in Tariscope as non-working, the period of their incapacity, the name of the subscriber to whom these DNs belong, as well as his personal account number. Information is provided for a given period. The total number of non-working numbers is calculated.

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.

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.

 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.
2. The HttpOnly parameter has been added for cookies used by the Tariscope system, which increases the security of the system.
3. Refined algorithm of work using SSL certificate. Stopping the Reporter and Scheduler services has been added to the Tariscope Start (Windows) application when the Tariscope service is stopped. In previous versions, they had to be restarted individually in order for them to be able to work using HTTPS.
4. Fixed an error that occurred on Linux when saving the price and date of the service.
5. Fixed a bug in saving widget settings from the dashboard.
6. ResourceUsageWidget has been temporarily removed from the list of available widgets.

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.
The prefix '+' is discarded.
If the phone numbers are included in the numbering plan, then the calls made through the gateways and which were previously treated as transit in Tariscope are become incoming, outgoing or internal calls. Thus, there is no need for the administrator to configure additional gateways, which is important when there are many of them, for example, when using softphones.
2. Changes have been made to the operation of Tariscope Observers, which use the 'Folder/File' data source. If the "Delete files after processing" switch enabled in the data source settings, then the "Last date" calendar value is ignored and all files in the folder are processed regardless of their date. This allows you to get rid of the situation of possible non-processing of individual files. Previously, this could happen when the CDR file was captured by the program when the Observer scanned the folders.
3. Fixed an error when working with an SSL certificate when Tariscope services did not work when using it.

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.
2. On the "Subscribers" page with a tree of subscriber groups within one branch, the group names are arranged alphabetically. Previously, they were displayed in the order in which they were created. With a large number of groups, it allows you to quickly find the one you need.
3. On the page "Editing a subscriber" in the "Group" list, the group names are arranged alphabetically. Previously, they were displayed in the order in which they were created. With a large number of groups, it allows you to quickly find the one you need.
4. Fixed an error when saving the effective date of a DN when adding a new DN.

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.
The display speed of this page has been significantly increased. The columns: Balance, Address, unique identifier and list of extensions have been removed from the display on the "Subscribers" page.

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.
2. Changes have been made to the subscriber search on the Subscribers page. To search for a subscriber by his extension (phone number), enter the number followed by a question mark (?). For example, to search for a subscriber with the number 1234, enter: 1234?
If a question mark is not added, then the search is performed either by the name of the subscriber, or by his ID, or by his personal account number.
3. Fixed subscriber search when creating a service view.

1. Fixed an error that could occur on the Service page when saving the service cost due to date localization.
2. Fixed an error in the ab_accounts_getsummary stored procedure that could occur on the subscriber's personal account page in the "Account Status" section.
There could be a penny (cent or and so on) difference between the charged amount and the balance at the end of the period.

Master of import of telephone codes and rates
1.1 Added choice of fare currency.
1.2 Added choice of tariff plan.
1.3 Added choice of rounding type: up to seconds (by default) or up to a minute.
1.4 Fixed calculation of updated tariffs.
1.5 Fixed tariff update date.

Synchronization with Active Directory
2.1 Added the ability to edit the synchronization profile with AD.
2.2 Fixed synchronization of some standard attributes.
2.3 Added the ability to import the cn attribute to fields other than FullName.
2.4 Added the ability to add any non-standard attributes for import by entering them into the AdditionalADAttributes system variable.

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.

Reports
5.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.
5.2 Fixed an error when configuring report settings.

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

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
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.

1. Improved import of phone codes (area and country codes) and rates to the Tariscope system from external files, for example, Excel format.
Any number of telephone codes that are on the same line of the file are now imported.
Codes must be separated by commas. Previously, the import was performed only for one code. This update facilitates changes in tariffs provided by the operator.

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.
2. Fixed a bug with saving mailing settings, when in some cases the need for SMTP authentication was incorrectly saved.
3. Fixed a bug when selecting folders with report forms for the Ukrainian language, the RU folder with Russian report forms was selected.
4. Due to irrelevance, the NetFlow collector has been removed from the Tariscope system.
5. When installing the system, the license for Tariscope was displayed only in English and Russian. Now added Ukrainian.

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.
2. Fixed a bug when exporting subscriber table parameters to an external file.
3. Fixed interaction with SureTax. Beginning from one of the latest versions, Tariscope did not send the subscriber's address to SureTax..
4. Converted the script to import information from CSV Bandwidth files from vb to c#.
5. Fixed bug when sending one report by e-mail from Tariscope Tasks.

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.
2. Fixed operation of the "Reset sorting for the selected field" button. Previously, sorting was reset completely for all fields.
3. Fixed an error in the operation of the API request when executing SQL queries (/api/sql).

1. When exporting a SQL query, the query results continue to be displayed on the page. They disappeared in the previous build.
2. Unused toolbar icons of views for services are hidden.
3. Fixed a bug in the parser for Panasonic that could occur when generating a route.
4. Display of tooltips for view icons has been fixed. Previously, tooltips could sometimes remain, preventing other tooltips from being viewed.
5. Added a generalized report on calls transferred to the Hotel systems.

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.
2. An Observer script has been developed to send notifications to the email when a specified percentage of the limit for a group of subscribers is reached.
3. Added the ability to select a saved view filter for calls as a report RDL parameter. For this, the report form must have the Filter parameter with its corresponding processing in the report form.
4. Added export of tabular SQL query results on the "SQL queries" page to a CSV file.
5. On the "Restricted subscribers" page, the display of information on groups of subscribers for which restrictions were set has been added.
6. An error in the work of the Tariscope Scheduler has been fixed, which could occur under certain circumstances when performing a task to build a large number of reports (more than 1000).
7. Corrections have been made to the work of parsers for PBXs Panasonic and Asterisk. For PBXs Panasonic corrected trunk formation for numbers larger than 4 digits. For Asterisk, saving records with the value "s" in the "dst" field has been fixed.
8. An error in the reporting task has been fixed, when reports could continue to be generated after the task was cancelled.
9. Fixed a bug where the recommendation to configure the Observer was always displayed in the Equipment settings.
10. Minor changes have been made to the text information of the Tariscope installation wizard.

1. The parser for PBX Coral 6000 v16.8 with variable configuration of SMDR fields was added.
2. Made changes to the processing of CDR records from CUCM. Previously, when processing conference calls, an error could occur in the log.
3. Fixed bug with automatic detection of routes / gateways.
4. Fixed error of the database backup task in the Tariscope Tasks. With a large volume of Tariscope database and insufficient resources of the SQL server, an error may occur due to exceeding the time for the operation.

1. Fixed manual switching of the restriction status. Relevant for licenses with the restriction feature.
2. Fixed the "Clear charges manually" function for restrictions on subscribers or groups. Relevant for licenses with the restriction feature.

1. Added a new Observer script for the function of restricting individual subscribers on 3CX v18.
2. Added configuration for parser MD110: you can set routes or their first digits, and for outgoing calls that are made through these routes, an access code will be added to the dialed number.
3. Added processing of nested reports in RDL format.
4. In Tariscope Tasks, added processing of reports that contain data on several subscribers.
5. Added non-editable document type, which is now used by default for documents.

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).
2. The algorithm for searching the dialing code for the dialed number has been improved.

1. Added the ability to process CMR files from CUCM with separated fields for the originator and terminator of the call.
2. Corrected connection of CMR records with CDR records in the Tariscope database.
3. When charging calls for short telephone numbers, now the call code search is performed only in local codes (numbers).

1. Fixed bug related to using HTTPS.
2. Fixed error with saving parameters of the Observer data source, which is configured through the Equipment creation wizard.
3. Fixed error of displaying call trace if two operators are installed on the route (gateway).
4. Fixed error when creating a view for services.
5. Fixed export of views in PDF format in order to display them correctly on the page.
6. Added details of the reason for call termination for SI3000 (Iskratel).

1. Added the ability to enter email addresses ending with the "underscore" character.
2. Fixed a bug with the synchronization of data with AD associated with the subscriber's address

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.
2. Increased view download speed. Significantly increased the download speed for calls if it has many records, compared to versions of Tariscope 4.5.x.
3. Improved reporting. In Tariscope 4.6, the type of report parameter that you enter when you run the report manually or when you configure the Tariscope Scheduler task settings depends on the type of variable, such as a calendar for a date and a box for a number that allows you to enter only numbers, and so on.
4. Tariscope Tasks. The Tariscope Tasks is a service which is intended to automatically execute tasks by schedule.
5. Hotel systems. Simplified work with the subsystem of interaction with hotel systems.
6. Tariscope Observer. Improved configuration and management of Tariscope Observer services.

Other changes and fixes: 
1. When re-rating calls in the view, the work with the view is not blocked, as was the case in previous versions. Upon completion of the re-rating, a notification about its completion appears.
2. Improved work with logs. All logs are now located in one place: C:\ProgramData\Tariscope\Logs.
3. Simplified work with Smart Assistant.
4. In Tariscope 4.6, all Windows and Linux services start with the prefix ‘TS.’. The dot is followed by the service ID.
5. Changed the location of exchange rate update profiles to: C:\ProgramData\Tariscope\CurrencyProfile.
6. Improved system configuration security.

Switching to Tariscope 4.6

All existing Tariscope users with warranty support can upgrade to the new version of Tariscope 4.6.
Users who have reached the end of their warranty support must purchase the technical support.
The price of the Tariscope 4.6 billing system remains the same as the price of the Tariscope 4.5 system.

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.
2. Fixed a bug in the Tariscope Personal Area when displaying a view for calls.

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.
In previous versions, it was assumed that the login always corresponds to the email address. For considered case, the login to access your personal account using AD is now saved separately from the email address on the subscriber's page, the Details tab, Auxiliary identifiers.
In the Auxiliary identifier field, enter the value of AD_Domain. In the Type field, enter the login for AD.
2. Added a new system variable of RoundTax, which determines whether the tax will be rounded or not. If its value is 1, then tax is rounded to 2 decimal places (since it worked before the current build).
If the value is 0, then the tax is not rounded. In this regard, changes have been made to the corresponding stored procedures (ab_accounts_getsummary, ab_accounts_getdebt, ab_accounts_getdebtforall).

Tariscope Personal Area
1. In the My Calls view, the Caller / Called Party columns now display the name of a contact from the phone book if the caller added such a telephone number.
2. Added the "Add number to phone book" icon to the toolbar of the call view. It allows you to add new contact parameters for the selected phone number in the view without going to the phone book page.
3. In the view for calls on the toolbar, an icon has been added that allows you to set a filter by dates. The parameters of this filtering are saved in the filter history.
4. For the group leader in the view for group calls, on the toolbar, an icon was added that allows you to select calls from one or more group subscribers.
5. For the head of the group (department) added the ability to change the categories of calls of subscribers included in his group.
6. Fixed rounding of numerical values ​​in the user profile, section "Services" (two decimal places instead of four).
7. Fixed a bug where it was possible to add a contact to the phone book with an empty line of the contact name or number.
8. Added the ability to save the state of views: selected columns, sorts, groupings, filter.

Tariscope administrator views
1. Viewing the SQL filter is now available only to the administrator. Added the ability to set a filter using an SQL query (the value of the query after the WHERE clause).
2. Added filtering by dates and specific subscribers.

Bug fixes
1. Fixed a bug with copying a rate (tariff).
2. Fixed error of saving a report after a tab was left open for a long time.
3. Added the ability to toggle the "Is local" option for dialing codes.
4. Fixed the error of editing the validity dates of the telephone code.

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.
2. Fixed error processing call duration with tens of hours in the Avaya CS1000, Meridian 1 (formerly Nortel) parser.

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.
Since in some countries the transfer of working days is used, you must first set up weekends and holidays for daily services.
2. Changed the mechanism for displaying the transfer of working days. These days are now displayed only for the selected year, not for all years. This display applies to both telecom operators and daily services.
3. In the parameters of the subscriber, namely in his services, a search has been added by the phone number (extension) to which the service was assigned, or by the name of the service.
4. On the page of subscriber phone numbers (extensions) added the display of the number of services for each subscriber phone number.
5. Added the ability to quickly switch from the subscriber's phone numbers (extension) to services that are assigned to this number.
6. Fixed definition of holidays (Saturdays and Sundays) for redefined operator days.
7. Fixed localization.

1. Added the ability for a subscriber to have any number of addresses.
2. The address can be linked to the phone number or IP address of the subscriber.
3. Added fields to the information about the subscriber's bank: the name of the bank and its address.
4. In the settings of the Tariscope Personal Area the setting of the scheme of possible transitions from one tariff plan to others was added.
5. Added support for the PayPal payment system to the Tariscope Personal Area.
6. Added display of subscriber services in the Tariscope Personal Area.
7. Added the ability to delete an extension that has services. In this case, the service is transferred to the subscriber.
8. Added search for a subscriber by contract number.

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.
2. Added support for Unify OpenScape Business X.
3. Updated the data source of the SFTP client. In previous versions, this client had difficulties with some SFTP servers.
4. Updated data source FTP server.
5. Added display of payments in the view for services.
6. Added display of the call type for incoming calls in the view for calls.
7. Fixed bug with importing subscribers from an external file. Previously, if the file did not contain information about the rate plan, then the subscriber was assigned a rate plan without a name.
8. Fixed toolbar in views.
9. Fixed some bugs in localization.
10. Fixed a bug that occurred when reopening license information.

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.
2. Added a simplified functionality for managing tariff plans of subscribers in the nodes (mass replacement, addition, update).
3. Fixed localization.

All additions and corrections of this release relate only to the Tariscope Personal Area.
1. Now a subscriber can change the rate plan. The function is available if it is allowed by the Tariscope administrator. Relevant for the Tariscope Provider edition.
2. The Tariscope administrator can allow or prohibit subscribers from changing rate plans in the Personal Area, set the date for the new rate plan to come into effect, set the cost of changing the rate plan.
3. On the Personal data page, a display of the history of changing rate plans has been added, as well as additional information describing the current rate plan of the subscriber.
4. Fixed display of personal data of the subscriber in accordance with the latest Tariscope updates.
5. Removed unnecessary fields for the name and fixed the settings for contact numbers.

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.
2. Added the display of the direction for which the prefix is ​​applied (incoming or outgoing calls) to the prefix table.
3. On the Prefixes page, a message has been added if the phone number changed by the prefix is not saved in the database.
4. Added the display of the serial number of the Tariscope license at the bottom of the page, next to the version number. This information can be useful, for example, if you need to send a new activation request.
5. Fixed error of charging for connection, if this fee was set.
6. Fixed the bug in the Tariscope Personal Aria, which sometimes occurred when changing the call category.

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).
2. Changes in the Tariscope Watchdog service (service for tracking calls from the telephone system):
2.1. The interface for configuring the Tariscope Watchdog service has been redesigned.
2.2. Fixed false positives of the Tariscope Watchdog service when the predicted interval was equal to the real one.
2.3. Sending notifications from the Tariscope Watchdog service now contains the name of the PBX with which the problem occurred, instead of its identifier.
3. Added a new button to install and run all Tariscope Observers at once. This may be relevant when collecting data from several PBXs.
4. Added a new option that allows you to set access to a group of subscribers in the directory of your Personal Area.
5. Added a new option for setting a password for your Personal Area and sending it to a subscriber by mail. It is possible to apply this option for a group of subscribers.
6. Renamed some of the Tariscope Observer settings, which makes them more intuitive.
7. Fixed localization.
8. All tables in Tariscope now have adaptive behavior. If the screen size is insufficient, horizontal scrolling appears.
9. Fixed a bug when importing a subscriber when the data contained a rate plan.
10. Settings for access to your Personal area have been moved to the subscriber editing page.
11. Restored the ability to load a report into the documents of the selected subscriber through the Tariscope Tasks.
12. Fixed problem with saving SQL filters when adding/editing a task in Tariscope Tasks. Previously, filters might not be saved correctly.
13. Changing the password of the system administrator of the SQL server is now possible only for the system administrator (sa).

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.
2. Removed unused name fields for subscriber when importing from Active Directory (AD). Now the name field is one.
3. Added setting to remove characters like space from phone number when importing from AD.

1. A new report has been added to the Statistical reports group: Longest external calls.
2. Updated the following reports in the Statistical group. The ability to set the data period and the number of calls (subscribers) that will be included in the report were added.
2.1 The longest calls.
2.2. Most expensive calls.
2.3. Subscribers with the highest call costs.
3. Added a language switch to the Tariscope Personal Area.
4. In the Tariscope Personal Area in the table with calls, the fields "From subscriber" and "To subscriber" have been added.
5. Fixed localization in the Tariscope Personal Area and the Tariscope application.

1. Fixed editing of payment or charges for a month.
2. Fixed display of the type of payment when editing it.
3. Added the ability to provide a Tariscope user with access to enter batch payments. Previously, only the Tariscope administrator could do this.
4. The authorization form for the Tariscope Personal Area has been corrected, for the case when authorization by Active Directory is selected.
5. Added search for subscribers by e-mail address on the pages of Subscribers and in Subscriber Accounts.
6. Added a new report to the Generalized group: Subscriber Payments. It displays the payments of subscribers for a certain period.

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.
2. For the Work Orders subsystem, a new Tariscope user type, "employee", has been added, which has access only to this subsystem.
3. Added an application for a Tariscope user with the "employee" type, which allows him to view his tasks, mark the start and end dates of work.
4. Added a new widget, Work Orders, which displays active tasks and their current status.
5. Added a warning message to the CDR processing page if a file with a size of more than 128 MB is added for processing. Such files are not processed.
6. Added standard view: 1000 longest calls for the last month.
7. Added the ability to transfer balance when creating a linked copy of a subscriber.
8. Added the ability to select the format of the phone number that is used for searching among local codes (original as in CDR or converted to E.164 format).
9. Added a column to the users page that displays the type of user (Administrator, Employee, etc.).
10. Fixed the import of operators from the SoftPI server (on-line), which was used in the initial setup wizard.
11. Fixed the function for creating groups of restriction classes.
12. Localization fixes in a number of modules.
13. Fixed the default view: 1000 longest calls this month. Previously, this view displayed data for the past month.
14. Fixed the display of the tariff plan name in the subscribers table. In some cases, the ID was displayed instead of the plan name.
15. Fixed the import of tax code when importing subscribers from an external file. Not imported previously.
16. Fixed editing of document types for the subscriber. When adding new types of documents, existing types are now displayed.
17. Fixed adding a number to a subscriber. Previously, the date of connection / disconnection of a subscriber could be set incorrectly.
18. Fixed the problem with new subscriber numbers. Previously, if you add a number, then it was not displayed when charging a service / service package or when adding a damage until you reload the page.

22.09.2020

1. Fixed Tariscope operation when using prefixes. In some cases, they were not applied.
2. Fixed views for calls. Filters by phone number and call cost did not work if the call cost was with a fractional part.

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.
2. Fixed menu for selecting a report for editing in the Report Form Designer application.
3. Fixed error when creating a new report and saving it without a screenshot.
4. Fixed uninstaller. Previously, after uninstalling, some files remained.

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.
2. Improved the export of views to file. Now, instead of identifiers for a number of fields, the actual values ​​of these fields are exported.
3. Added the ability to select subscribers or a subscriber groups when creating or editing a task in Tariscope Tasks.
This function is used for the following tasks: Report generation, Charging periodic services, Newsletter. Previously, a list of subscribers or subscriber groups, for which the task should be performed, could be specified only by writing a SQL query.
4. For the TCP Server data source used in Observers and in integration with hotel systems, added support for working with several TCP clients simultaneously.
5. Added a subsystem for monitoring the state of Tariscope services. Tariscope services, for which the monitoring will be enabled, will be automatically restarted when they are unexpectedly terminated. This subsystem maximizes service uptime. To include the Tariscope service in the tracked list, you must enable this function on the service settings page. By default, the monitoring function is enabled only for the Tariscope server, the Tariscope main service.
6. Edited settings for PBXs: Aastra MX, LG LDK 100/300, LG-Ericsson iPECS-LIK and Panasonic KX-xxx.

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.
2. Added the page notifying about an error in connecting to the SQL server. Previously, information about such an error was not specified, which did not allow the user to deal with the problem on his own.
3. Optimized the work with the Tariscope licensing server. Earlier Tariscope could access this server several times in one request to the page. Now it addresses once every 5 minutes, which reduces the load on the CPU.
4. Fixed localization in some settings for telephone systems.
5. Added the ability to open an element by double-clicking for the following pages:
5.1. Views.
5.2. Reports.
5.3. Tariscope Observers.
5.4. Tariscope Tasks.
5.5. Subscribers accounts.
5.6. List of subscribers.
5.7. List of services.
5.8. List of service packages.
5.9. List of currencies.
6. Added the ability to set a name for an instance of the Tariscope system. The name is displayed at the top of the page. This function may be relevant for users who have several licenses and simultaneously administer more than one Tariscope system. To specify the name of a Tariscope instance, a button has been added on the System variables page.
7. Added the ability to convert internal calls to city calls. This functionality can be useful for telecom operators, who want to charge calls between their subscribers as the city call. This function is configured on the Provider management page.

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.
2. A new script (GuardianConnector.cs) for Tariscope Obsserver services has been developed. It is designed to integrate with the SoftPI Guardian subsystem. The script must be connected to the Observer for the "New call processed" event.
3. Updated the Tariscope task to receive currency rates. Added a new mechanism for obtaining the NBU currency rate, which is not tied to the site page.
4. Added the ability to receive currency rates for a specific date or for a range of days from the Currency rates page without using the Tariscope Tasks.
5. A new task type has been added to the Tariscope Tasks: Newsletter. It allows users to send messages by e-mail.
6. Added the ability to send messages from Tariscope in HTML format.
7. A new widget has been added for the dashboard to display the exchange rate from the NBU website.
8. New fields have been added to the subscriber's parameters: date of birth and gender.
9. When calls are re-charged from the Calls view, the phone cache is cleared. Clearing the cache is necessary if you have made any changes to the system settings related to area codes.
10. Added the ability to assign a call category directly from the call view.
11. Added a new type of call category: System. This category cannot be deleted. It is created by Tariscope if necessary.
12. Added a new system category: Fraud Call. It is automatically assigned to fraud calls and can also be manually assigned in the Call View.

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.
2. Added the setting page (and menu item) "Days with interruptions". It was designed to account for the days when there were interruptions in the work of Observers or PBXs, and no information about calls was received. This information will allow the Tariscope Watchdog service to correctly predict the waiting for information about calls.
3. On the Observer pages, added information about the predicted time interval before receiving information about a new call.
4. Added a new widget for the dashboard, showing the time elapsed since receiving information about the last processed call.
5. Added a new widget for the dashboard, which displays a graph of the predicted load by the Tariscope Watchdog service and the current state with receiving information in the form of a red dot.
6. In the widget "Information about Tariscope", information about the version of the system was added.
7. Added the ability to automatically determine the best distribution of subscribers for the Tariscope Forecasting service, which predicts charges to subscribers.
8. Added the ability to change the month for forecasting charges in the Tariscope Forecasting service.
9. Added a system of global notifications about events in the Tariscope system.
10. On the call view page, added the ability to open call details in a new window. This allows you to see simultaneously both the processed call and the original information on it.
11. The function of updating rates when importing telephone codes and rates from an external file has been improved. Previously, if a rate was already assigned to the area code, the rate value from the imported file was ignored. Now, in this case, a new rate is created with a new date.
12. Fixed sorting of view data when applying grouping.
13. Fixed call rating. If the dialing code that was used in the call is absent in the Tariscope database or it does not have an assigned rate, then the rate assigned to a similar code, but with a smaller number of digits, is applied.
For example, if the dialed number used the code 380057, and a rate has not been assigned this code, then the rate assigned to the code 380 will be applied.
14. The description of some settings for CUCM has been corrected, allowing more precise understanding of their purpose.
15. Changed display of the server name in the "Database Information" widget. Now the PC / Server name and SQL server name are displayed separately.
16. Fixed localization for some services.

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.
2. A new widget for the dashboardhas been developed  to display the results of the month charge prediction feature.
3. A new user right named Access Smart Assistant was added. It allows user to predict month charges for customers.
4. The settings of some Tariscope system services are simplified, namely: the Hotel system, Flow collector and Tariscope Tasks.
5. In views for calls, services, and traffic, the ability to copy any table cell or the entire row was added.
6. Two new call types were added to the system: Free line is used for calls to phone numbers with code 800, Toll line is used for calls to phone numbers with code 900.
7. Fixed the email check when creating the Tariscope administrator.
8. Fixed caching the license key settings.

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.
2. In settings of S3000 (Iskratel) the Processing taking into account the number plan switch was added. It should be enabled when AMA files contain transit calls of subscribers. That means the subscribers are on another telephone system.

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:
1.1. for subscribers;
1.2. for telephone numbers;
1.3. for groups of subscribers;
1.4. for routes and gateways.
2. When creating a new call view for setting filtering parameters, a search has been added for the source and purpose of the call:
1.1. for subscribers;
1.2. for telephone numbers.
3. The error that occurred when checking the activation key when the key became inactive after updating Windows was fixed.

1. Two new widgets have been added to the dashboard: Request to database (tabular) and Call statistics+.
The Request to database (tabular) widget allows you to display the query results in several fields in a tabular form in the widget.
The Call Statistics+ widget allows you to build a call chart taking into account the filter for some of the database fields.

1. Added support for HTTPS. Tariscope can work both over HTTP and over HTTPS.
2. Added the ability to specify multiple ports for HTTP and HTTPS, separated by semicolons (;). Tariscope will work on several ports.
3. Added informing the user if an ad blocker or other similar extension is enabled in the browser. Ad blocker can block individual Tariscope windows.
4. A bug was fixed when opening the list of views, which arose for some users who were updated from previous versions.
5. A bug has been fixed when saving a view whose name contains forbidden Windows characters in the name.

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:
1.1. Independent group. Each task in the group will be launched without analyzing the result of completing the previous task in the group.
1.2. Dependent Group. Each task in the group will be launched only if the previous task was successfully completed.
1.3. Independent group with feedback. Starting tasks in a group is similar to option 1.1, but if any task was unsuccessful, an attempt will be made to execute it again.
 The number of attempts to complete tasks is configurable. If all attempts are exhausted, but the task was never completed successfully, then the next task in the list will still be launched.
1.4. Dependent group with feedback. This group is similar to option 1.3, but if execution attempts are exhausted and the task was not completed successfully, then the next task in the list will not be executed. The execution chain stops.
1.5. Run all together. All tasks of the group will be launched simultaneously in different threads, without a queue for their execution.
2. Changed submenu for Tariscope Tasks.
3. A display of the destination code and its description have been added to the window for editing the destination code parameters.
4. The display of the list of reports for the task of the Tariscope Tasks to generate a report for the case when the report is in the root folder of the reports has been fixed.
5. Added check when importing the parameters of the telecom operator. If a file of a different format (not json) is mistakenly selected, a message appears about this.
6. The word of 'copy' is added to the name of the imported telecom operator, if the operator with the same name is already in Tariscope.
7. Fixed closing the window through the Cancel button for the destination code editing window.
8. Several corrections in localization.

1. Added the script, fraud.vb, to detect the fraud.
2. Added the script MissedReaction.cs, designed to quickly receive information by e-mail about missed calls.
3. In the Rates settings, in the Accounts tab, a drop-down list has been added to describe the rate.
4. Added information on events that were set in Tariscope Observer. This feature is available for both local and remote Observer services.
5. A bug was fixed when sending messages from scripts of Tariscope Observer.

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.
2. Added the ability to clean the folder with temporary files. To do this, select Advanced options → Database info → "Clear Tariscope temp folder" button on the toolbar.
3. Fixed export in subscriber accounts.
4. On the Service settings page, earlier it was possible to create a service without specifying its name. Now this error has been fixed.

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.
2. Call rating within the PBX network has been improved. If the number you called is in the numbering plan of another PBX, then the call type is applied that the user set for the route (or gateway) connecting these PBXs.
  If it is set to change the call type for this route to internal, then the call is charged as internal. Otherwise, the call is charged as before at the rates of the provider specified for this route.
3. The mode of automatic creation of subscribers has been changed. Now they are created only if the subsciber's extension is included into the numbering plan specified for this PBX.
4. Added the ability to add extensions to the subscriber using a list or range of extensions.

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.
2. An icon has been added to the view page, which allows you to save the changed view as a new one.

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.

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.

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.

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.