Defining corporate calls in Tariscope Enterprise
Tariscope Enterprise (SoftPI) is a telephone accounting system. This system has many various functions that allow you to control the costs of telephone calls, optimally spend money on communication channels, detect unanswered calls and much more. Among these features is the feature to easily identify corporate calls. This feature can be useful for those users who have two or more PBXs and who want to control calls within the telephone network.
Consider a system of two telephone systems connected to each other (Figure 1).
Figure 1
There are two PBXs interconnected by Route 1 (group of lines). PBX 2 has access to the public switched telephone network (PSTN) via Route 2. That is, calls from PBX 1 to the PSTN are made via PBX 2. Call data collection is performed from PBX 2. If, for example, a subscriber with extension ‘202’ calls a subscriber of PBX 1 at extension ‘101’, then the CDR (Call Detail Record) data will show that this is an outgoing external call, because it was made outside PBX 2. That is, in the Tariscope system, such a call will be defined as a local call by default. The same situation will occur if CDR data collection is performed from PBX 1, and, for example, a subscriber with extension ‘102’ makes a call to subscriber with extension ‘201’.
In order for such calls in the corporate telephone network to be identified as corporate (internal) calls in the Tariscope system, settings must be made that will allow the system to know that the route connects two corporate PBXs.
Let's consider what settings need to be made in Tariscope for correct processing and billing calls.
- In Tariscope, you need to create two PBXs, although for our example, the basic settings need to be performed only for one PBX (PBX 2).
- You need to determine which route number on PBX 2 is used to connect the two PBXs. You need to add this route, set it to work as a Remote cabinet, and in the Equipment Network setting for PBX 2, set it to connect to PBX 1 and set the call type for such calls to "Corporate".
- All extensions of subscribers of both PBXs are added only for the second PBX.
So, we create two PBXs in Tariscope, an example of which is shown in Figure 2.
Figure 2
CDR data collection will be performed from the PBX named CS1000two. This PBX uses route 11 (line group) to connect to the PBX named CS1000. Therefore, on the Routes and Gateways settings page of the CS1000two PBX, we add this route (Figure 3).
Figure 3
After creating this route, select the corresponding line on the Routes and Gateways page (Figure 4) and click on the Equipment Network icon on the toolbar.
Figure 4
As a result, a corresponding window appears, where in the Equipment list, select the name of the PBX to which this route connects, and in the Call Type list, select the Corporate value (Figure 5).
Then save this setting.
Figure 5
Again, you need to select the line with this route and click on the Transit Call Tariffication icon on the toolbar. The corresponding window will appear, as shown in Figure 6, where you need to enable the Remote cabinet switch.
Figure 6
As a result of these settings, the line with the route connecting the two PBXs will look similar to that shown in Figure 7.
Figure 7
To correctly charge subscribers for the PBX named CS1000two, create a numbering plan on the settings page with that name. This numbering plan must include all extensions (internal telephone numbers) of subscribers of both PBXs.
Next, we add subscribers to Tariscope with their extensions. All extensions in our example must belong to the PBX with the CS1000two name.
For Tariscope to work properly, you must also perform all the other settings described in the Tariscope 4.6. Administrator's Guide document. These settings are not covered in this article.
An example of processed CDR data is shown in Figure 8.
Figure 8
As can be seen from this figure, calls from one PBX, where numbers start with 1, to another PBX, where numbers start with 2, and vice versa, are defined in Tariscope as corporate.
Other corporate telephone network configurations are possible. For example, if in Figure 1 an IP telephone system is used as PBX 2, then instead of the route connecting the PBX, you must determine the IP address of the gateway through which such a connection is made and enter this IP address instead of the route number (Figure 3).
If you have more than two PBXs in your corporate telephone network, then settings similar to those described in this article must be made for all routes (gateways) used to connect PBXs to the network.
In addition, for all PBXs that have a separate access to the public switched telephone network, you must organize separate CDR data collection. In this case, the Remote cabinet switch should not be enabled in the routes (gateways) to these PBXs, the extensions (internal telephone numbers) of subscribers must belong to these PBXs, and numbering plans must be created separately for all such PBXs.
Import of new service prices from an Excel file
To import services, you need to use an xlsx file with information about new service prices. Files in the xls format are not supported, as this format has long been obsolete. If you have an xls file with services from which you need to export new service prices, open it in Excel and save it in the xlsx format.
For greater convenience when setting up the import, it is better if the first row in the Excel file is the table header, as shown in Figure 1.
Figure 1
In this case, when "linking" Excel file columns to database fields, the column names from the Excel file table header will be displayed. If there are empty rows at the beginning of the table, then instead of the column names from the table, the following will be suggested: C1 - for the first column, C2 - for the second column, and so on.
At a minimum, the Excel file with new service prices should contain the following fields:
- The service identifier (ID) in Tariscope.
- The new price.
- The date from which this price becomes effective.
To import data about new service prices, open the Services page and click the Import from file icon (Figure 2).
Figure 2
The Import Wizard page appears (Figure 3)
Figure 3
Click the Start button. The next step of the Import Wizard will be displayed (Figure 4).
Figure 4
As mentioned above, only Excel files in the xlsx format are used for import. Click the Choose button and select the appropriate Excel file. Click the Next button. The next import step will be displayed (Figure 5).
Figure 5
The Available tables list contains a list of Excel sheets. Select the desired one and click the Next button. In the next import step (Figure 6), you must select the correspondence of the Excel file columns to the Tariscope database field names.
Figure 6
In the example shown in Figure 6, an Excel file was opened that contained blank rows before the data table. As a result, the columns are named: C1 … C5.
Accordingly, in the Service ID list, you must select the value C3, because this column contains service identifiers.
In the Price list, select the value C4, and in the From date list, select the value C5.
If the Excel file has a table header in the first row, this import step will be displayed as shown in Figure 7.
Figure 7
In this case, the lists will contain the column names from the table header (Figure 8).
Figure 8
Click the Next button. The Import Wizard page will look like Figure 9.
Figure 9
Here you must specify the date format used in the Excel file. For example, if your date is specified as: Month.Day.Year, then you must enter the format: MM.dd.yyyy
Click the Start Import button.
Check the import results on the Services page. You may need to refresh this page to see the imported data.
In addition, the results of the import are displayed in the Tariscope log.
Changing the rate plan in Tariscope
This article is more relevant for the Tariscope Provider edition, designed for telecom operators.
Rate plans exist in both editions: Tariscope Provider and Tariscope Enterprise. But, as a rule, Tariscope Enterprise users do not need more than one rate plan.
The situation is different for telecom operators.
The use of different rate plans with different costs of calls and with a different set of services allows you to meet the needs of a wider segment of telecommunication services users, providing them with exactly what they need. That is, by doing this you can attract new subscribers and increase the loyalty of existing subscribers to your company, as well as reduce the churn of subscribers.
The Tariscope system allows you to create any number of rate plans, include any periodic services in them, assign a rate plan both for a specific subscriber and for individual phone numbers or IP addresses.
In Tariscope version 4.5.4, it became possible to store the history of changes in the subscriber's rate plans or rate plans of his phone numbers or IP addresses. In addition, the ability has been added to allow the subscriber to independently change the rate plan using the Tariscope Personal Area.
As a reminder, it is possible to create, edit or delete a rate plan if you select the Rate plans item in the menu. An example of the page is shown in Figure 1.
Figure 1
Only a user with Tariscope administrator rights has access to the Rate plans page.
It is possible to delete a rate plan only if it is not assigned to any of the subscribers.
You can assign a specific rate plan to a subscriber on the Subscriber page, an example of which is shown in Figure 2.
Figure 2
To set or change a rate plan for a subscriber, click on the button next to the Rate plan box. A page appears, an example of which is shown in Figure 3.
Figure 3
To set a new rate plan, click on the Add icon on the toolbar. The New rate plan window appears, where you need to enter the name of the rate plan and the date from which it is valid. To save the settings, click the Save button.
In order to give the opportunity for subscriber to independently change the rate plan, the Tariscope administrator must load the Webconfig page in the Tariscope Personal Area, where select the Rate plan settings tab. An example of this tab is shown in Figure 4.
Figure 4
Turn on the Allow users to change their rate plan.
In the Plan activation date list, select the desired item from the following items:
- From the next day.
- From the next week.
- From the next month.
In the How often can users change their rate plan list, select the required option:
- Not limited.
- Once a day.
- Once a week.
- Once a month.
If you want to charge for a subscriber's transition from one rate plan to another, create a corresponding one-time service in the Tariscope system, and then select the name of this service in the Charged one-time service for plan change list.
To save the settings, click the Confirm button. The page appears with information about the modified Web.config file. You need to download this file and write it instead of the existing one. By default, this file is located in the folder: C:\inetpub\tsweb\www .
To change the rate plan, the subscriber must enter into the Tariscope Personal Area and select the Personal data menu item. The Personal Data page appears, an example of a part of which is shown in Figure 5.
Figure 5
If the subscriber is allowed to change the rate plan, the Change rate plan button will be displayed. If the subscriber clicks on this button, the Change rate plan page appears. The subscriber must select a new rate plan in the New rate plan list and click on the Send button. The page will display information that the rate plan has been changed and the date from which it will be active is indicated.
Tariscope and Active Directory
This article is primarily intended for users of the Tariscope Enterprise software (hereafter referred to as Tariscope).
The Tariscope system is used to process call information. Determining who made a specific phone call, as well as its cost, is performed only if the directory number is linked to a specific subscriber in Tariscope. Therefore, there is a need for the correct setting of subscriber parameters and constant support in the current state of such information. Tariscope allows you to do this in three ways:
- Manually adjust subscriber data.
- Import subscriber data from external files.
- Receive such data from the Active Directory.
If you have an Active Directory in your company, then using it will probably be the most optimal option for maintaining information about subscribers in an up-to-date state.
The basic information required for Tariscope Enterprise is:
- the subscriber's name,
- the unit where he works,
- his directory numbers (DNs),
- the date from which the employee (subscriber) works in the company and from which he owns DNs,
- release date, that is, the date when the DNs phone numbers no longer belong to this subscriber.
To get data into Tariscope from the Active Directory, a profile is created in Tariscope that specifies which Active Directory attributes are linked to Tariscope database fields. The name of the employee, his department and directory numbers are specified in the main attributes of the Active Directory. As a rule, additional attributes are created for the dates of employment and dismissal. If necessary, you can import other attributes into Tariscope, which are required for generating reports on the use of telecommunication systems (PBXs).
In order for Tariscope to work with additional attributes, you need to add their list separated by commas on the System Variables page to the AdditionalADAttributes parameter. For a detailed description of how to create a Tariscope synchronization profile with Active Directory, see the page.
Data import from AD can be performed either at the initiative of the Tariscope administrator from the Active Directory or Subscribers pages, or automatically according to the schedule by the Tariscope Tasks when creating the corresponding task.
The last option, i.e. the use of the Tariscope Tasks allows you to completely automate the process of obtaining data from the Active Directory, even if some of this data needs to be refined. An example of updating data can be a change of directory number. For example, directory numbers are stored in AD together with access codes to various PBXs, and access codes are not displayed in CDR data. In this case, in order to correctly identify the subscriber who made the call, the access code must be removed from the imported phone number. To finalize the data, you can use the RDL report, which will be launched after data synchronization with the Active Directory and perform the necessary actions with the Tariscope database data. This report may not display any data, but only perform actions with the database.
Thus, if you are a user of the Tariscope Enterprise software and your company uses the Active Directory, its data can be synchronized with the Tariscope database daily in automatic mode, thereby providing Tariscope with up-to-date subscriber data.
The trace of the call charging process in Tariscope
Tariscope system, which is a call accounting system and a billing system for telecom operators, has a powerful system of call billing. This charging system allows you to flexibly configure the processing of almost any call charging algorithm. You can use a different cost for different tariff plans; per second or per minute billing; the cost of a call may depend on the duration of this call or the duration of all previous calls for the current month, on the day of the week, on the time of day. The tariff can be set in any currency, and the cost of the call is calculated in the base currency with conversion at the current or other exchange rate. Call billing can be calculated simultaneously at the rates of two telecom operators. There are other possibilities as well.
All this flexibility requires some settings from the Tariscope administrator. When setting up Tariscope administrators do not always refer to the documentation, and they sometimes have problems with the correct calculation of the cost of calls. To make it easier to determine the reason for the incorrect setting of the billing system, the Tariscope 4.5.4 system has added a function for tracing the billing process, which reflects the results of each billing stage, and if it does not find the necessary data or the results do not correspond to what was expected, information about the parameter that requires settings is displayed.
This function is accessed from the views for calls. It has added the Recharge with tracing icon, which is shown in Figure 1.
Figure 1
The user must select the call that he considers having been charged with an error and click on the Recharge with tracing icon. Information on all stages of the charging process with information on each of the stages appears on a new browser tab. An example of a trace is shown in Figure 2.
Figure 2
If any of the tariffication stages was performed with an error, it is indicated in red. An example of this is shown in Figure 3.
Figure 3
The description for the failed step provides information on the possible cause of the error and links to the appropriate configuration page.
The user must follow this link, make the appropriate settings, and repeat the recharging with trace by clicking on the Refresh icon on the toolbar (Figure 2).
In addition to the tree, the results of tracing the tariffication of a call can be presented in the form of a table. To display such a table, click on the Raw Data icon on the toolbar. The Tariffication of a call with tracing page will look as shown in Figure 4.
Figure 4
If you still did not manage to correctly configure the Tariscope system, and you have technical support from SoftPI, send the data of this table to the SoftPI Support Team. To save the table in the file, on the toolbar, click on the Export of the table icon and select any file format for storing data from the following: Excel, HTML, CSV, PDF.
