FOP2 Community Forum

It is already implemented: Event: UserEvent Privilege: user,all UserEvent: FOP2RELOADVOICEMAIL Action: UserEvent Mailbox: 606@default Or better: you can do it with no dialplan hacks by setting in voicemail.conf: pollmailboxes = yes ; If mailboxes are changed anywhere outside of app_voicemail, ; ; then this option must be enabled for MWI to work. This ; ; enables polling mailboxes for changes. Normally, it will ; ; expect that changes are only made when someone called in ; ; to one of the voicemail applications. ; ; Examples of situations that would require this option are ; ; web interfaces to voicemail or an email client in the case ; ; of using IMAP storage. ; pollfreq = 30 ; If the "pollmailboxes" option is enabled, this option ; ; sets the polling frequency. The default is once every ; ; 30 seconds. externotify is also used by some users.

There is no clever way right now to use hashed passwords. I do not remember the details, but it is not something simple to implement right now. FOP2 already uses/receives md5 hashed (and salted) passwords on the "wire", the salt changes on each action/request. So the hash sent via the string changes every time. .htpasswd can have different hashing algorithms specified so it is not something trivial at all to do. Best regards,

I do not know how do you have your buttons.cfg file set, perhaps you are missing the context on the mailbox. As I said before, mwi works in realtime if the event is sent properly. You can always start fop2_server in full debug mode to see what happens after the event is received, there are usually some lines that might give you an idea of what is wrong or going on, you can start fop2 in full debug with the command line options: -X 511 -l /tmp That will write a log file in /tmp (if you use version 2.26 log files are output.log and error.log, if you use 2.27 is only one log file named fop2_debug.log). Run in full debug and check the output ..