Hi all, Just want to draw your attention to some behaviour that may seem like a bug if you encounter it. But, I think it is an acceptable limitation.
With XX-6777 (thanks Dave!), as of revision 17480 the Alarm settings (Group & Min Threshold) are now persisted in the database. One minor limitation still exists. A re-install of sipXsupervisor will still always over-write the existing sipXalarms-config.xml with a default version. The configured values will be restored (from the DB) upon the next replication of this file. But (and here's the limitation), unless it is a formal upgrade situation, the next replication will not be done automatically. You need to trigger it manually: An Apply on the Alarm types table, or sipxconfig.sh --first-run (and sipXconfig restart) will do the trick. This isn't a problem when sipXconfig RPM is installed (such as formal upgrade), because there a sipxconfig.sh --first-run, which causes a replication. But, in developer environments (i.e. Makefile installs) this problem will show up every time sipXsupervisor is re-installed. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
