The new version Tariscope 4.4
SoftPI is pleased to announce the release of a new version of the telephone call accounting system and billing system, Tariscope 4.4. The new version contains a number of innovations and bug fixes of the previous version.
Innovations of Tariscope 4.4
Support of SAP BCM
Tariscope 4.4 allows you to process the log files of the SAP BCM contact center. The contact center can independently generate a number of reports on calls made through it. However, it is often not used independently, but in connection with other telephone systems, to the telephone numbers of which calls are transferred. And in order to have complete information about the call chains, you need to have information about the call through another telephone system that is connected with the call data from SAP BCM. Providing the ability to handle a large number of telephone systems from different manufacturers, Tariscope 4.4 allows you to generate comprehensive reports that provide the user with full information about the calls made through SAP BCM, working in conjunction with other telephone systems.
Since the time in SAP BCM logs is set in UTC format, Tariscope has a setting that allows you to display local time.
Support of М 200
Tariscope 4.4 supports the processing of detailed information about calls from PBX M-200 (MTA). For users of this PBX, all features of the Tariscope system on call processing are available.
Support of Avaya Session Border Controller for Enterprise (ASBCE)
The new version of Tariscope 4.4 supports the processing of CDR data with ASBCE. As with a number of other telephone systems, Tariscope allows you to save all the CDR data from the ASBCE, which, if necessary, allows the user to analyze any data available in the CDR and generate reports on it.
Script to import calls data from CSV file of Bandwidth.com
For US operators, who use the CSV file from Bandwidth.com for calculating the cost of services for telephone calls, it became possible to use the Tariscope billing system, in particular, the Tariscope Provider edition, to account for the communication services provided. Naturally, these telecom operators can also have their own PBXs. Tariscope supports a wide range of telephone systems and does not have any restrictions on the number of telephone systems from which it processes CDR.
Addition of services on calls to customers
This feature is relevant only for telecom operators who use the Tariscope Provider edition. For each type of calls in Tariscope, determined by the rate settings, a service is automatically created. In previous versions, such services were applied to all customers and were not displayed in the customer (subscriber) settings. In the new version of Tariscope, these services are automatically added to the services of all customers, but each customer can be set the amount of services provided. Thus, the Tariscope administrator can specify that the calls cost, corresponding to the rate, will charge for local calls for some subscribers, and the calls cost will be charged for other subscribers, for example, with some kind of discount.
Rating of imported incoming calls
In Tariscope 4.4 the possibility was added to rate the imported incoming calls. Remind that in Tariscope there is a possibility not only to receive information about the calls made from the telephone system or from CDR files, but you can also import data from files with call data, for example, provided by the service provider. Specially developed scripts are used to import call information. In previous versions, when performing such an import, it was not possible to rate incoming calls.
Data display on taxes in the services views
This functionality may be of interest to users of the Tariscope Provider edition, who use the taxation of charged telecommunication services in Tariscope. The service view now displays accrued tax data.
Improving the work of script for interaction with hotel system
The ability not to transfer information about calls from office phone numbers to a hotel system was added in the scenario of interaction of Tariscope with hotel system, Opera (Micros Systems Inc.). To do this, you should set the subscribers type of "Service" for customers with such phone numbers.
Addition of fields to SI3000 table
Previous versions of Tariscope already contained the ability to save data from the AMA file, even if they were not used for charging calls. Such data could be used by administrators of PBX, Tariscope for various purposes. But a few fields from the AMA format were missing. Tariscope 4.4 allows to save all fields from the AMA file.
Arbitrary number of the personal account of the customer
This feature may be relevant for users of the Tariscope Provider edition. In previous versions of the Tariscope Provider, the subscriber ID was used as the subscriber’s personal account, which was automatically assigned by the system. In Tariscope 4.4, it became possible to use the previous option of assigning the subscriber’s account number, as well as using the previously existing subscriber account numbering system of the telecom operator.
Extending the use of RDL reports
In the Tariscope system, two types of reports were used for generating reports: own and RDL reports. Before the new version of Tariscope, RDL reports could only be generated from the standard Reports mode. In Tariscope 4.4, RDL reports can also be generated from the Accounts view and when a task of the Tariscope Scheduler is executed. Thus, the user for any tasks in the system can choose the format of the report at his own discretion, based on his own requirements.
New variable was added
In previous versions of Tariscope, the system automatically added 0 to the beginning of the phone number from which the incoming call was made (CLID). This was done in order to lead such a phone number to the telephone codes, which were present in the data of telecommunication provider, which allowed to determine the name of the settlement from which the incoming call was made.
However, in some cases such an operation is not required to be performed, since the CLID already contained 0. Therefore, the system variable of Add zero to CLID was added to Tariscope 4.4. The default value of the variable is 1. This means that Tariscope must add 0 to the beginning of the phone number. The variable is in the System variables configuration branch.
Addition of customer import options
Tariscope имеет возможность импорта данных абонентов из внешних файлов, что существенно ускоряет первоначальную настройку системы. В импортируемые параметры добавлены номер банковского счета абонента и код банка.
Services history was added
From Tariscope 4.4, the system maintains a history of services assigned to subscribers, which makes it easy to re-charge services for previous periods, if services with different prices are used in the different periods.
Export call information from Tariscope Personal Area
The ability for a subscriber who uses the Tariscope Personal Area was added to Tariscope 4.4 to export call data in one of the following formats: Excel, PDF, HTML, CSV.
Fixes
- Bug fixes in the Avaya IP Office parser.
- Bug fixes in the HiPath 4000 (Unify, Siemens) parser.
- Fixed a bug in the Alcatel-Lucent OXE parser when processing ticket files received via the TCP / IP protocol.
- Bug fixes in the Platan parser.
- Bug fixes in the Aastra MX-ONE parser.
- Fixed Asterisk parser when getting CDR data from MySQL database. Previously, under certain conditions, individual records could not be loaded into Tariscope.
- Fixed the logic of the restriction feature in Tariscope. In particular, before performing the restriction removal from the subscriber, the queue for restricting subscribers is cleared.
- Fixed a bug related to report variables.
- The error related to incorrect behavior of the Active only button on the Services tab of the Subscriber window has been fixed.
- Fixed import of payment information from an external file.
- The possibility of deleting subscribers together with the removed rate plan is excluded. Now a warning message appears that requires the subscribers to first change the rate plan, which must be deleted, to another one.
- Fixed import of reports in the PDF format in landscape orientation.
- Fixed a bug related to printing reports from the Tariscope Scheduler.
- Corrections have been made to a number of procedures that are used to work with customer accounts: clearing accounts, charging periodic services and others.
- Fixed bug in prefixes. If a special telecom provider was assigned to the prefix, then calls for which the prefix was applied were not rated.
- Fixed a bug in the Alcatel-Lucent OXE parser when processing ticket files received via the TCP / IP protocol.
