A problem that I have always had with AMI events is that they are not controllable at a very fine level. As an example, turning on call class gives WAY more that one might always want. I had posted a patch some time ago that added a new class. The patch was rejected with a comment that some work would be undertaken for 1.8 that would allow finer control. As I am using the ABE version of asterisk I have not looked at 1.8 to see if anything has been done.
It would be very useful if there was more control over which events one sees. As I recall all the events have a name and if one could somehow say I want to see events with names x,y,z and forget the whole class mess. That way if you want to see some specific events but not others you could get what you want. I know this does not answer you question but I for sure feel your pain. -- Jim Dickenson mailto:dicken...@cfmc.com CfMC http://www.cfmc.com/ On Dec 3, 2010, at 10:36 AM, Frank Church wrote: > I am logging events from the AMI and the PeerStatus and Registry > events show that the privilege for them is System,All. > > Can a lower set of privileges be used? All looks pretty high to me. > > /Frank > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
