Tariscope 4.5.1
SoftPI is excited to announce a new version of Tariscope, Tariscope 4.5.1. Tariscope is a call accounting and billing system that is used in more than 30 countries. The new Tariscope version contains a number of innovations and bug fixes of the previous version.
Innovations of Tariscope 4.5.1
Remote Tariscope Observer
Sometimes Tariscope users need to receive call information (CDR) from the remote telephone system. There is no problem if the telephone system can use internet protocols, such as TCP, FTP, SSH and others. But what will you do if the telephone system has only a serial port? Previously, our company, SoftPI, offered the own separate program, COM2LAN, that allows to transfer data from a serial port to IP network. It is also possible to use the program now. At the same time, now Tariscope 4.5.1 has an embedded feature that executes a CDR transfer from remote computer to the server with Tariscope (Figure 1).
Figure 1
It allows Tariscope users to install Tariscope Observer Remote Services Server (Figure 2) on the remote computer and configure and manage those Observers from the main Tariscope program.
Remote Tariscope Observers can be located on any PC running Windows 10, 8.1, 8, Server 2016, 2019, which has a connection with the server where Tariscope (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.
Figure 2
Setting an arbitrary serial port number
We added the ability to enter any serial port number (Figure 3) for the data source of Observer service. This ability is useful if you use remote Tariscope Observers which work with serial ports. Before, Tariscope Observer shows to configure only a list on ports that located on the Tariscope server.
Figure 3
New widgets
- 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 that Tariscope applications use. In advanced mode (Figure 4), it displays the resource usage that Tariscope applications with other software running on the server engage.
Figure 4
- Added a new widget that displays statistics of missed calls. There are widget options that display data in text form or in the form of charts (Figure 5).
Figure 5
- Added the widget displaying the status of Tariscope Observer services. It allows you to quickly assess the current status of Observers. An example of the widget is shown in Figure 6.
Figure 6
3CX Integration
A new integration was added to Tariscope (Figure 7).
Figure 7
The CDR file from the VoIP PBX 3CX Phone System contains information on transfer calls using 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 in the transfer call spoke with the subscriber. The Tariscope system can now receive the duration of the transfer call of each of the participants from 3CX that provides complete information about transfer calls.
Minor improvements
- The script for processing CDR data received from the operator Bandwidth.com (USA) was updated.
- Added support of paper sizes from A0 to A10 for manual generation in the RDL reports.
- Added a link to the SoftPI LinkedIn page.
- Added a link to the Tariscope software update history page on the site.
- Improved interface to work with subscribers and their numbers so that the toolbar is always visible when scrolling.
- Improved interface for subscriber documents. New subscriber documents are always displayed on top (the list is displayed from new to old).
- 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.
- 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.
- In the service view, a display of the number of charged services is added. Previously, only minutes were displayed for a specific call direction.
- Added saving the number of charged periodic and one-time services to the Tariscope database.
- 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.
Fixes
- Added a message that appears if the report has not been generated. Previously, the 404 page was appeared.
- Fixed an export of telecom providers' settings to an external file.
- Fixed the display of the last processed calls by Observer. Previously, the first 50 calls were sometimes shown, instead of the latest 50 calls.
- Fixed some errors in localization.
- 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.
- Fixed the work with routes and gateways. Previously, an application could stop working if a telecom provider that was deleted was assigned to a route (gateway).
- The error related to the configuration of route parameters has been fixed. It was not possible to reset the access code for the route.
- 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.
- Fixed the hanging up the Tariscope Web Administrator application when deleting large nodes.
- Fixed the process for deleting telecom providers from Tariscope.
- Fixed bug when receiving a list of Observers and active calls for Asterisk if the Tariscope database is installed on a remote server.
- 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.
- 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.
Accessibility
The Tariscope 4.5.1 installation package is available on the site. All Tariscope users who have warranty or post-warranty support can install and use this version. Before any Tariscope update, we recommend that you create a full backup of the Tariscope database.