> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Kollipara, Seshu-Babu (AMR:9T40) > Sent: Tuesday, November 17, 2009 10:03 AM > To: Sipx-dev list; Campbell, Alfred (BL60:9D30) > Subject: Re: [sipX-dev] SNMP Trap Proposal > > >> I don't see what the problem is with the above; > > Please suggest which is a optimal design choice keeping in > mind the size/scope of snmp monitor task: > > 1.Implementing snmp alarm monitor into sipXsupervisor & > taking up the promotion of alarm server into normal > service as separate task later. Or 2.Promoting alarm server > into service first & put the snmp monitor functionality into > the new service. > > Thanks, > Seshu
It's completely out of scope for the snmp task. Add your bit into the existing infrastructure. If/when it gets reorganized, the snmp bit will come along for the ride. 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 sipXecs IP PBX -- http://www.sipfoundry.org/
