Introduction. OTRS-Billing is alternative Call Accounting software (web-billing) as package of modules for OTRS Call Accounting module for OTRS is free software, distributed under the terms of the AGPL (GNU Affero General Public License). The system is designed for administrators and IT-services, which is necessary to carry out a verification with telecom providers, analysis cost of calls, loads channels of PBX, keep history crosstabs of PBX. Unites Help Desk system, base of subscribers and control of telephone traffic. The system can process CDR-data from a network of multiple PBXs, as scheme: The module is designed for Windows-based platforms, OTRS-installer for versions with StrawberryPerl. It can be installed on Windows-based versions prior to and including OTRS-3.2.3 For versions OTRS 3.2.4 and above, Call Accounting module can be install manually. Features: Support CDR-formats of PBX: - Siemens HiPath 3000 - Unify OpenScape Business, OpenScape Office MX/LX Costs of own and transit calls. Multi-tariff charging scheme. Database type: MySQL. The system uses single (one) area code table of countries / cities. Can be connected extended codes table. Collect segmented calls (desegmentation option). Traffic Event Notification (event catcher). Display resolution: 1920x1080 (24-inch wide monitor). Identification of customer is based on processing fields: PBX, trunks, station (CLIP). This principle allows you to uniquely identify the customer, even if you use the same numbering of subscribers at several PBX.
Log format. Source CDR-log of HiPath 3000 will be transformed to a look: Income Line Number-A Outgo Line Number-B Date Time Duration Cause This format of CDR, according to the developer, most is suitable for processing of transit connections. Installation. System requirements: PC is running Windows OS; CPU: Dual Core Intel; System Memory (RAM): 2GB+; Hard Disk: 100GB free space; Display resolution: 1920x1080 (24-inch wide monitor). 1. Download and install OTRS (package for Windows). Installer otrs-3.0.22-win-installer-2.4.8 for Windows can be found here: http://ftp.otrs.org/pub/otrs/ 2. Download and unzip the package otrs_billing_v1.0.1b_en.zip into an directory. 3. On tab Admin -> Package Manager, select the package otrs_billing_v1.0.1b_en.opm from the directory into which it has been extracted. 4. Install the package. 5. Restart OTRS through Program menu "OTRS Services Restart". After successful installation, appears the sub-menu "Telephony". Proceed to configure the module pricing. At initial setup, you must create tariff record PBX on tab: "Billing: CDR source". Further on tab: "Billing: Tariff plans" create tariff plans for telephone providers used in PBX CO-lines (trunks). The order further establish records of subscribers is as follows: 1. Customer Management tab -> Add Customer 2. Subscribers Manage tab: select a customer and to fill necessary fields.. Customer - a subscriber or group of subscribers, which will be applied to the tariff plans. The key between table Customers and Call Accounting module - WebLogin (login of Customer). Billing: CDR source. CDR Manage. This tab describes the basic parameters for obtaining call records PBX.
Adding PBX new entry. To add a new record PBX, click the "Add" button. Enter information into the form fields. Confirm adding press "Submit" button. After that, it moves to the edit page of the record with additional parameters. On the edit page, select output format of CDR-protocol used output data. For the type of PBX Siemens HiPath 3000 (hipath3xxx) available protocols: - file - serial - tсp- client - tftp-client - tftp-server For the PBX type Siemens OpenScape Business and OpenScape Office LX / MX (osb & oso) available protocols: - file - HTTPS - tcp-server The protocol file is used to receive records from the specified directory in which the output file. Serial protocol used to receive records via COM-port. Tcp-client protocol used to receive records on TCP-based server. Tftp-client protocol used to receive records on the TFTP-server. Tftp-server protocol used to receive records on the TFTP-client. HTTPS is used to receive records on the protocol HTTPS. If you use a separator, its type must be pipe.
After confirmation of the protocol type field is displayed to enter the connection parameters: Data Collector with Serial-port is limited to one COM-port entry. The tftp-client protocol is least reliable for reception of data, since in this protocol reception is carried out with use of UDP-transport and in case of inaccessibility of the server, information will be lost. For this reason, it is recommended to use protocols: - tсp-client - tftp-server - HTTPS
Example for the source file. In this mode, data will be received from the specified file: Options: - Collect segmentation (desegmentation option) The option allows to try to collect segmented call into one. Collected segmented records (+30 info. Codes). This option is necessary if you need to carry out verification with a telephone providers. Explanation: If the call was transferred between several subscribers in the CDR-log will record each participant connections. It is difficult to compare, because, for example, with the tariff plan rounds to the minute, starting with the 5 second, the call duration of 15 seconds, which was transferred between the two subscribers with a duration of 6 and 9 sec, the program billing will be shown as the two calls of one minute. But, by the provider side has only one entry of this call with a duration of one minute. Desegmentation option solves this problem. Operation Desegmentation for the current table is irreversible. However, the segmentation can be restored by surgery, "Recost period" in the Extended module. - Identify incoming source This option allows to try determine source of incoming call. - Extended area codes The option allows for the identification of additional plug-in base area codes. Processing will be applied to the fields of: Destination Operator-2 The base is located in DB: tariffzone table: area_extension_codes
- PBX monitor This option adds the PBX to view status of CDR-Data in PBX-monitor module. Adding CO-lines. To add, click the "CO lines" and the button "Add" Enter the field lines: Interlink internal CO-lines. For proper identification, the "Interlink" of PBX should be the type of "internal". Inlines 0-0. This entry for each PBX required only one. If you are using a distributed network with internal channels, they also used a type of "internal.". Calls on the lines with this type will be treated with internal code_group and will not be charged.
External lines. The external lines are introduced separately, or in a range of 1-1, such as 1-30. For HiPath3000 line numbers correspond to the numbers on the tab Trunk ports in the Manager E. The lines must be defined to the operators who provide these lines.
LCR. This tab allows for billing connections to card operators such as when a call occurs when dialing a number and access PIN-code input through a line provided by another operator. Also allows modification of the number if the call originates from the application MyPortal in format E.164. LCR option can be used to identify internal channels. LCR type: operator. Example entries for PIN-operator: LCR dial rule # - corresponds to number of the rule of a set in the table of Dialing rules tables in Manager E:
LCR type: modificator. It is intended to modify the numbers if you are using a set of MyPortal, when the number dialed appears in the international format and without the prefix the log appear to enter the national / international networks. LCR dial rule # - corresponds to number of the rule of a set in the table of Dialing rules tables in Manager E:
Starting collect call data from PBXs. To start data collection, click on the icon Run The system will go into a state of receiving data. Message will change to "Collecting running" Working Directory: \installation path\otrs\otrs\cdrsrc With the successful launch in this directory will process the files and backup files collectors call records from the PBXs in the \installation path\otrs\otrs\cdrsrc\log Information CDR-sources updated with time period of 5 minutes. For immediate change CDR-sources, after editing, do the stopping and starting Collecting. When stopping MySQL server, for example, at restart OTRS, data will be accumulated in the buffer files in directory \installation path\otrs\otrs\cdrsrc\ buf and then start the service MySQL server, the data from buffer is automatically loaded.
Status of CDR-data receiving can be observed in the PBX-monitor module: Example of setting the output format in ManagerE: HiPath3000
Example settings for OSO LX: On Setup -> Central Telephony -> Call Detail Recording
Set the flag: Activate Call Charge Recording Further, the tab Expert mode -> Telephone Server -> Basic Settings -> Call Detail Recording
Set the following flags:
The CDR-log format of the "external" column output should be without a PBX prefix. Form LCR, if necessary, as illustrated by example: Activate LCR: Enter Dial rules
Make a Dial plan for your region, for example: Configuration Complete.
Subscribers: management The tab comes add / change charging information for subscribers PBX. To add an entry: search for clients by name or login. * - Display all the customers. Click LOGIN field to go to the add / change pages. After adding to the edit page, enter the additional tariff data: In the fields of CLIP and DID valid entries marked with an *. * - Matches any digit(s). Inlines field is determined by how the subscriber is connected - to a local subscriber terminal station Inlines to be selected 0-0. If charged transit telephone traffic, should be set inlines coming from a transit PBX. Tariffing of record begins of start date. Charged only valid entries. Viewing information about a calls. To view information about a calls, use the available report in the report module.
On the "Billing: Calls view" displays calls of customers. To view the source - use the "Billing: Extended module" -> "CDR source." OTRS-Billing 1.0.1b_en - Admin Manual Copyright 2015 IP-LAB.RU