UPDATE… Hope this helps others and hope the developers of Freepbx run into this in case it’s a bug not a “feature”.
So, it is confirmed that the Post Call Recording Script field in the Advanced Settings does not interpret single or double quotes properly, instead, it inserts the ASCII code into the extensions_additional.conf therefore leaving it useless as any call truncates the call at the ASCII code.
The solution: Remove the entry from the post call recording field and set the MIXMON_POST variable manually in the globals_custom.conf file.
In my case, we are attempting to integrate with callcabinet for call recording analysis and reporting so our specific entry is:
MIXMON_POST = /home/callcabinet/moverecfreepbx.sh ^{MIXMONITOR_FILENAME} “^{AMPUSER}” ^{CALLERID(number)} ^{CDR(dst)} ^{CDR(start)} ^{CDR(src)} ^{UNIQUEID} “^{AGENTEXTEN}”
This resulted in a successful call even when some variables were empty as indicated in the logfile:
app_mixmonitor.c: Executing [/home/callcabinet/moverecfreepbx.sh /var/spool/asterisk/monitor/2019/05/19/in-2255324130-2252058967-20190519-090135-1558274495.9.wav “” 2252058967 recordcheck 2019-05-19 09:01:35 2252058967 1558274495.9 “”]
NOW TO FIGURE OUT WHY THE AMPUSER AND AGENTEXTEN FIELDS ARE EMPTY 