Letting users access call recordings for their extensions

[jdc_eddie]

I have a client who wants to have his sales people be able to listen to their own call recordings.

I have come up with two possible options:

UCP is the ideal solution as each sales person can log in with their own extension and then view and listen to their own calls from there. The issue with this is that the client does a lot of paging and internal calling, and all those calls show up in UCP as well. This causes UCP to take around 2-5 minutes just to load one page, and because it’s so slow, the client refuses this option.

Call Recordings module would resolve the slowness issue, but even if I give the users access only to the Call Recordings module, they can view calls for all extensions, which wouldn’t sit well with the client.

Open to recommendations or suggestions.

[dobrosavljevic (Igor Dobrosavljevic)]

So yea, UCP sucks after a while because of how long it takes to load the cdrs. UCP is the correct answer here but what you probably want to do is go back purge old call records so that they don’t load in the UCP.

It sucks that this seems to be the only answer for this and is not a setting that can be adjusted to improve the performance of the UCP for individual users, it really does load all cdrs for the relevant extension at all times whenever you try and load it and performance really suffers.

[jdc_eddie]

What’s the best way to purge old calls?

I found the following comment from 2020, is the script you mentioned still the best way to do this?

UCP Call history slow to load

As a follow up. A support engineer helped by creating a script that we’ll run once a month that simply drops records older then two months, here it is for anyone else that’s running into the same problem and would like to implement the same solution: #!/bin/bash mysql -D asteriskcdrdb -e “DELETE FROM cdr WHERE calldate < DATE_SUB(NOW(), INTERVAL 2 MONTH);” mysql -D asteriskcdrdb -e “DELETE FROM cel WHERE eventtime < DATE_SUB(NOW(), INTERVAL 2 MONTH);” mysqlcheck --auto-repair --optimize --al…

[dobrosavljevic (Igor Dobrosavljevic)]

Ha! I completely forgot that I had posted about this and provided the workaround to the community. Yea, we still do this on that phone system. We just setup the thing to run in cron on an interval and they haven’t had any issues since.

I still wish there was an easier way to set a default date range for UCP to pull from instead of the default “Pull all every time the page loads!”

[ErikVandergeld]

You could use FOP2, where each user would have a login equivalent to their extension, and the users who have the “recordself” permission would listen only their own recordings in the “call recordings” menu option.

FOP2 naturally does not automatically display all recordings on this page, only those that the user records using the action button - but to make this automatic you just need to use a post recording script that takes the recordings (in fact, the path they are in) to the FOP2 database, where whoever has the “all” permission listens to all of them and “recordself” only listens to itself.

I have clients using it this solution to achieve that same goal and the results are very positive, its a nice option

[BlazeStudios (Tom Ray)]

Has fop2 moved that away from app_monitor? Cuz that will be a problem.

[jdc_eddie]

Is there any way, from within FreePBX, to remove internal calls from showing in call history?

[ErikVandergeld]

IIRC FOP2 stills uses the Monitor, PauseMonitor and UnpauseMonitor commands for recordings done by users clicking on the action button