On Tue, 2008-06-17 at 08:44 -0400, Carolyn Beeton wrote: > In another post, Scott said: > > > I think that the (single) target address should be a sipXsupervisor > configuration parameter. > > I'm not sure I understand what you mean by this. It is currently > configured in the alarmDef.xml config file, where other things such as > whether notifications are enabled are also stored. These settings will > be exposed by the GUI. > Did you have some other place in mind?
What reads alarmDef.xml ? If it's just sipXsupervisor, that's all that I meant. Kathy Eccles and I are getting started on a set of issues that will end up restructuring much of sipXsupervisor, so we'll need to be careful not to trip over each other on this... > And should the default be <none>, or [EMAIL PROTECTED] I think the existing default is ok. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
