Vmnotify fails to run for vm from external calls

I’ve successfully used vmnotify for quite some time. Just recently had an end user tell me the vmnotify wasn’t working, which was a bit of a surprise given that this system is very much a ‘set it and forget it’ type system at this point. (The only thing that changes is that periodically I’d do updates.) After some troubleshooting, I’ve discovered that if I call and leave a vm in the monitored mailbox from an internal extension, vmnotify runs as expected. If I call from an external number or even call from an internal extension to the external did of the mailbox, the vmnotify doesn’t work. Watching the logs, I can see where the vmnotify doesn’t even execute for the external call.

I wasn’t running FPBX17 before this so I took the opportunity to backup and restore to a brand new install of FPBX17 but no change. I also tried setting up a different extension with vmnotify and it functions the same way. voicemail.conf has externnotify=/usr/sbin/fwconsole voicemail but I did try changing to /var/lib/asterisk/agi-bin/vmnotify-newvm.php just in case.

Logs:
working vmnotify (internal call to vm) vmnotify success - Pastebin.com
failed vmnotify (external call to vm) vmnotify failed - Pastebin.com

If anyone has an ideas, I’d be eternally grateful.

So this stopped working after updating to v17?

No, I updated to 17 hoping it would magically fix it.

Well the problem here is that your working example comes from v16 where the Macro() application is still being used. The one that doesn’t work is from v17 which replaced Macro() with Gosub(). We would need to see a working example on the v17 system.

Ok, I updated the original pastebin with a v17 working example.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.