I am seeing some things which are not quite right when I add a new email contact for alarm notifications.
It does not "take". One problem is, sipXconfig does not call the xmlrpc "reloadAlarms" interface when the Apply button is pressed (or at least, the supervisor is not receiving the reloadAlarms). Unless we have another mechanism of letting the supervisor know that it should reload the xml files? (do we have an ability to monitor file changes?) Even after restart, I only see an email to [EMAIL PROTECTED], not the configured email address.This, even though the etc/sipxpbx/alarm-config.xml file has the correct information, and manually kicking the reload through sipx-alarm --reloadAlarms loads it properly. Part of the problem might be that the alarm config xml files are listed as dependencies of the sipXproxy process, not the supervisor. Part of it might be that the supervisor does not itself wait for files to be generated by sipXconfig. But I don't understand where it is getting the [EMAIL PROTECTED] from, when I deleted it through the GUI, unless a default version of the file is generated and then overwritten during startup. Thoughts? Carolyn
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
