Commit 8bfd195d authored by Etienne Allovon's avatar Etienne Allovon

3104 - update and enhance recording configuration and description

Move Gateway recording in a separate file.
Tried to enhance titles/toc for this recording topic.
Better split the recording activation (on the PBX) from the recording
features of the recording server itself.
parent f697978f
.. _recording_configuration:
***********************
Recording configuration
***********************
*********
Recording
*********
This page describes how to configure the recording feature.
.. contents:: :local:
Configure recording
===================
Recording Configuration
=======================
.. note:: Recording can also be activated on the *XiVO Gateway*.
For this, you need to follow the following guide:
.. toctree::
recording_on_gateway
To configure recording there are two steps to follow on *XiVO PBX*:
......@@ -36,7 +43,7 @@ During the configuration, you will be asked for :
* the *XiVO PBX* name (it must not contain any space or "-" character).
If you configure more more than one *XiVO PBX* on the same Recording Server, you must give a different name to each of them.
After having configured the recording, you have to enable it via sub-routines. See below.
After having configured the recording, you have to enable it in the Queue's configuration or via sub-routines. See below.
2. Enable recording
-------------------
......@@ -115,12 +122,52 @@ These subroutines are to be configured on the following *XiVO PBX* objects (eith
and set the field :menuselection:`Pre-process subroutine` to ``xivocc-incall-recording``
Recording Features
==================
.. _automatic_stop_start_rec_on_queues_conf:
Automatic Stop/Start Recording On Queues
----------------------------------------
By default recording is stopped when a call is transferred to a queues in *Not Recorded* mode (see the feature descriptiuon: :ref:`automatic_stop_start_rec_on_queues`).
This can be deactivated by adding ``ENABLE_RECORDING_RULES`` environment variable to the xuc section of your :file:`docker-xivocc.yml` file:
.. code-block:: yaml
:emphasize-lines: 1,7
xuc:
image: ...
environment:
- ...
- SECURED_KRB5_PRINCIPAL
- ENABLE_RECORDING_RULES
and ``ENABLE_RECORDING_RULES=false`` value to your :file:`custom.env`.
.. code-block:: bash
:emphasize-lines: 5
XIVO_HOST=192.168.1.1
XUC_HOST=192.168.1.2
XUC_PORT=8090
...
ENABLE_RECORDING_RULES=false
and then relaunch the xivocc services with ``xivocc-dcomp up -d`` command.
.. _stop_recording_upon_ext_xfer_conf:
Stop recording upon external transfer
-------------------------------------
By default recording is stopped when both parties of the call are external.
By default recording is stopped when both parties of the call are external (see the feature descriptiuon: :ref:`stop_recording_upon_ext_xfer`).
This can be deactivated by adding ``STOP_RECORDING_UPON_EXTERNAL_XFER`` environment variable to the xuc section of your :file:`docker-xivocc.yml` file:
......@@ -154,7 +201,7 @@ and then relaunch the xivocc services with ``xivocc-dcomp up -d`` command.
.. _recording_filtering_configuration:
Recording filtering configuration
=================================
---------------------------------
.. note:: Steps to be done on **XiVO CC**
......@@ -190,21 +237,3 @@ to be excluded from recording on outgoing calls. These numbers will be checked b
.. note:: check is made against XIVO_SRCNUM dialplan variable.
.. _recording_gw_configuration:
********************
Recording on gateway
********************
Recording can be enabled on a gateway instead of the XiVO PBX where the users, queues and other objects are configured. This architecture will allow to off-load the recording process to a gateway server. To configure recording on a gateway, you need to follow the process to enable recording via subroutines (see :ref:`enable_recording_via_subroutines`).
In order to allow agents to control the recording of their current call, you need to perform the following steps:
* Copy the following file `/etc/asterisk/manager.d/02-xivocc.conf` from the XiVO PBX to the same folder on the gateway.
* On your XiVO gateway, configure your operators' trunks and the trunk to your XiVO [1]_.
* On your XiVO PBX, configure the gateway as a media server in `Configuration/Media servers`
* On your XiVO PBX, configure your operators' trunks of your gateway and assign it to the media server configured for your XiVO gateway [1]_.
* Disable the feature to stop recording upon external transfer (see :ref:`stop_recording_upon_ext_xfer_conf`, `STOP_RECORDING_UPON_EXTERNAL_XFER=false`)
* Configure recording as per :ref:`enable_recording_via_subroutines`
.. [1] Please note that you need to do this configuration both on the XiVO PBX and on your gateway as no synchronization mechanism exists at the moment.
.. _recording_gw_configuration:
********************
Recording on gateway
********************
Recording can be enabled on a gateway instead of the XiVO PBX where the users, queues and other objects are configured. This architecture will allow to off-load the recording process to a gateway server. To configure recording on a gateway, you need to follow the process to enable recording via subroutines (see :ref:`enable_recording_via_subroutines`).
In order to allow agents to control the recording of their current call, you need to perform the following steps:
* Copy the following file `/etc/asterisk/manager.d/02-xivocc.conf` from the XiVO PBX to the same folder on the gateway.
* On your XiVO gateway, configure your operators' trunks and the trunk to your XiVO [1]_.
* On your XiVO PBX, configure the gateway as a media server in `Configuration/Media servers`
* On your XiVO PBX, configure your operators' trunks of your gateway and assign it to the media server configured for your XiVO gateway [1]_.
* Disable the feature to stop recording upon external transfer (see :ref:`stop_recording_upon_ext_xfer_conf`, `STOP_RECORDING_UPON_EXTERNAL_XFER=false`)
* Configure recording as per :ref:`enable_recording_via_subroutines`
.. [1] Please note that you need to do this configuration both on the XiVO PBX and on your gateway as no synchronization mechanism exists at the moment.
......@@ -4,25 +4,30 @@
Recording
*********
*XiVO CC* includes a call recording feature: recording is done on *XiVO PBX* and recorded files are sent to the *XiVO CC* Recording server. It's possible then to search for recordings and download recorded files from *Recording server*. If connected user is an administrator, he will be able to download also an access log file that track all action made on files by all users having access to recording server.
*XiVO CC* includes a call recording feature:
* recording is done on *XiVO PBX* (or the XiVO Gateway)
* and recorded files are sent to the *XiVO CC* Recording server.
Recording
=========
It's then possible to search for recordings and download recorded files from *Recording server*.
If connected user is an administrator, he will also be able to download an access log file that tracks all actions made on files by all users having access to recording server.
.. contents:: :local:
For configuring this feature, see :ref:`recording_configuration`.
Recording Server
================
Recording must first be enabled on the *XiVO PBX*, see :ref:`recording_configuration`.
Description
-----------
Recording feature records the conversation between caller and callee and stores it on dedicated recording server. All the files are then available for download only for predefined *granted* users.
Recording is done on *XiVO PBX* and sent to *Recording server*. If recorded file can't be synchronized on *XiVO CC* Recording Server, files might be found on *XiVO PBX* in
When recordingis is enabled the whole conversation between caller and callee is recorded and then sent on dedicated recording server. All the files are then available for download only for predefined *granted* users (see :ref:`profile_mgt-profile`).
.. code-block:: bash
ls -al /var/spool/xivocc-recording/failed
These files will be automatically resynchronized from *XiVO PBX* to *XiVO CC* Recording server each night.
Search
------
You can then do following actions:
......@@ -34,6 +39,9 @@ You can then do following actions:
.. figure:: search.png
:scale: 100%
Disk Space
----------
On *Recording server*, one can monitor the space used by the audio files stored in ``Contrôle d'enregistrement`` menu.
.. figure:: store.png
......@@ -51,11 +59,21 @@ Any action made from the UI on a recording file (``result``, ``listen`` or ``dow
.. note:: This access log is defined to track information for 6 months by default.
Transferred calls recordings
----------------------------
Search and Display
^^^^^^^^^^^^^^^^^^
File Sync
---------
Recording is done on *XiVO PBX* and sent to *Recording server*. If recorded file can't be synchronized on *XiVO CC* Recording Server, files might be found on *XiVO PBX* in
.. code-block:: bash
ls -al /var/spool/xivocc-recording/failed
These files will be automatically resynchronized from *XiVO PBX* to *XiVO CC* Recording server each night.
Recording and Transfers
=======================
In case an agent has transferred a call to another queue, which was answered by the agent available in that queue, the recording feature will display both agents (name and number) in column **Agent**
and both queues (name and number) under column **File** in one recording.
......@@ -63,8 +81,10 @@ and both queues (name and number) under column **File** in one recording.
.. figure:: search-transfer.png
:scale: 100%
Stop/Start Recording
^^^^^^^^^^^^^^^^^^^^
.. _automatic_stop_start_rec_on_queues:
Automatic Stop/Start Recording On Queues
========================================
When a call enters a queue, the recording will be started (or not) according to the queue Recording mode (see :ref:`queue_recording_configuration`).
If this call is transferred to another queue, it will stop or start the recording according to the following table:
......@@ -81,11 +101,12 @@ If this call is transferred to another queue, it will stop or start the recordin
|*State* |*Disabled*| Stop recording | Stop recording | |
+------------+----------+-------------------+--------------------+----------------+
This behavior can be deactivcated, see :ref:`configuration section <automatic_stop_start_rec_on_queues_conf>`
.. _stop_recording_upon_ext_xfer:
Stop recording upon external transfer
-------------------------------------
Automatic Stop Recording Upon External Transfer
===============================================
Recording is stopped when both parties of the call are external.
......@@ -101,7 +122,7 @@ This behavior can be deactivated, see :ref:`configuration section <stop_recordin
Recording filtering
===================
For configuring this feature, see :ref:`recording_filtering_configuration`.
To configure this feature, see :ref:`recording_filtering_configuration`.
Description
-----------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment