New version of Tariscope 4.7
SoftPI announces the release of a new version of the Tariscope Enterprise 4.7.2 call accounting system and Tariscope Provider 4.7.2 billing system. Most of the Tariscope 4.7.2 updates are intended for telecommunications operators (providers), i.e. users of Tariscope Provider. Tariscope 4.7.2 includes all updates and fixes that have been made since the release of the previous version, 4.7.1.
New functions
1. New report forms
First and foremost, report forms related to the accrual of VAT on telecommunications services provided have been added.
1.1. Report – procedure for calculating VAT for all subscribers
The procedure calculates VAT for all subscribers for a specified period. VAT is applied to all service charges in the subscribers' Tariscope bills for the selected month. If there are no charges, no VAT is calculated. Upon completion of this procedure, a report is generated; an example is shown in Figure 1.
Figure 1
1.2. Report – procedure for individual VAT calculation
The procedure calculates VAT for a specific subscriber for a given period. VAT is calculated on all service charges in the subscriber's Tariscope invoices for the period. If there are no charges, no VAT is calculated. Upon completion of the procedure, a report is generated; an example is shown in Figure 2.
Figure 2
1.3. Report – procedure for calculating VAT for all subscribers for calls
The procedure calculates VAT for all subscribers based on their calls during a specific month. VAT is applied to all charges for calls listed in the subscriber's Tariscope bills for the period. If there are no charges, no VAT is calculated. Upon completion of the procedure, a report is generated; an example is shown in Figure 3.
Figure 3
1.4. Report – procedure for the individual calculation of VAT on call charges
The procedure calculates VAT for a specific subscriber over a given period based on all their calls. If there are no charges, no VAT is calculated. Upon completion of the procedure, a report is generated; an example is shown in
Figure 4.
Figure 4
1.5. Services intended for subscribers
The report displays the service name, the number of subscribers to whom it is assigned, the list of these subscribers, and the quantity of the service allocated to each subscriber. The service identifier is used as a parameter. An example of this report is shown in Figure 5.
Figure 5
1.6. Accounting for the number of subscriber extensions
The view displays the number of subscribers and phone numbers that are currently active. The data is sorted by subscriber name. An example of the report is shown in Figure 6.
Figure 6
1.7. Services for a specific subscriber
The report displays the total number of a subscriber's services, a list of these services, the quantity of each service, and their identifiers. The service identifier is used as a parameter. An example of the report is shown in Figure 7.
Figure 7
1.8. Accounting for specific subscriber extensions
The report displays the number of the subscriber's phone numbers, a list of these numbers, and the number of services assigned to each number. The subscriber identifier is used as a parameter. An example of the report is shown in
Figure 8.
Figure 8
1.9. Charged services
The report provides aggregated charges for all subscribers across all services: recurring, one-time, and call-based for a specified month. The total cost of the services provided is calculated. An example of the report is shown in Figure 9.
Figure 9
2. Additional field when importing subscriber parameters
A field for importing the name of the bank where the subscriber is served has been added to the subscriber parameter import wizard.
3. Avaya Aura Parser
The processing of CDR data from the Avaya Aura PBX has been fixed. In previous versions of Tariscope, data records received from the PBX that did not contain call information caused logging errors. While this did not affect actual call data processing, the log errors could raise questions among users regarding the correctness of CDR processing. The Avaya Aura parser now skips records that do not contain call data.
4. Mitel (Unify) OpenScape Business parser
Previous versions of Tariscope processed only Uncompressed CDR format; now, Compressed CDR format data is also processed. Processing for the Dialed Number Identification Service (DNIS) field has been added. While earlier versions processed only records longer than 50 characters, this threshold has now been reduced to 47. Processing has also been added for CDR records with Call Types 31 and 39.
5. Full name of the subscriber type
In previous versions of Tariscope, abbreviated subscriber type names were used in the subscriber settings. Now, the full names are displayed.
6. Tariscope API
6.1. The service.list method
The ability to retrieve all service parameters has been added to this method. In previous versions, this set of parameters was limited.
6.2. The accounts.payments method
The fields `bank` (bank name) and `paymenttype` (payment type) have been added to the parameters available via this API method.
7. Editing system variables
Fixed an error that occurred when editing Tariscope system variables. Previously, editing would not proceed if the "Description" field was empty.
8. Service parameters
Fixed a bug on the add or edit services page. The "Use day types" switch was always inactive.
9. Tariscope installation file for Windows
The Tariscope installation file in previous versions stopped Tariscope system services before starting to write files to disk. This shutdown was performed by the WMIC utility. Microsoft removed this utility as obsolete. As a result, when using previous installations of Tariscope, errors may occur during system installation. In the current installation of Tariscope, commands to stop running Tariscope services are replaced with PowerShell commands.
Upgrading to a new version by existing users
All Tariscope system users who have warranty (technical) support can upgrade to the new version of Tariscope 4.7.2.
Users whose warranty (technical) support has expired must purchase either technical support or a system version upgrade to use Tariscope 4.7.2. Both purchase options are equivalent in terms of features and price.
The price of the Tariscope 4.7.2 billing system (Enterprise and Provider) remains the same as the price of the Tariscope 4.7.1 system.
To migrate from previous versions, starting from 4.6.0 and up to 4.7.1 inclusive, you do not need to perform any additional actions, for example, uninstalling the previous version. The only thing recommended is to stop the Tariscope Observers and Tariscope Tasks (Scheduler) before running the installation file.
