23 mar 2010 kl. 22.20 skrev Kevin P. Fleming: > Steve Edwards wrote: > >> It may not be as intended, but from a "user" standpoint, it seems logical >> and convenient to establish "policy" in [general] and make exceptions in >> the entities as needed. > > Right... for when you have one policy. When you have two policies, each > that apply to a dozen or more entries in the config file, then it really > doesn't help, it harms. Templates solve that problem completely, because > each policy can be its own (named!) template, and they can be combined. > Since templates are also very easy to use for the single policy case, > they are a better solution to teach people (and they're also easier to > implement in the configuration code of the module). > > In other modules created since chan_sip, we've intentionally avoided > this problem, and you'll note that in nearly every other module, the > [general] section is exactly that; general settings for the module, and > not defaults.
In my NACL work, I implemented a channel-wide NACL for blacklist purposes. /O -- _____________________________________________________________________ -- 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
