Hi Dan,

Your requests are kind of mutually exclusive, having fop2 recordings tab interface or having fop2 recordings appear on the recordings tab in Elastix.

If you installed fop2 from the Elastix RPM, the native fop2 recording interface is disabled, as Elastix requested to not duplicate resources. Both the fop2 phonebook and fop2 recording interface are not available in the Elastix RPM.

So, we are left with the option of making fop2 recordings appear in the Elastix recoridngs interface, unfortunately I am not an Elastix expert, I am not sure what are the requirements in the elastix recording interface so it is shown. In fop2 you can change the recording file name, and you can execute post recording scripts. Perhaps you can choose a recording filename wisely so it appears on the Elastix monitoring tab, or perhaps you not only need to change the name but also run some post recording script to update a database entry.

I will have to talk to Elastix guys to try to make it work.

I will add a script to update the cdr with the audio file link (required by the elastix monitoring tab), in the next elastix rpm update. It is not that hard to write the script, but requires some knowledge and coding experience.

Best regards,

The fop2 version 2.25 tarball includes a script recordings_elastix.pl that you can use as the monitor_exec setting in fop2.cfg

you have to check the cdr table and see if the userfield is being updated with audio:filename-of-recording , that is the important part to make them appear on the monitoring tab.

The only way to truly troubleshot is to run the script as asterisk with the same parameters, you can see that system call on the asterisk full log when you enable debug. The problem is that the script mixes the two legs and remove the original wavs to leave the mixed one, if that part works, you cannot rerun the script as it will not find the original audio files. So you will have to edit the script, comment the lines that remove leg A and B so the files remain when you try to run them by hand.

I have the same issue. When I click on the Voicemail tab none of the recordings show up, however I do see the recordings in the /var/spool/asterisk/monitor folder with the correct extension prefix.

How can we fix this? Thanks

Bill

Hi, not sure what "same issue" are you referring, this post talks about recordings, not voicemail tab. What tab are you referring too? From fop2 or from Elastix, or freepbx? Are you talking about ARI ?

Your problem is most probably the use/abuse of Local channels, where the call initially has a uniqueid but it changes to a different one do to a channel masquerading or similar.

It is not something that can be easily fixed, as the manager monitor application uses the monitor app (instead of mixmonitor), and I am not sure if we can pass arguments to be expanded when the call ends (and not when the recording starts/middle of call).

Mixmonitor has the option, but not sure if Monitor does. So, the script is ok, but the uniqueid does not match the cdr uniqueid and that is why the field is not populated. You could modify the script to do a fuzzy search of sorts, using src, dst, and aproximate uniqueid and timestamps, but it won't be too nice imho.

I am reviewing events and code, and I think the problem might be the channel you are monitoring. If you start recording on the channel that receives the call (leg B), the filename will have the uniqueid of that channel, but the cdr is saved with the uniqueid of the originating channel (leg A).

Try starting a recording for an extension that is doing an outgoind call and check uniqueids, then do it when you receive a call. Do you see the difference in the later case?

I am working on a fix, so fop2 sends the other leg uniqueid as a parameter to the post recording script. On my initial tests it seems to work, you should see it working on the next release. If you want to test it before release, catch me on the live help and I will provide a link to download a test version.

Regarding monitor_mix, it does not affect the script. If you set monitor_exec asterisk IGNORES the mix option, and records unmixed and passes 3 parameters to the script.

Best regards,

Yes, the issue is fixed on what it would be the next release. Just to be sure we are talking about this, I will describe the issue : using elastix and the update script provided for monitor_exec is that the recording appears depending on the call leg you start the recording in fop2. Suppose you have extension 100 talking to extension 200, and you start recording , it works when you record 100, but it does not work when you record 200. (actually , the recordings *are* made, but the uniqueid of the call does not match the cdr entry, and so the link is lost)

wait. wait. I smell a "I too have this problem" when you are actually not having the same problem.

One thing is not having the recordings populated in the recordings interface because you did not configure them, and a totally different thing is that you have SOME recordings on the *Elastix* recording interface (not fop2 interface) showing up when using the special purpose recordings_elastix.pl script supplied with the latest fop2 version.

If you do not see *anything* in the fop2 recordings interfaces then it is not the same problem, the most probable cause is what I said above, you did not configure the monitor_exec option in fop2.cfg.

Recordings, by default, are *not* enabled because they will most probably require some intervention from your part.

Look for this line in fop2.cfg,

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

remove the semicolon so it becomes active:

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

Then restart fop2:

service fop2 restart

After that, you *might* start seeing recordings that you initiate via fop2 in the recordings tab. If you have "all" permissions you will see all recordings, if not you will see only your own.

Best regards,