> -----Original Message----- > From: Lawrence, Scott (BL60:9D30) > Sent: Monday, November 16, 2009 12:42 PM > To: Beeton, Carolyn (CAR:9D60) > Cc: [email protected] > Subject: Re: [sipX-dev] SNMP Trap Proposal > > On Mon, 2009-11-16 at 12:35 -0500, Carolyn Beeton wrote: > > > The Alarm Server was made part of the supervisor because > the existing > > xmlrpc interface made that logical. But does sipXconfig > have to model > > the service that way? Could it model the Alarm Server > separately, and > > perhaps implement "restart" for that service by doing "reloadAlarms" > > instead? > > Eventually, alarm definitions should probably be loaded from > a directory so that each service can provision its own... > >
Alarm definitions are read from a directory, and can be "dropped in" by any service. We started out with all the sipXecs alarms in sipXalarms-config.xml, but they could be split apart by service if we wanted. I don't think that would help sipXconfig, because what is causing (at least some of) the trouble for it is the top-level config file alarm-config.xml, which does not contain any service-specific settings, but rather global settings such as where emails are sent from, where alarms are logged, etc. _______________________________________________ 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/
