Recording tab under the phonebook looks faulty

johnatan

Hi Nicolas,

I updated our office FOP2 to the 2.22 release.
Everything working perfectly fine except the recording tab under the phonebook.
There is no any recorded call there but in the PBX var/spool/asterisk/monitor folder I have more than 100 call.

What need to change to see these recorded calls?

The FOP2 is brilliant.

Regards,
Johnatan

nicolas

You must uncomment the monitor_exec line included in the fop2.cfg from 2.22

monitor_exec=/usr/local/fop2/recording_fop2.pl

johnatan

The line uncommented in the: /usr/local/fop2/fop2.cfg
The server restarted but under the "Recordings" tab I still can't see any recorded call.

I tried to reinstall the complete FOP2 but the Recordings tab still not working.

Any advise?

Regards,

Johnatan

nicolas

If you use your own database credentials, you might need to revise you have the proper permissions and table. The latest fop2 will use the freepbx "asterisk" database for its own tables (visual_phonebook and fop2recordings), instead of requiring a separate database.

The scripts will try to use what you have in freepbx configured for mysql instead of your own database/credentials, so it is much easier to setup for new users (no need to tweak/handle mysql permisisons). But if you want to go with your own, you might be lacking permissions to the proper tables, etc. It is not easy to troubleshot via forum nor email.

One thing to verify: Check the permissions for the recordings_fop2.pl script, it must be executable and owned by the asterisk user.

vtecchump

Can you somehow provide a tutorial on how to enable recordings to show under recordings tab.

I have just setup a new test PIAF and bought your license. I would like to have all recordings (all extensions) that are in var/spool/asterisk/monitor to show up under the tab .

nicolas

Can you somehow provide a tutorial on how to enable recordings to show under recordings tab.

I have just setup a new test PIAF and bought your license. I would like to have all recordings (all extensions) that are in var/spool/asterisk/monitor to show up under the tab .

Hello,

The recordings tab will show ONLY recordings that are initiated via fop2, not all your pbx recordings. To enable that you have to uncomment the 2nd monitor_exec line in fop2.cf:

;monitor_exec=/usr/local/fop2/recording_fop2.pl

Best regards,

vtecchump

Thanks for your reply.

I was under the assumption that FOP2 could somehow recognize the filename in /var/spool/asterisk/monitor and show them in the recordings tab.

Right now I have a queue that records and dumps the recording in /var/spool/asterisk/monitor and the queue manager would like to have easy access to all recordings for this queue.

Can FOP2 be modified to do this? The filename of a sample recording is below:

q700-20111214-131334-1323886414.3.wav
"Queue 700 - Date - unknown - unknown.unkown.wav"

nicolas

Looking for files on hard disk is bad design. Fop2 will not work that way. You can write your own post recording script so it updates the fop2recordings table in your asterisk database. So, it is possible, but you will have to write the post processing script. The one included in fop2 only works for fop2 based recordings because is fop2 that sets the recording script to execute and it uses the filename as a base to extract key fields like src and destination extensions. That script will not work with standard freepbx recordings because of the filename. Anyways, it should be possible to write a general freepbx script to popupate the fop2recordings table..

londony

Sorry to "wake up" such an old post but does someone have such a script? I would also appreciate seeing on call recordings in FOP2.

nicolas

The problem is that there is not enough metadata to insert into the fop2recordings table. In fop2 there is always a recording 'owner', the extension that initiates a recording becomes an owner and has the right to see it, while others don't.

When you inititate a recording from the pbx itself, there is no owner, also, many times you are not sure about the target extension to use, etc.

So you will have to make compromises, either hardcoding an owner, or modifying also the fop2 recordings interface (recordings.php) to not perform restrictions based on owner.