Tariscope 4.5.x. Administrator's guide
Chapter 5 Tariscope service
5.1 Control over Tariscope work
5.1.2 Monitoring Call Information
Call receiving monitor (Tariscope Watchdog)
Tariscope Observer services collect calls data from telephone systems into the Tariscope system. These services support a wide variety of data sources from which information is obtained, for example, TCP server, TCP client, and the like. That is, there are several objects in the call data collection chain. These are the following objects: telephone system, IP network (in most cases), a computer with Tariscope Observer, an operating system on this computer and the Tariscope Observer service. Each of these objects can fail, which will stop the calls data collection.
If it is important for you to promtly receive calls data, then you should constantly monitor the status of the system for receiving this data. Since the intervals between calls in the system can be different at different times of the day, as well as on different days of the week, the solution to this problem is not easy.
To solve this problem, a Call Monitoring subsystem or Tariscope Watchdog has been added to the Tariscope system. This system is based on artificial intelligence. For its work, it is desirable to have already received calls information for a period of 3 - 6 months. Tariscope Watchdog will analyze this data and calculate the interval through which calls are usually made at a particular hour of a day on a particular day of the week. If you still do not have the collected information about calls, then the Tariscope Watchdog can still be used. Every day it will process the data on calls and adjust the model of their arrival.
The Tariscope administrator must configure the Tariscope Watchdog system based on his needs. And if this system detects that there have been no calls for a period longer than that set during setup, then it will send a message about this event to the administrator or another person specified in the settings. Therefore, the administrator can quickly identify problems with receiving call data and fix them.
For the Tariscope Watchdog subsystem to work, the software must be installed on the Tariscope server: .NET Core Desktop Runtime 3.1.10 x86.
To configure Tariscope Watchdog, select in the menu: Smart Assistant. The corresponding page appears where you need to click on the Call monitoring button. The Tariscope Watchdog page appears, an example of which is shown in Figure 5.1.2.1.
Figure 5.1.2.1
On this page, click the Open settings button. The Settings page appears, an example of which is shown in Figure 5.1.2.2.
Figure 5.1.2.2
In the Previous period (in months) box, specify the required value. In this case, the Tariscope database must contain calls for the specified period. The more you select the period, the more accurate the model will be. But you must bear in mind that if you have chosen a large previous period, then the processing of this data may take some time. Usually 3-6 months is enough if the call process in your company does not differ significantly for different months of the year. If the Tariscope database does not yet contain information about calls, but it does not matter what you specify in this box.
Select the desired value from the Separation of the day list. The shorter the interval, the more accurate the model will be, because it will be generated for each such interval, taking into account other settings as well. But in this case, building the model will take more time. There are the following options:
- 30 minutes.
- 1 hour.
- 2 hours.
- 6 hours.
- 12 hours.
- Do not split.
Enter the appropriate values in the Start of working hours and End of working hours boxes.
In the Weekends and holidays section, you must specify such days. This setting allows you to create a model for receiving calls depending on the type of day: workday, weekend, or holiday. By default, the weekend is Saturday and Sunday. In order for the system to know the days that are considered holidays, you must select in the list the Source of holidays of the telecom operator that you assigned to routes or gateways of your telephone system and for which you assigned a list of holidays.
If your Tariscope database for some reason may not have data on calls for some days that will be used to create a model, then to create a more accurate model, it makes sense not to take such days into account. To do this, specify the number of days in a row that should not be taken into account if there are no calls in the database for these days, in the Skip empty days in a row box. If your company does not work on weekends and does not have any calls on these days, then for the correct setting of the model in this position, you should specify 3 as the lowest value.
To take into account the parameters calculated in the model, turn on the Is adaptive operation interval switch. In this case, the period of the warning system response depends on: ·
- a value calculated for a specific time period;
- a value of the Minimal operation interval box;
- a value of the Deviation threshold.
Let us give an example. Suppose that in the calculated model it is assumed that on a working day from 10:00 to 11:00, calls are made every 5 seconds. If the Is adaptive operation interval switch is on, and the Deviation threshold is 40%, and the Minimal operation interval box contains the value 0, then the notification system should be triggered when there was no call for more than 7 seconds (5 sec. + 5 sec. * 0, 4). This setting means that Tariscope Watchdog will turn on every 7 seconds. Firstly, it will lead to a load on the processor of the Tariscope system server. Secondly, in the event of some unforeseen failures, for example, in the IP network for only 8 - 10 seconds, you will receive notifications about the delay of receiving data. It will be something like a false positive. To avoid this situation, use the Minimal operation interval box.
The Minimal operation interval box is used to indicate to the Tariscope Watchdog system, after what minimum time interval the system should check for new calls in the system. For example, if you set the value to 300 seconds, then for the above example, the system will check for new calls not every 7 seconds, but every 300 seconds. This reduces the load on the server processor and makes it possible to prevent the frequent triggering of the notification system when the interval between calls is small. Specify the value that is most optimal for your company in this box.
In the Deviation threshold position, set a value in percent, such that if the interval exceeds the one calculated by the model plus the specified deviation, the notification system will be triggered.
If Tariscope works with several telephone systems, and each of them has specific traffic, then enable the Analyzing each equipment separately switch. The system will create a call receipt model for each telephone system.
If you do not want to include the specific telephone system in Tariscope Watchdog, for example, the one into which calls are imported once a month from external files, then click on the Unused telephone systems link. A window appears with a list of all PBXs specified in Tariscope. Select the checkboxes opposite those that you do not need to consider when creating the model.
Tariscope has the ability to receive CDR (SMDR) data using FTP, SFTP protocols or, for example, from a folder. In these cases, the data arrives in the files at some interval. In order to take into account this interval and there were no false positives, turn on the CDR/SMDR receiving interval switch and set the value of the file receiving interval in the Interval in seconds box.
To track the work of the Tariscope Watchdog subsystem, its log is used, which can have a different level of detail. Select the required log detailing from the Log level list. The least detailed level is Status. The most detailed level is Debug.
To generate notifications, the first thing that is needed is the settings of the corresponding subsystem in Tariscope, which is performed on the Notifications and mailing page. If the settings are made there, then turn on the Notifications switch (Figure 5.1.2.2).
In the Working hour notification type list, select the required value:
- Once. The message will be sent only once even if the subsystem is triggered several times in a row.
- Each time. The messages will be sent each time the Tariscope Observer subsystem is triggered.
Select the required value from the Non-working hours notification type list.
Determination of working and non-working hours is carried out according to the settings specified in the positions Start of working hours, End of working hours, and Weekends and holidays.
By default, the notification is sent by e-mail to Tariscope administrators. It is possible to send such notifications to other email addresses. To do this, enter email addresses separated by semicolons in the Email box. In the Mail subject box, specify the message subject. For example, "Tariscope. There are no calls."
It is possible not to specify anything in the Mail text box. The {body} template will be replaced by the system with information about exceeding the interval between calls. You can add some information in the box.
To save the settings, click the Save button. After that, the Tariscope Observer page will be displayed (Figure 5.1.2.1).
Tariscope Watchdog runs as a Windows service. Therefore, it must be installed and start. By default, this service is offered from the LocalSystem system account. You can change this account to another. The main thing is that this account must have rights to access to the Tariscope database.
To use another account, turn off the Manage service switch.
In the User account box, enter the required account, and in the Password box, enter the corresponding password.
To install the service on Windows, click the Install service button. This button will change its name to Uninstall service, and the Run service button becomes active.
To start the service, click the Run service button. If the service starts successfully, this button changes its name to Stop service, and the status of the service should change to "Running", the Uninstall service button becomes inactive. If the service fails to start, click on the Open service log button, and analyze the errors.
To stop the running service, click the Stop service button. It will change its name to Run service, the status of the service will be “Stopped”. The Uninstall service button becomes active.
To uninstall the service, click the Uninstall service button. In this case, the Run service button becomes inactive, the service status is "Not installed".
In some cases, Windows can stop the running service. To have the service automatically resume its work, turn on the Automatic restart switch.
Previous page Next page
