Difference between revisions of "RecordMAN.client"

From pubWiki-en
Jump to: navigation, search
(Log into PABX)
 
(68 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<center>'''RecordMAN.client'''</center>
 
<center>'''RecordMAN.client'''</center>
 
<center>'''Instruction manual'''</center>
 
<center>'''Instruction manual'''</center>
<center>'''Issue 1.02 for version 3.00</center>
+
<center>'''Issue 1.03 for version 3.00</center>
  
 +
 +
 +
Dla wersji firmware od 4.11<br>
 +
Data aktualizacji 14 07 2011
 
= Introduction =
 
= Introduction =
 
RecordMAN.client application can be used for recording and listening phone calls realized using embedded recording (EbdRec) system installed in Slican PABXes. RecordMAN.client application, after defining recordings server address and appropriate access parameters, log into server and download its content, presenting list of recordings which can be listen or save in location defined by user (under only one condition, PABX admin assigned appropriate privileges in ConfigMAN application). Complete description of functions and configuration of embedded recording system installed in Slican PABXes can be found in ConfigMAN programming instruction. As recordings server any Slican PABX (CXS-0424, CCT-1668, MAC-Zero or MAC-6400) or PC with RecordMAN.server application installed (description of this application functionality can be found in appropriate instruction manual) can be used. Using RecordMAN.client application, it is possible to listen recordings stored in local archive create earlier using this application. Chapter 2 describes requirements needed to using any of mentioned recordings source.
 
RecordMAN.client application can be used for recording and listening phone calls realized using embedded recording (EbdRec) system installed in Slican PABXes. RecordMAN.client application, after defining recordings server address and appropriate access parameters, log into server and download its content, presenting list of recordings which can be listen or save in location defined by user (under only one condition, PABX admin assigned appropriate privileges in ConfigMAN application). Complete description of functions and configuration of embedded recording system installed in Slican PABXes can be found in ConfigMAN programming instruction. As recordings server any Slican PABX (CXS-0424, CCT-1668, MAC-Zero or MAC-6400) or PC with RecordMAN.server application installed (description of this application functionality can be found in appropriate instruction manual) can be used. Using RecordMAN.client application, it is possible to listen recordings stored in local archive create earlier using this application. Chapter 2 describes requirements needed to using any of mentioned recordings source.
Line 11: Line 15:
 
* At least 128 MB RAM memeory
 
* At least 128 MB RAM memeory
 
* At least 5GB free space on hard drive
 
* At least 5GB free space on hard drive
 +
 
=Software requirement=
 
=Software requirement=
If firmware 4.10 is installed in PBX, to download recordings from PBX or recording server it is necessarily to use software in version 3.00. Software in this version can be used also with previous firmware version. In this situation it is necessarily to check field '''Compatibility mode''' w oknie '''''Application settings>Application'''''. Field '''Pss - password''' is unused in this situation and connection is established after checking Login and hardware key.
+
If firmware 4.10 is installed in PBX, to download recordings from PBX or recording server it is necessarily to use software in version 3.00. Software in this version is compatible with previous firmware version and can be used with versions earlier than 4.10. In this situation it is necessarily to check field '''Compatibility mode''' in window '''''Application settings>Application'''''. This field is presented on below figure.
 +
<center>[[File:RM Settings.JPG]]<br>
 +
Fig. 1 Window '''''Application settings>Application'''''</center>
 +
Field '''Password''' is not used and loggin can be peformed according Login and hardware key.
  
= Operation with recordings server =
+
=RecordMAN.client application configuration=
 +
During first launching of RecordMAN.client application unique hardware key is generated - HardKey, this key enables access to recordings only from specified PC. Info about HardKey is uploaded to PBX automatically during first recording downloading from PBX. It is always possible to compare this key with data downloaded from PBX using ConfigMAN. Hardware key generated during application installation is presented in window visible on figure 6. The same hardware key should be entered in ConfigMAN , sheet '''Embedded recordings/RecordMAN.client accounts'''.<br>
 
During first launching of RecordMAN.client application following window appears:
 
During first launching of RecordMAN.client application following window appears:
  
 
<center>[[Image:io rm2 welcome window.png]]</center>
 
<center>[[Image:io rm2 welcome window.png]]</center>
<center>Fig. 1 Welcome window for first application launch</center>
+
<center>Fig. 2 Welcome window for first application launch</center>
  
If you choose „Run authorization wizard” option, window of authorization wizard will display, in this window data according PABX settings should be entered:
+
If you choose „Run authorization wizard” option, procedure of setting parameters and first log-in to PBX is started. Below figure presents authorization wizard window, while authorization procedure is presented in next text:
  
 
<center>[[Image:RM2_authorization_wizard.PNG]]</center>
 
<center>[[Image:RM2_authorization_wizard.PNG]]</center>
<center>Fig. 2 Authorization wizard window</center>
+
<center>Fig. 3 Authorization wizard window</center>
 
+
Into field '''Address of the server''' IP address of recordings server should be entered, while into fields '''Login''' and '''Password''' content of fields '''Log''' and '''Pss''' from appropriate record in sheet '''''Embedded recording / RecordMAN.client accounts,''''' in ConfigMAN application. After fulfilling above mentioned fields and pressing '''Next''' following window will appear:
+
 
+
<center>[[Image:RM2_configuration_finish.PNG]]</center>
+
<center>Fig. 3 Hardware identifier of PC with RecordMAN.client installed</center>
+
  
Authorization - configuration process was finished. During installation of RecordMAN.client application, computer hardware identifier is generated, this hardware identifier should be entered into ConfigMAN application (sheet '''''Embedded recording / RecordMAN.client accounts''''', field '''HardKey'''). This key can be visible in window '''Application settings''' and by pressing appropriate button, existing hardware identifier is copied to clipboard and can be pasted to appropriate field in ConfigMAN application. Hardware identifier enables log into recording server only from PC with this hardware identifier. Additionally data entered in field '''Password''' limit access to recordings only for specified person who knows this password. To lock access for  unauthorized persons during first attempt of downloading recordings from server, application RecordMAN.client forces change of password entered during first log-in. This password should be defined by PBX admin and next repeat during first log-in. Application forces password change and upload new password to the PBX. So PBX admin doesn't know this password, because it is presented in ConfigMAN as string of '''*''' (asterisk). After pressing '''Close''' button application start window including authorization data can be visible:
+
# From PBX admin you should gain information concerning PBX IP address and enter it into field '''Address of the server'''.<br>
 +
# PBX admin should create new record in sheet '''''Embedded recordings/RecordMAC.client accounts''''' and enter data into fields '''Log''' and '''Pss''' and inform RecordMAN.client user about these data<br>
 +
# RecordMAN.client user should enter these data to appropriate fields in authorization wizard window. After fulfilling above mentioned fields and pressing '''Next''' following window will appear:<br><center>[[Image:RM2_configuration_finish.PNG]]<br>''Fig. 4 Hardware identifier of PC with RecordMAN.client installed''</center><br>
 +
# Authorization process was finished. After pressing '''Close''' button application start window including authorization data can be visible:
  
 
<center>[[Image:io rm2 after.png]]</center>
 
<center>[[Image:io rm2 after.png]]</center>
<center>''Fig. 4 Window visible after finishing configuration''</center>
+
<center>''Fig. 5 Main window visible after finishing configuration''</center>
  
 
Window visible above is very similar to widow presented on figure 1. However it is possible now to download data from defined previously recording server. Additionally instead of „Run authorization wizard” button, information about authorization data is presented. Entered data can be always changed after pressing '''Settings '''button. In window (visible on figure 5) which appear after pressing '''Settings '''button there is possible also change server which RecordMAN.client log into.
 
Window visible above is very similar to widow presented on figure 1. However it is possible now to download data from defined previously recording server. Additionally instead of „Run authorization wizard” button, information about authorization data is presented. Entered data can be always changed after pressing '''Settings '''button. In window (visible on figure 5) which appear after pressing '''Settings '''button there is possible also change server which RecordMAN.client log into.
  
 +
=Operation with recording server=
 
== Log into PABX ==
 
== Log into PABX ==
As mentioned above, after pressing '''Settings '''button window which enables to change server which RecordMAN.client log into.
+
Log-in to PBX can be performed as follows:
 +
# First log-in into the server should be always executed with PBX, not with application RecordMAN.serwer, it assures uploading into PBX hardware key which was generated during installation process.
 +
# Process of uploading hardware key is described in chapter '''''RecordMAN.client application configuration'''''. This key is visible in '''Application settings''' window and by pressing button located near field with hardware key is copied into clipboard, from clipboard it can be pasted in any place. Hardware key enables to log-in only from PC with appropriate hardware key.
 +
# Before downloading recordings from server, RecordMAN.client forces primary password (granted by PBX admin) change and new password is uploaded to PBX. Due to this operation also PBX admin doesn't know this password, because in ConfigMAN this password is presented as '''*''' (asterisk) string.
 +
As mentioned above, after pressing '''Settings''' button, new window appears, where change of recording server is possible.
  
 
<center>[[Image:io rm2 aplication settings.png]]</center>
 
<center>[[Image:io rm2 aplication settings.png]]</center>
<center>''Fig. 5 Settings window''</center>
+
<center>''Fig. 6 Settings window''</center>
  
If in field '''Address of recording server''' PABX IP address is entered, PABX with this address is recording server, under condition that in sheet '''''Embedded recording / RecordMAN.client accounts''''', in ConfigMAN application there is an appropriate entry with login and hardware identifier as in window above.
+
In this window all configuration data (except password) are visible - this password is known only to authorized person. If in field '''Address of recording server''' PBX IP address is entered, PBX with this address is recording server, under condition that in sheet '''''Embedded recording / RecordMAN.client accounts''''', in ConfigMAN application following identical data are entered:
 +
* login,
 +
* password and  
 +
* hardware identifier shown in window above.
  
== Log into server ==
+
== Log into RecordMAN.serwer application==
If in window visible on figure 5, field '''Address of recording server''' is fulfilled with IP address of computer with RecordMAN2.server application installed, RecordMAN2.client application connects to this computer an reads data downloaded from PABX. Login and hardware identifier should be the same as defined in PABX. There is a possibility of reading data from server installed on the same computer as RecordMAN2.client application. To do this, field '''Select server type''' should be fulfilled with option '''Local server'''. In this situation there is no necessarily to enter login and password. It is assumed as default, that PC user is authorized to access to all files stored on this computer (lock can be set at OS level), so there is no needed to duplicate lock to recordings inside RecordMAN2.client application.
+
If in window visible on figure 6, field '''Address of recording server''' is fulfilled with IP address of computer with RecordMAN.server application installed, RecordMAN.client application connects to this computer an reads data downloaded from PABX. Login and password should be the same as defined in PABX. There is a possibility of reading data from server installed on the same computer as RecordMAN.client application. To do this, field '''Select server type''' should be fulfilled with option '''Local server'''. In this situation also entering login and password is required.
  
 
== Recordings archive ==
 
== Recordings archive ==
After selecting option '''''Local disc''''' from '''File''' menu special browse window with list of folders is displayed, in this widow RecordMAN2.client user can select a location on disc, to store recordings archive. After selecting folder with name '''Data''', including day folders with call recordings, all recorded calls will be show in application main menu. Until option '''''EbdRec server '''''from''''' ''File''' menu is selected, all operations are executed on recordings files stored in recordings archive.
+
After selecting option '''''Local disc''''' from '''File''' menu special browse window with list of folders is displayed, in this widow RecordMAN.client user can select a location on disc, to store recordings archive. After selecting folder with name '''Data''', including day folders with call recordings, all recorded calls will be show in application main menu. Until option '''''EbdRec server '''''from''''' ''File''' menu is selected, all operations are executed on recordings files stored in recordings archive.
  
 
= Recordings operation =
 
= Recordings operation =
Independent on recordings server (PABX, remote server, local server, local disc) in main window you can see recordings available for RecordMAN2.client user. On the left side of window, list of day folder is visible and in the main part of window you can see the recordings included in selected day folder. In the pane on the right side there is visible legend with descriptions used for stored recordings.
+
Independent on recordings server (PABX, remote server, local server, local disc) in main window you can see recordings available for RecordMAN.client user. On the left side of window, list of day folder is visible and in the main part of window you can see the recordings included in selected day folder. In the pane on the right side there is visible legend with descriptions used for stored recordings.
  
 
<center>[[Image:io rm2  main window.png]]</center>
 
<center>[[Image:io rm2  main window.png]]</center>
<center>''Fig. 6 Main window of RecordMAN2.client application''</center>
+
<center>''Fig. 7 Main window of RecordMAN.client application''</center>
  
RecordMAN2.client application user can see in main window only recordings according his/her access privileges granted in ConfigMAN application. These privileges are detailed define in chapter 3.4. At the bottom of RecordMAN2.client application main window, there are standard icons for play, stop and wind back or wind forward selected recordings, as also store recordings to computer disc as .wav file. Detailed description of actions, which can be executed is included in next chapters.
+
RecordMAN.client application user can see in main window only recordings according his/her access privileges granted in ConfigMAN application. These privileges are detailed define in chapter 3.4. At the bottom of RecordMAN.client application main window, there are standard icons for play, stop and wind back or wind forward selected recordings, as also store recordings to computer disc as .wav file. Detailed description of actions, which can be executed is included in next chapters.
  
 
== Recordings filtering ==
 
== Recordings filtering ==
As presented on fig. 6, in main window of RecordMAN2.client application there is a filtering pane, which enables to select specified recordings from all available for user.
+
As presented on fig. 6, in main window of RecordMAN.client application there is a filtering pane, which enables to select specified recordings from all available for user.
  
 
<center>[[Image:io rm2 recording filter.png]]</center>
 
<center>[[Image:io rm2 recording filter.png]]</center>
<center>''Fig. 7 Recordings filtering pane''</center>
+
<center>''Fig. 8 Recordings filtering pane''</center>
  
 
For searching recordings following fields are used:
 
For searching recordings following fields are used:
Line 94: Line 109:
  
 
== Recordings saving ==
 
== Recordings saving ==
RecordMAN2.client application enables to store recordings - downloaded from recording server – to disc of computer with launched application. To do this, specified recording on list of recordings downloaded from server, should be selected and button [[Image:RM2_save.PNG]] pressed. Selected recording will be stored in specified location as a .wav file. Mentioned above button is active only, if appropriate privileges are assigned to RecordMAN2.client application user. Detailed description of privileges possible to assign to RecordMAN2.client application user can be found in next chapter.
+
RecordMAN.client application enables to store recordings - downloaded from recording server – to disc of computer with launched application. To do this, specified recording on list of recordings downloaded from server, should be selected and button [[Image:RM2_save.PNG]] pressed. Selected recording will be stored in specified location as a .wav file. Mentioned above button is active only, if appropriate privileges are assigned to RecordMAN.client application user. Detailed description of privileges possible to assign to RecordMAN.client application user can be found in next chapter.
  
 
== User privileges ==
 
== User privileges ==
RecordMAN2.client application privileges for specified account (specified PC) are defined in ConfigMAN application by PABX admin. In chapter 2 there are described requirements for log in RecordMAN2.client application user to recording server. To enable application user to log into recording server, it is necessarily to create an account with user log-in and hardware identifier of PC with RecordMAN2.client installed. Additionally for this account recording access levels, internal line filter and how deep (how many days) from recording history recordings can be accessed. For every recording in system specified access level is assigned and only recordings with appropriate access level can be visible. In ConfigMAN application following settings can be defined for every account:
+
RecordMAN.client application privileges for specified account (specified PC) are defined in ConfigMAN application by PABX admin. In chapter 2 there are described requirements for log in RecordMAN.client application user to recording server. To enable application user to log into recording server, it is necessarily to create an account with user log-in and hardware identifier of PC with RecordMAN.client installed. Additionally for this account recording access levels, internal line filter and how deep (how many days) from recording history recordings can be accessed. For every recording in system specified access level is assigned and only recordings with appropriate access level can be visible. In ConfigMAN application following settings can be defined for every account:
  
* '''Full access''' – all recordings can be accessible for specified RecordMAN2.client account.
+
* '''Full access''' – all recordings can be accessible for specified RecordMAN.client account.
 
* '''Restricted access''' – for specified account can be defined all conditions which must be fulfilled by recordings, to access recordings from this account. Mentioned above conditions are following:
 
* '''Restricted access''' – for specified account can be defined all conditions which must be fulfilled by recordings, to access recordings from this account. Mentioned above conditions are following:
 
** '''Recording access levels''' – for specified account only recordings with access levels coherent with account access levels.
 
** '''Recording access levels''' – for specified account only recordings with access levels coherent with account access levels.
 
** '''Internal line filter''' – if in this field extension number is entered, only recordings established with this number as will be visible for specified account.<br/> Settings of both above fields operate together, if in first field you define levels A and B, while in second field number 100 is entered, accessible will be only recordings with access level A and B, established with extension number 100.
 
** '''Internal line filter''' – if in this field extension number is entered, only recordings established with this number as will be visible for specified account.<br/> Settings of both above fields operate together, if in first field you define levels A and B, while in second field number 100 is entered, accessible will be only recordings with access level A and B, established with extension number 100.
 
** '''Number of days from recording history''' – in this field you can defined number of days from recording history for which recordings will be accessible for specified account.  
 
** '''Number of days from recording history''' – in this field you can defined number of days from recording history for which recordings will be accessible for specified account.  
* '''No access''' – by setting this option, RecordMAN2.client application user after connecting to recording server will be see the message '''You have no privileges to view recording archive'''. This option can be used for temporarily lock an account. Due to this option account can be locked an after some time unlocked without necessity of resetting all parameters.
+
* '''No access''' – by setting this option, RecordMAN.client application user after connecting to recording server will be see the message '''You have no privileges to view recording archive'''. This option can be used for temporarily lock an account. Due to this option account can be locked an after some time unlocked without necessity of resetting all parameters.
 +
=Using application outside the local network=
 +
RecordMAN.client application is  destined to be used in LAN network and due to security reason it id not recommended to use it in WAN.<br>
 +
Although, if it is necessarily it can be realized by using three methods:
 +
* By setting LAN card mode to Router and connecting public access to WAN socket. In such configuration only encrypted redcordings should be used.
 +
* By creating virtual private network VPN in location where application should be installed. Concerning method of creating such network you should contact with LAN admin.
 +
* By using RecordMAN.server application working i appropriate configuration.
 +
** RecordMAN.client application - it is recommended to change port used to communication with server, from 21 to any another if in LAN network exists any other FTP server or any service using port 21.
 +
** RecordMAN.server application - it is necessarily to limit passive port range and change of listening port if such change was made in RecordMAN.client application.
 +
** introduce some changes in firewall, to assure connection between client and server application.
 +
To obtain full information about configuration method of recording system for maintaining from outside of LAN network, please contact with PBX admin.
  
 
=Previous version =
 
=Previous version =
Instruction for previous version of RecordMAN2.client you can find [[RecordMAN2 v1.01|here]]
+
Instruction for previous version of RecordMAN.client you can find here:
 +
* [[RecordMAN2 v1.01|version 1.01 for firmware 4.02 to 4.07]]
 +
* [[RecordMAN2 v1.02|version 1.02 for firmware 4.10]]
  
 
<center>„Manufacturer reserves right to make changes without prior notification.”</center>
 
<center>„Manufacturer reserves right to make changes without prior notification.”</center>

Latest revision as of 07:40, 15 July 2011

RecordMAN.client
Instruction manual
Issue 1.03 for version 3.00


Dla wersji firmware od 4.11
Data aktualizacji 14 07 2011

Introduction

RecordMAN.client application can be used for recording and listening phone calls realized using embedded recording (EbdRec) system installed in Slican PABXes. RecordMAN.client application, after defining recordings server address and appropriate access parameters, log into server and download its content, presenting list of recordings which can be listen or save in location defined by user (under only one condition, PABX admin assigned appropriate privileges in ConfigMAN application). Complete description of functions and configuration of embedded recording system installed in Slican PABXes can be found in ConfigMAN programming instruction. As recordings server any Slican PABX (CXS-0424, CCT-1668, MAC-Zero or MAC-6400) or PC with RecordMAN.server application installed (description of this application functionality can be found in appropriate instruction manual) can be used. Using RecordMAN.client application, it is possible to listen recordings stored in local archive create earlier using this application. Chapter 2 describes requirements needed to using any of mentioned recordings source.

Hardware requirement

  • Operating system - Windows 2000/XP/Vista/7
  • Processor Pentium 300MHz or better
  • At least 128 MB RAM memeory
  • At least 5GB free space on hard drive

Software requirement

If firmware 4.10 is installed in PBX, to download recordings from PBX or recording server it is necessarily to use software in version 3.00. Software in this version is compatible with previous firmware version and can be used with versions earlier than 4.10. In this situation it is necessarily to check field Compatibility mode in window Application settings>Application. This field is presented on below figure.

RM Settings.JPG
Fig. 1 Window Application settings>Application

Field Password is not used and loggin can be peformed according Login and hardware key.

RecordMAN.client application configuration

During first launching of RecordMAN.client application unique hardware key is generated - HardKey, this key enables access to recordings only from specified PC. Info about HardKey is uploaded to PBX automatically during first recording downloading from PBX. It is always possible to compare this key with data downloaded from PBX using ConfigMAN. Hardware key generated during application installation is presented in window visible on figure 6. The same hardware key should be entered in ConfigMAN , sheet Embedded recordings/RecordMAN.client accounts.
During first launching of RecordMAN.client application following window appears:

Io rm2 welcome window.png
Fig. 2 Welcome window for first application launch

If you choose „Run authorization wizard” option, procedure of setting parameters and first log-in to PBX is started. Below figure presents authorization wizard window, while authorization procedure is presented in next text:

RM2 authorization wizard.PNG
Fig. 3 Authorization wizard window
  1. From PBX admin you should gain information concerning PBX IP address and enter it into field Address of the server.
  2. PBX admin should create new record in sheet Embedded recordings/RecordMAC.client accounts and enter data into fields Log and Pss and inform RecordMAN.client user about these data
  3. RecordMAN.client user should enter these data to appropriate fields in authorization wizard window. After fulfilling above mentioned fields and pressing Next following window will appear:
    RM2 configuration finish.PNG
    Fig. 4 Hardware identifier of PC with RecordMAN.client installed

  4. Authorization process was finished. After pressing Close button application start window including authorization data can be visible:
Io rm2 after.png
Fig. 5 Main window visible after finishing configuration

Window visible above is very similar to widow presented on figure 1. However it is possible now to download data from defined previously recording server. Additionally instead of „Run authorization wizard” button, information about authorization data is presented. Entered data can be always changed after pressing Settings button. In window (visible on figure 5) which appear after pressing Settings button there is possible also change server which RecordMAN.client log into.

Operation with recording server

Log into PABX

Log-in to PBX can be performed as follows:

  1. First log-in into the server should be always executed with PBX, not with application RecordMAN.serwer, it assures uploading into PBX hardware key which was generated during installation process.
  2. Process of uploading hardware key is described in chapter RecordMAN.client application configuration. This key is visible in Application settings window and by pressing button located near field with hardware key is copied into clipboard, from clipboard it can be pasted in any place. Hardware key enables to log-in only from PC with appropriate hardware key.
  3. Before downloading recordings from server, RecordMAN.client forces primary password (granted by PBX admin) change and new password is uploaded to PBX. Due to this operation also PBX admin doesn't know this password, because in ConfigMAN this password is presented as * (asterisk) string.

As mentioned above, after pressing Settings button, new window appears, where change of recording server is possible.

Io rm2 aplication settings.png
Fig. 6 Settings window

In this window all configuration data (except password) are visible - this password is known only to authorized person. If in field Address of recording server PBX IP address is entered, PBX with this address is recording server, under condition that in sheet Embedded recording / RecordMAN.client accounts, in ConfigMAN application following identical data are entered:

  • login,
  • password and
  • hardware identifier shown in window above.

Log into RecordMAN.serwer application

If in window visible on figure 6, field Address of recording server is fulfilled with IP address of computer with RecordMAN.server application installed, RecordMAN.client application connects to this computer an reads data downloaded from PABX. Login and password should be the same as defined in PABX. There is a possibility of reading data from server installed on the same computer as RecordMAN.client application. To do this, field Select server type should be fulfilled with option Local server. In this situation also entering login and password is required.

Recordings archive

After selecting option Local disc from File menu special browse window with list of folders is displayed, in this widow RecordMAN.client user can select a location on disc, to store recordings archive. After selecting folder with name Data, including day folders with call recordings, all recorded calls will be show in application main menu. Until option EbdRec server from File menu is selected, all operations are executed on recordings files stored in recordings archive.

Recordings operation

Independent on recordings server (PABX, remote server, local server, local disc) in main window you can see recordings available for RecordMAN.client user. On the left side of window, list of day folder is visible and in the main part of window you can see the recordings included in selected day folder. In the pane on the right side there is visible legend with descriptions used for stored recordings.

Io rm2 main window.png
Fig. 7 Main window of RecordMAN.client application

RecordMAN.client application user can see in main window only recordings according his/her access privileges granted in ConfigMAN application. These privileges are detailed define in chapter 3.4. At the bottom of RecordMAN.client application main window, there are standard icons for play, stop and wind back or wind forward selected recordings, as also store recordings to computer disc as .wav file. Detailed description of actions, which can be executed is included in next chapters.

Recordings filtering

As presented on fig. 6, in main window of RecordMAN.client application there is a filtering pane, which enables to select specified recordings from all available for user.

Io rm2 recording filter.png
Fig. 8 Recordings filtering pane

For searching recordings following fields are used:

  • Internal sub. – after entering a PABX extension number into this field and pressing Filter button, all calls with specified extension number as a part of this call will be selected. If in this field several extension numbers, separated by spaces, are entered, selected will be all calls with at least one of above mentioned extension numbers as a part of call.
  • External sub. – after entering this field with any external number, selected will be all calls with this number as one of call part. Similarly as for Internal sub. field, if you enter several external numbers, separated with spaces, selected will be all calls with at least one of above mentioned numbers as a part of call.
  • Connection – in this field you can select one of five possible options, depending on kind of call. Possible are following options: incoming, outgoing, internal, or transit. If call type isn't important, option all should be checked.
  • Time period – in this field you can define time period when searching call started.
  • Only selected call – if this field is checked and you select specified records from list of recordings, application searches all recordings created during call including selected recording, if call was transferred there are more than one recordings created during this call.

After fulfilling all fields, which are important for searching specified call or calls, press Filter to execute search according defined conditions.

Example: If in field Internal sub. there is number 105, field External sub. is empty, option outgoing is selected in field Connection and period from 9:00 to 11:00 is entered to field Time period, after pressing Filter button all outgoing calls established between 9:00-11:00, dialed from extension number 105 will be search.

Defined search conditions are valid independently on selected day folder. So, if you change day folder, only calls according filter conditions will be selected and shown. Pressing Reset button filter condition settings will be erased. After erasing filter condition settings all recordings from selected day folder will be shown.

Attention!

After checking field only selected call there is no necessary to press Filter button. Application automatically shows recordings, which are parts of the same call.

Recordings playing

It is possible to make following operations:

  • After pressing RM2 play.png button, recording will be played.
  • After pressing RM2 stop.png button, just played will be finished.
  • After pressing RM2 pause.png button just played recording will be stopped. Next pressing this button will resume playing.
    Next group of buttons can be visible only after selection of recording stored as a several files (transfered between subscribers). Following operations are possible:
  • After pressing RM2 back.png button previous recording of specified call will be selected. This button is not active if selected recording is first recording of specified call.
  • After pressing RM2 back2.png button, selected recording will be reviewed by 15s.
  • After pressing RM2 fwd2.png button, selected recording will be forwarded by 15s.
  • After pressing RM2 fwd.png button next recording of specified call will be selected.

Recordings saving

RecordMAN.client application enables to store recordings - downloaded from recording server – to disc of computer with launched application. To do this, specified recording on list of recordings downloaded from server, should be selected and button RM2 save.PNG pressed. Selected recording will be stored in specified location as a .wav file. Mentioned above button is active only, if appropriate privileges are assigned to RecordMAN.client application user. Detailed description of privileges possible to assign to RecordMAN.client application user can be found in next chapter.

User privileges

RecordMAN.client application privileges for specified account (specified PC) are defined in ConfigMAN application by PABX admin. In chapter 2 there are described requirements for log in RecordMAN.client application user to recording server. To enable application user to log into recording server, it is necessarily to create an account with user log-in and hardware identifier of PC with RecordMAN.client installed. Additionally for this account recording access levels, internal line filter and how deep (how many days) from recording history recordings can be accessed. For every recording in system specified access level is assigned and only recordings with appropriate access level can be visible. In ConfigMAN application following settings can be defined for every account:

  • Full access – all recordings can be accessible for specified RecordMAN.client account.
  • Restricted access – for specified account can be defined all conditions which must be fulfilled by recordings, to access recordings from this account. Mentioned above conditions are following:
    • Recording access levels – for specified account only recordings with access levels coherent with account access levels.
    • Internal line filter – if in this field extension number is entered, only recordings established with this number as will be visible for specified account.
      Settings of both above fields operate together, if in first field you define levels A and B, while in second field number 100 is entered, accessible will be only recordings with access level A and B, established with extension number 100.
    • Number of days from recording history – in this field you can defined number of days from recording history for which recordings will be accessible for specified account.
  • No access – by setting this option, RecordMAN.client application user after connecting to recording server will be see the message You have no privileges to view recording archive. This option can be used for temporarily lock an account. Due to this option account can be locked an after some time unlocked without necessity of resetting all parameters.

Using application outside the local network

RecordMAN.client application is destined to be used in LAN network and due to security reason it id not recommended to use it in WAN.
Although, if it is necessarily it can be realized by using three methods:

  • By setting LAN card mode to Router and connecting public access to WAN socket. In such configuration only encrypted redcordings should be used.
  • By creating virtual private network VPN in location where application should be installed. Concerning method of creating such network you should contact with LAN admin.
  • By using RecordMAN.server application working i appropriate configuration.
    • RecordMAN.client application - it is recommended to change port used to communication with server, from 21 to any another if in LAN network exists any other FTP server or any service using port 21.
    • RecordMAN.server application - it is necessarily to limit passive port range and change of listening port if such change was made in RecordMAN.client application.
    • introduce some changes in firewall, to assure connection between client and server application.

To obtain full information about configuration method of recording system for maintaining from outside of LAN network, please contact with PBX admin.

Previous version

Instruction for previous version of RecordMAN.client you can find here:

„Manufacturer reserves right to make changes without prior notification.”