PBX Version:14.0.13.40
PBX Distro:12.7.8-2008-2.sng7
Asterisk Version:13.36.0
System modules up to date as of today.
Problem: Call files are only processed when pbx_spool.so loads. Then the call files just sit there until asterisk reload and pbx_spool.so is loaded. (I made that module no_load so I could load it and confirm the issue. The module does not allow re-load or un-load.)
When I load the module, all call files in outgoing are processed, but any new ones added just sit there.
That’s completely new. Have you submitted a ticket to go along with the support you might get from here?
To be clear - I’ve never heard of this problem happening. You are the first person I’m aware of that’s reporting it. If it was a common problem, the forums would be on fire!
It seems it must be an issue with my pbx_spool.so, so I replaced with copy form same version of 14 that is working, but it made no change. So I tested on that PBX 14.0.13.40 and same result – call file sat there. Then I tested on FreePBX 15.0.16.77 and — SAME RESULT! It worked on the next 14.0.13.40 I tried, so I copied the pbx_spool.so to the first machine and it still doesn’t work, so I am convinced it is not the module but some background or directory watching daemon that is not running. I have not used call files for a while except on that 3rd 14.0.13.40, and uses them constantly. But I am surprised no one else has complained of this when I can reproduce it on both 14 and 15 machines.
Anyone have a clue what be preventing pbx_spool.so from reading a call file from /var/spool/asterisk/outgoing?
CLI> module show like pbx_spool.so
Module Description Use Count Status Support Level
pbx_spool.so Outgoing Spool Support 0 Running core
1 modules loaded
@dicko That actually solved the mystery. The original issue was with a system that uses a PHP program executing system commands to move the files, and they were just piling up in outgoing. This was most likely solved by replacing pbx_spool.so, but I didn’t know my testing methodology was severely flawed. I was using WinSCP to move the files to outgoing on the other machines I tested. Your suggestion of inotifywait showed me that a WinSCP move does not produce the same output as when I use linux mv: then the output includes the filename and the call file is handled immediately by asterisk. Moral of the story: Don’t use WinSCP to move files to outgoing. Thanks again, dicko.