- Quick Start
- Server Setup
- User Management
- Telephone Book
- Team Management
- pascom Clients
- Trunk Templates
- Automatic Call Distribution
- Data protection and IT operations in the pascom cloud
- Monitoring via Nagios or Icinga
- Setup Mobile Access via the Internet
- Using a Lancom as a Router
- Subscription Downgrades
- Setup Extensions
- Remove Dialplan Loops
- Function / Service Codes
- Change SIP Header
- Mobile App Energy Optimisation Settings
- Telephone Provisioning via DHCP
- Support & Release Notes
- Developer APIs
Call Recording System+ Cloud and Self Hosted
HowTo record calls as a contractual quality and control tool or for training tool.
The recording of calls can be legally problematic, and in certain cases even a criminal offence. Depending on the scenario certain criteria must be fulfilled, such as Framework Conditions, Data Protection/Privacy Policies and Notification Obligations. In case of uncertainty and doubt, please seek legal counsel before using this service.
The recording system is based one of the many frameworks existing within pascom phone systems. This framework enables your pascom phone system to automatically record calls or to allow an user to manually start a recording.
Regardless of whether the recordings are manually or automatically initiated, they will be stored on the pascom HardDisk and be displayed to permitted users within the Classic Client. An additional option is for the recordings to be sent via the rule framework to any number of e-mail recipients or copied via script to any destination.
In order to activate the recording system, you must have created at least one rule whereby either specific calls will be automatically recorded or a predetermined group of users are allowed to manually initiate call recordings. To this end, you can add a new rule under the pascom Web UI menu tab > through using the button:
|Description||Description of the Rule|
|Rule enabled||Activate or Deactivate the Rule|
|What will be Recorded?||pascom automatically ensures that all call recordings will be automatically performed for the Role Members under “What will be Recorded?” Call Partners are permitted to effect recordings manually, who are selected as Role Members under the “What will be Recorded?” setting. This can then be done via the Classic Client or via the Record Button on support IP Telephones.|
|What is included?||The recording destination is role based. Select a Role and all members assigned with this role, regardless of whether they are individual users or whole teams will be included. The role itself does not require a specific role type, rather it serves a grouping purpose. Find out more under Concept: Roles.|
|Call Direction||Sets whether the service should be started for incoming calls only, outgoing calls only, or for both incoming and outgoing calls.|
|Origin||Only internal, only external or both internal and external calls should be recorded.|
|Dispatch Mode||As standard, all recordings will be saved on the pascom HardDisk and can be retrieved via the Classic Client. Additionally, one can send the recordings to any number of e-mail addresses or setup a process via a Bash-Script whereby the recordings will be copied to an alternate desitinate, e.g. an external file server. The sending is regulated via a Cronjob, which will be executed as standard once a day at 20:00 hours. For further details, please refer to Cronjobs for recordings below.|
Dispatch Mode: Bash Script
If the dispatch mode Bash script is selected, then a Bash-Editor into which one can enter the desired script will appear. The script will then be call up after every recording and the following parameters will be passed on, which can then be called up in the Variables $1 and $2:
Cronjob for Recording System
In order to execute the sending of recordings via e-mail or script as well as the clean up of the HardDisk (see HardDisk memory management), a Cronjob will be run at 20:00 hrs (default setting). All data relating to the sending will be saved within the system until runtime and then during the running of the Cronjob, the data will be processed using a batch mode.
This really only applies for the sending of recordings via e-mail or script. In the Desktop Classic Client the recordings will be displayed immediately after the recording has been made.
Should you need to, you can increase the frequency of the Cronjob execution (e.g. send the recordings every 15 Minutes) this can be modified under the > > > or alternatively > > .
HardDisk Memory Management (Onsite only)
Every recording, regardless of whether it was automatically or manually created, will be stored centrally on the pascom HardDisk. A recording that took 1 minute, will require approx. 1 MB of memory. So should you for example for training purposes need to continuously record the support team, which consists of 4 people who are on the phone for ca. 3 hrs per day, the recordings will require approximately 720 MB of HardDisk space, therefore, please ensure that you have sized your HardDisk memory accordingly.
In order to prevent the overflow of the HardDisk, we have setup the system so that it removes all recordings after 90 days as standard. This setting can be modified through using the pascom Web UI under > . Within the tree structure, you will find the expiration parameter under sys.monitor.configure.monitorcron, which has been set to 90 days but can be modified to any time period
Control Recordings via Variables
pascom additionally, provides the option of dynamically controlling (turning on/off) the recording system via DialPlan Variables e.g. by transferring existing rules.
For example, it could be the case that you would like to offer your callers an IVR Menu in which they can decide for themselves whether or not a call should be recorded for Quality Control purposes.
To this end, the DialPlan can be influenced according to needs through using the Variable MDC_MON_MODE:
Setting MDC_MON_MODE Variable in the Call Setup
|MDC_MON_MODE||not defined or Value=auto: Rule Framework accessed , (see below). DEFAULT|
|MDC_MON_MODE=force||This call will be recorded in every scenario (Skips Rule Framework )|
|MDC_MON_MODE=deny||This call will not be recorded under any circumstances (Skips Rule Framework )|
|MDC_MON_MODE=manual||Rule Framework will be skipped, manual recording will be enabled|
|MDC_MON_MODE=caller||records only caller voice|
|MDC_MON_MODE=callee||records only callee voice|
|MDC_MON_MODE=splited||records caller and callee but stores streams in separate files|
An example script for the blocking of call recordings could appear somewhat like:
exten => s,1,Set(\__MDC_MON_MODE=deny) exten => s,n,Return()
This script could be then be linked into the IVR Menu and thus through being selected deactivate the Recording function.
Configure Record Button on Telephones
Many Telephones have a record button, which will be, through pascom, automatically provided with the correct URL for controlling the Recording System. On Handsets that do not have an additional recording button, you can repurpose any button to control this function.
Central Distribution of Button Settings
The simplest method of doing this is through using the Provisioning System and assigning the following value to a button::
Individual Button Settings Direct from the Telephone
Alternatively, you can also assign the following Actions Type URL to a Telephone button, whereby you will have to replace the PASCOM_SERVER_IP with the concrete IP-Address of the pascom-Server:
Manage Recordings from the Client
Allows a user who is through a rule permitted to manually record, and during a call a red Record symbol will become visible within the Classic Client, which will start a recording:
Should a recording have been made, you can access it retrospectively from your Journal through the REC symbol: Through clicking on the REC Symbol all the recordings from this Call will be then be displayed:
Through clicking on the Play Symbol you can listen to the recording directly from your client as well as being able to download it via the download symbol.
Manage Recordings via REST API
Via the REST Interface, you can set various queries and parameters for monitoring and downloading conversation recordings. Below is a example URL that needs to be adjusted with your parameters.
- https://$ip/$instance/services/monitor/r_$recordID/$ruleID/1/wav -> Anrufer Gesprächsdatei
- https://$ip/$instance/services/monitor/t_$recordID/$ruleID/1/wav -> Teilnehmer Gesprächsdatei
Using the interactive REST documentation of the pascom system, you can test queries and adapt them accordingly.