New version of Tariscope 4.7
SoftPI announces the release of a new version of the Tariscope Enterprise 4.7 call accounting system and Tariscope Provider 4.7 billing system. Tariscope 4.7 includes all updates and fixes that have been made since the release of the previous version, 4.6.7.
New functions
1. New API method
A new Tariscope API method, call.info, has been added, which allows you to get information about calls from all or a specific subscriber through all or a specific PBX, if there are several, in a given direction for a given period.
2. New report forms
2.1. All incoming calls
The report allows you to get detailed information about all incoming calls for period. An example of this report is provided in the figure below.
Figure 1
2.2. All outgoing calls
The report allows you to get detailed information about all outgoing calls for period. An example of this report is provided in the figure below.
Figure 2
2.3. Internal calls of a subscriber
The report allows you to get detailed information on internal calls of a specific subscriber for a given period. An example of this report is provided in the figure below.
Figure 3
2.4. Missed calls
The report allows you to get all missed calls. Missed calls include those with the type ‘No Answer’ or with a duration of 0 seconds. An example of this report is provided in the figure below.
Figure 4
2.5. DNs that are not assigned to subscribers
The report allows you to get a list of outgoing calls for a given period, in which no subscriber was detected, i.e. the extension number was not assigned to any subscriber in Tariscope. The following fields are displayed: Number A, Number B, Date and time, PBX name. This report can be useful for users detecting extensions that were not entered in Tariscope, as well as for possible hacking of the telephone system, when an unauthorized subscriber makes calls at the expense of your company. An example of this report is provided in the figure below
Figure 5
2.6. Summary report for all groups
The report displays aggregated data on different types of calls for each subscriber. Subscribers in the report are grouped according to their belongings to a specific group. The report has the following parameters: period, group nesting level, filter. Filters stored in the Tariscope system can be used as filters. The report is generated in landscape orientation. An example of this report is shown in the figure below.
Figure 6
2.7. Generalized report by groups and subscribers
This report existed in previous versions but has been slightly improved. The report displays summarized data on the costs of telephone conversations of 2nd level groups in one table, and summarized data by subscribers in the second table, which are sorted by group name and extensions.
Figure 7
2.8. Missed call statistics
The report allows you to get statistics about the missed calls for period. An example of this report is shown in the figure below.
Figure 8
3. Sorting tables with subscriber parameters
On the subscriber settings pages, data sorting has been added to the settings tables for extensions and services assigned to subscribers, which is useful when the tables contain many rows.
4. TSConnector application for interaction with 3CX v20
The TSConnector application, which is used to interact with the Tariscope system and the 3CX v20 IP-PBX, has been redesigned to set or remove restrictions on outgoing calls by the subscriber. The Tariscope Observer script, which interacts with the TSConnector application, has been redesigned accordingly.
5. New parser for MiVoice Business
Tariscope also had a parser for MiVoice Business in previous versions. That parser processed the format that is called Standard SMDR Record Fields in the Mitel documentation. Now the parser for MiVoice Business has added processing of the SMDR format, which is called SMDR Extended Reporting Level 1 and Level 2. This format allows you to get the call start time with an accuracy of seconds, while the Standard format rounds the call start time to minutes. This format also allows you to have information about unfinished internal calls, which can be useful when analyzing missed external calls that were redirected inside the system. There are some other differences of this format.
6. Parser update for Avaya Session Border Controller for Enterprise (ASBCE)
Starting with version 10.2, Avaya has made some changes to the CDR format for ASBCE. Tariscope 4.7 takes these changes into account and now CDRs are processed without errors.
7. Parser update for 3CX v20
7.1 If the CDR field of DialNo contains the character “-”, it is removed for correct data processing.
7.2 If the FinalDN field contains the value 'EndCall' instead of an extension, then the FromDN field value is used for the call source field in Tariscope.
8. Parser update for NEC SV9100
Improved parser for NEC SV9100 to process call records containing the following call types: IVIN, IVOT, ITRS.
9. Updating the script for receiving CDR from Alcatel-Lucent OXE PBX
In Tariscope 4.7, the script for Tariscope Observer, which retrieves CDR data from the Alcatel-Lucent OmniPCX Enterprise via TCP, has been updated.
Tariscope database update
Tariscope 4.7 database has been updated to version 237. This update is related to changes in the stored procedure ab_mc_dns_transfer, which transfers extensions from one subscriber to another. As before, all extension parameters are transferred, but for the transferred extensions, a new address record is created with the values that were there. Therefore, now the extensions that were there before the transfer and the transferred extensions have different address records in the database and are edited separately from each other.
Error correction
1.Changing the order of fields in views for calls and services
Due to the fact that Chrome, Edge and Opera browsers have changed the DOM (Document Object Model) processing algorithm since April 2026, in previous versions of Tariscope, changing the order of fields in views for calls and services has stopped working. In the Firefox browser, this defect does not appear.
In Tariscope 4.7, changing the order of fields in views has been restored.
2. Error in views with data grouping
In previous versions of Tariscope, in some cases an error occurred when opening a view that had a data grouping function. This has been fixed in Tariscope 4.7.
3. Error configuring the restriction function under Linux
In previous versions, the list of restriction classes was stored in the Windows registry. This caused an error when using Linux. This error has been fixed.
4. Online import of telephone codes
Fixed an error on the Providers and rates -> Common phone codes page that occurred when clicking the Import online icon, which provides an expanded list of telephone codes.
Upgrade to Tariscope 4.7
All Tariscope system users who have warranty (technical) support can upgrade to the new version of Tariscope 4.7.
Users whose warranty (technical) support has expired must purchase either technical support or a system version upgrade to use Tariscope 4.7. Both purchase options are equivalent in terms of capabilities and price.
The price of the Tariscope 4.7 billing system (Enterprise and Provider) remains the same as the price of the Tariscope 4.6.7 system.
