Recall Prilog Service

Transcription

1 Extension integration based on CDRs Installation & Setup Guide Software version 1.0

2 TABLE OF CONTENTS 1. Introduction Prerequisites Installation Configuration Basic configuration CDR capture Advanced configuration Trunk matching table Testing Backup

3 1. Introduction When the extension number is not available in the recorded media, typically on trunk lines, this information can be retrieved from the pbx CDRs if it is available. This document is intended to help understand the principles, installation and configuration of the Prilog Service allowing the Recall to retrieve and display some additional information from the Call Details Records (such as the internal number of the called or calling) when this information can t be obtained in the recorder due to technological reasons. As mentioned previously, when the extension number is not available in the recorded media, this information can be retrieved from the pbx CDRs if available. The system gets the CDRs from the pbx and uses the CDR information to assign the extension number to the recordings. Examples of CDRs from different pbx brands: Date Time Ext Trk Number Duration 20/05/10 10: :00'27 20/05/10 10: '01 00:00'00 Ext Trk Date Time Duration Number A > L02 16/11/11 08:24 00:01:02 0 ST A > L01 16/11/11 08:48 00:00:00 0 ST Time Date Trk Duration Ext Number 30 IVIN 09:54 10/ :00: :05 31 IVIN 09:53 10/ :01: :32 Both CDR and recordings share parameters as Call Type (Incoming, Outgoing), Dialed number, Date and Time, Trunk Number, Duration, etc. Prilog service compares all values between both CDR and recording and when they match, the extension number appearing in the CDR is assigned to the recording. Different services installed are responsible for CDR capture, processing and data matching. Service Jusan CallXpressCollect Jusan CallXpressProcess Jusan Prilog Funtion CDR capture CDR processing Data matching 2. Prerequisites - Recall Software already installed and operational. -.Net Framework 4 extended (it will be installed automaticaly if needed). - CDRs from pbx available on the computer via RS232, TCP server, etc. 3

4 For Recall ISDN/Analog : - Enable the Recintegra option in the Recall Server Setup. 3. Installation Note: (Only for Recall ISDN, Recall Analog or Recall SIP) The installation of the Jusan PRI Database Logger Service (Prilog) is needed for products as Recall ISDN, Recall Analog or Recall SIP when the Extension integration is to be done; otherwise, do not install it. Note: (Only for Recall E1) The standard installation or Recall E1 already installs the Jusan PRI Database Logger Service. If it was already installed and the option PBX integration was not enabled and you need to integrate the Extension Number now, please uninstall current Prilog from Control Pannel- Programs and install it again activating this time the option PBX integration. To install the Prilog Service, launch the installation wizard (Bin\Setup.exe) and select Language- Install Software-Recall E1-Recall E1 Logger. Alternatively you can move to the folder RecallSoftware\Recall E1\PRI Database Logger and run Setup.exe When prompted about the option PBX integration, be sure to check the option PBX integration ONLY when you intend to integrate the Extension Number in the recording using the pbx CDRs; otherwise, leave the option un-checked. Follow the different installation windows. The installation will finish and the CallXpress Setup window will open. 4

5 4. Configuration For PBXs where the channel number is not shown in the CDR, just go through the basic configuration described in point 4.1 CDR capture. ONLY for PBXs where the channel number is shown, after going through the basic configuration also proceed with the advanced configuration as described in point Basic configuration CDR capture The configuration of the CallXpress Setup will define the type of connection with the pbx (RS232, TCP, etc.) and the processing of the CDR (PBX format). To enter into the CallXpress Setup, enter with default user and password (user: admin / Password: admin). Select the Site 1 and the configuration window will be opened. In the first section, select the right PBX format for the pbx CDRs. If you don t have the PBX format Driver, please contact our Technical Support at support@jusan.es In the second section called Type of Protocol, select the type of connection with the pbx (TCP server, TCP Client, RS232, etc.) and its related parameters (IP Address, TCP Port, Baudrate, etc.). After setting all parameters have been setup, select OK. The services will be restarted to make the changes effective. 5

6 4.2 Advanced configuration Advanced configuration can ONLY be used when the Trunk Number is shown in the PBX CDR. Otherwise, go only through basic configuration. The usage of Trunk Number from PBX CDR in the matching helps to avoid assigning a wrong extension number assignation mainly when the pbx traffic is high and some calls from the same number to the same destination are made at times very close to each other. To enable the Trunk Matching, open the Prilog.ini file and set the parameter TrunkMatch= Trunk matching table To use the Trunk matching, in addition to enable it by changing the parameter TrunkMatch=1, you have also to setup for each Device Channel Number, the corresponding Trunk ID as it appears in the CDR. To do this, you can be aware in advance of what kind of cabling you made between recording devices and pbx trunk; otherwise, make some tests calls in different trunks and build the table according to the Trunk ID info you get in the CDR. Open the Prilog.ini file with Notepad or similar plain text editor and setup the Trunk ID shown in the CDR to the relevant Device Channel Number: Example: Ext Trk Date Time Duration Number A > L01 16/11/11 08:24 00:00:15 0 ST Pbx CDRs A > L02 16/11/11 08:26 00:00:20 0 ST Ext Trk Date Time Duration Number A > L03 16/11/11 08:28 00:00:15 0 ST A > L04 16/11/11 08:30 00:00:20 0 ST Prilog.ini file [Device_BBRI0886] Channel_0886A = L03 Channel_0886B = L04 [Device_BBRI0887] Channel_0887A = L01 Channel_0887B = L02 As can be seen on the above example, the Device Channel Number 0886A is assumed to be connected to the PBX Trunk Number L03 as it appears in the CDR. Depending on the recording device (Analog, ISDN, E1, etc.), the Device and Channel identification may be different. Here are some examples for different recording devices: 6

7 Example for E1 recorder: Recall Prilog Service [Device_B1] Channel_B1 Channel_B2 Channel_B3 Channel 1 of the E1 B Channel 2 of the E1 B Channel 3 of the E1 B The different Channels (B1, B2, etc.) belong to the different channels in the E1 recorder. Example for ISDN recorder: [Device_BBRI0886] Channel_0886A Channel A of the unit with MAC Address ending in Channel_0886B Channel B of the unit with MAC Address ending in [Device_BBRI0887] Channel_0887A Channel A of the unit with MAC Address ending in Channel_0887B Channel B of the unit with MAC Address ending in The 4 digits identification belongs to the last 4 digits of the unit MAC Address. You can find the unit MAC Address in the label at the unit bottom. After the table has been completed, it is necessary to restart (Stop/Start) the Prilog service (Control Pannel-Administration Tools-Services) 5. Testing Open the Recording Manager software, make some test calls, wait for 2 or 3 minutes and then refresh the call list to check if the extension number is shown. The extension number is assigned in post-process mode; this means that when the call ends, the recording doesn t have the extension number yet. When the CDR is received and processed (capture and processing services run every minute), then the extension number will be assigned. It is recommended to enable the Auto-Refresh mode of the Recording Manager to help in the fields refresh to shown changes in the extension number after the post-process has taken place. 6. Backup In case of a system reinstallation due to a computer crash, it is recommended to keep a copy of the following files: Cdr Format Driver xxxx. LF3 file Prilog.ini file 7