Reference13r1:Concept App Service Recordings: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 39: Line 39:
=== Installing the App Object on the PBX ===
=== Installing the App Object on the PBX ===


Prerequisite for installing and configuring the Recordings App Object is that an “AP” object is set up properly on the PBX and the user  has the pbxmanager app available (as required for configuration of all other app objects). Select the pbxmanager app, then the “AP recordings”:
Prerequisite for installing and configuring the Recordings App Object is that an “AP” object is set up properly on the PBX and the user  has the pbxmanager app available (as required for configuration of all other app objects). Select the pbxmanager app, then the “AP recordings”:


[[Image:Recordings4.png]]
[[Image:Recordings4.png]]
Line 74: Line 74:
[[Image:Recordings10.png]]
[[Image:Recordings10.png]]


In the above example the mode “transparent” is set so the recording starts automatically when the call is established. We recommend that the users phone beconfigured via a configuration script. Following is an example of script entries to configure recording on the phone with a function key for manual start/pause operation.
In the above example the mode “transparent” is set so the recording starts automatically when the call is established. We recommend that the users phone beconfigured via a configuration script or template.


Note: pressing the function key after recording has started pauses the recording, another press resumes recording until it stops when the call terminates.
Note: pressing the function key after recording has started pauses the recording, another press resumes recording until it stops when the call terminates.

Revision as of 13:34, 18 June 2019

Preliminary article. More infos will be added.

Recordings is an application running on the app platform which allows to capture the audio streams during a telephone call.

Applies To

  • innovaphone PBX from version 13r1

Apps

recordings

This is the standard UI App for Recordings.

recordingsadmin

This App will be used by the admin.

Description

  Recordings is an application running on the app platform which allows to capture the audio streams during a telephone call.

The users phone can be configured to forward the transmit and receive audio streams to the Recordings App which in turn stores it in a database.

Setting up

Setting up the Recordings App on the App Platform

On the App Platform click the “App Store”, find and install “Recordings”.

Recordings1.png

Now click “Add” to add an instance and fill the entries:

Recordings2.png

Save, then select the new instance and click Start. The Recording App on the App Platform is now up and running:

Recordings3.png

Installing the App Object on the PBX

Prerequisite for installing and configuring the Recordings App Object is that an “AP” object is set up properly on the PBX and the user has the pbxmanager app available (as required for configuration of all other app objects). Select the pbxmanager app, then the “AP recordings”:

Recordings4.png

Now you can configure a “User” object (TYPE selector) via which a user can access and administer his own recordings and/or an “Admin” object which allows the access to all recordings. “NAME” and “SIP” can be freely chosen. The “Licenses” entry specifies how many licenses from the installed Recordings Service License are allocated for this object. For example:

Recordings5.png

After pressing “Ok” the installed entry appears:

Recordings6.png

Note: The checkmark between “USER” and “10” indicates that the Pbx Object has successfully opened a connection to the Recordings App. Similarly an administrator object can be configured:

Recordings7.png

Note: The administrator does not claim licenses

The App is known to the Pbx under the “SIP” name. For the user to be able to use the app the checkmark must be set in the “Apps” tab:

Recordings8.png

Note: the “arecordings” aka AdminRecordings app and the “urecordings” aka UserRecordings app are enable for the User. Please do not get confused by the appearance of “recordings” and “recordingsadmin” in the selection. These are dormant leftovers from previous configurations

Setting up the users phone

In order to set up the users phone for recording the Record to (URL) entry must be set:

Recordings9.png

This entry consists of the app platform server address (http://172.16.67.100/) ,the “Webserver path” (as configured in Pic 2) and the “Files” submodule name. Furthermore, under “Recording” the “Recorder”: HTTP Server must be selected. The mode can be set as appropriate.:

Recordings10.png

In the above example the mode “transparent” is set so the recording starts automatically when the call is established. We recommend that the users phone beconfigured via a configuration script or template.

Note: pressing the function key after recording has started pauses the recording, another press resumes recording until it stops when the call terminates.

Setting up reporting to provide the recordings app with the call information

In order to have call information (caller name, number..) the reporting information must be passed from the pbx to the recordings app. If this is not configured the calls are still recorded but appear with “No CDR” indistinguishable on the GUIs. First enable CDR generation :

Recordings11.png

Then configure the cdr target:

Recordings12.png

“Type” must be “HTTP”. Address: the app platform server ip address, Port: must be 80 Method: must be “External(Post)” Path: the webserver path as configured in Pic 1 plus “cdr” as the submodulename

User and Admin GUI

User Gui

The User Gui allows a user to access the OWN recordings

He can listen, delete, filter through his records. Furthermore he can save the Record as wav file. Every record will be saved per default for 30 days in Recordings App. (This can be modified by the admin in Recordingsadmin App) If the user wants to save his Record for longer than he can press the lock symbol of his Record.

In the following picture we see the Gui showing one call:

Recordings13.png Pic 13

The GUI consists of a header containing a

  • Search field to the left
 The search can either be a search for names or phone numbers. The search is dynamic, so every every character or digit entered lists the matching substrings
  • followed by a Sort button “A-Z”/”Z-A”
 Sort the entries in ascending or descending order
  • and a “settings” button to the right
 the button opens a menu where display filters for name and/or recording periodcan be set:


Recordings14.png

The above example shows just one recording entry, which comprises of the following items:

  • an arrow indicating the call direction (bottom left to top right: outgoing, top right to bottom left: incoming).
  • The partners name and number
  • A conversion button
 Since the recordings are stored in pcap format and the respective codec used for the call, the recording must be converted to a wave file before it can be played back (or downloaded). Note: depending on the codec used during the call this conversion process can be time consuming. The  most time consuming codecs are: G729 and Opus.  
  • The date and time
 The date and time of the recording
  • A lock button
 The recordings are automatically deleted after a specific time which can be set in the Administrator GUI. If the user wants to avoid this and permanently flag the recording, this button can be engaed. The button appears Orange for permanently flagged recordings.
  • A delete checkmark
 To delete recording(s) they can be selected here, A confirm button triggers the deletion.


Conversion process

When pressing the conversion button a thread is started on the app platform for this purpose. The conversion button changes to a circling activity icon with the percentage completed indicator below. Multiple conversions can be started, however they are processed subsequently . Once the convertion process is completed the activity indicator changes to a download icon (to download the wave file) with the duration of the audio file underneath. Additionally a player interface opens in the recording item:

Recordings15.png Pic 15

The wave file generated by the conversion process is stored temporarily in the database to allow for subsequent access without the nessecity to go through the conversion process again. After a lifetime of 1 hour this temporary file is deleted and the player item in the recording entry disappears.


Admin Gui

TheAdmin Gui allows a user to access ALL recordings. Its layout is similar to the users Gui with the addition that both parties of the call are showm with the call initiator in the top row.:

Recordings16.png Pic16

The settings menu contains, besides the filter settings an item to configure the time how long the recordings are held in the database before they are permanently deleted:


Recordings17.png


Appendix