New version of Tariscope 3.5.26
Innovations
Support for SFTP server
The Tariscope Observer service (hereinafter "Observer") supports the ability to obtain information about calls (CDR, SMDR, etc.) when it works as SFTP servers. It allows to encrypt data which is transmitted through public networks. In particular, SFTP server of the Observer service can receive CDR files from SFTP client of Cisco Unified Communications Server (CUCM). An example of SFTP server configuration is shown in Figure 1.
Figure 1
Support for SFTP client
The Observer service supports ability to receive information about calls (CDR, SMDR, etc.) when it works as SFTP client. It allows to encrypt data which is transmitted through public networks. The SFTP client can be useful, for example, to collect CDR data from Avaya Aura Session Manager. An example of SFTP client configuration is shown in Figure 2.
Figure 2
Processing CDR from IP-PBX "Agat-UX"
The Tariscope 3.5.26 provides processing CDR from IP-PBX "AGAT-UX" by Agat RusTeh company. Tariscope configuration window to select this PBX is shown in Figure 3. Tariscope does not require any adjustment to the CDR format of the PBX.
Figure 3
Processing CDR from Reuters Wyatts DK2000
The Tariscope 3.5.26 provides processing CDR from special PBX "Wyatts DK200" by Reuters company. Tariscope configuration window to select this PBX is shown in Figure 4. Tariscope does not require any adjustment to the CDR format of the PBX.
Figure 4
The script for the restriction feature that used for 3CX Phone System (HTTP API mode)
A script, which enables the Tariscope users who use Tariscope with IP-PBX 3CX Phone System, was completely redesigned. It allows to apply the restriction feature in the case when Tariscope gets the CDR information after the end of the call.
Time conversion for 3CX Phone System
Due to the fact that in recent versions of IP-PBX 3CX Phone System the information about call time is presented in the format of UTC + 0 instead of a local time, for most users of Tariscope, whose area differs from the UTC + 0, the definition of call time is incorrect. In the new version this problem has been solved.
Alternative charging
In Tariscope 3.5.26 the alternative charging of calls has been implemented. This charging is carried out for a particular route (channel group). This allows the Tariscope Enterprise users simulate a work through alternative communications providers to select the optimal connection. For the Tariscope Provider users the alternative charging can be used, for example, as part of the system of settlements with other communications providers or to simulate the application of the new tariff policy.
Fixes
- Fixed a bug in the subscribers editor: a tree of subscribers wasn't updated, if the subscriber was added to a group, which even didn't contain subscribers.
- Fixed a bug in the Subscriber management mode when the Tariscope server and the database server are on different computers.
- Fixed a bug in the matching fields editor during the work of the import wizard when an import is performed from Active Directory.
- A parser for Mitel PBX, when handling unanswered calls, has been improved.
- A parser for PBX NEC Univerge, when handling internal calls, has been improved.
- An ability for a subscriber to set individual categories for calls has been added. Subscribers can set the category to the dialed number from your Personal Area. In the further the category is saved for all subsequent calls.
- An extra field "All numbers" has been added in the subscribers editor.
- An ability to import subscriber limits for the restriction feature has been added in the Subscribers Import Wizard.
