I wanted the files recorded via FOP2 to have a certain filename, I see variables listed for me to use inside fop2.cfg and after restart it seems to work great, my new filename is:

monitor_filename=/var/spool/asterisk/monitor/${ORIG_EXTENSION}_${DEST_EXTENSION}_${CLIDNUM}_%Y%m%d-%h%i%s_${UNIQUEID}

However, I noticed inside the recording_fop2.pl file that it says:

In fop2.cfg you MUST set the monitor filename and configurations to be:
#
# monitor_filename=/var/spool/asterisk/monitor/${ORIG_EXTENSION}_${DEST_EXTENSION}_%h%i%s_${UNIQUEID}

Now, when I access FOP2 recordings tab the field labels don't quite match contents, for instance using the above filename settings the Unique ID is not the new date format I added and the context is the unique ID variable (see screenshot - https://skitch.com/elijahlynn/g34i5/fla ... or-panel-2).

So my question is, should I not change the filename format? Or am I able to but need to do something else to accomodate the FOP2 recordings tab?

Any word on if this is officially going to cause problems?

Any word on if this is officially going to cause problems?

For anyone else wondering, it really works best if you don't change the filename and want your users to use the GUI. The filenames don't make as much sense if you pass them around via email but the GUI gives you good info and I think that is more important. I guess it would be nice if the GUI used a more descriptive format by default but that isn't something I am going to hack.

Here is a pic of how it looks if you custom name the files via my first post.

https://img.skitch.com/20120229-eidjh9tgg5qqgk4maswy8htkh2.png

edit: added screenshot