On Monday 12 December 2011 4:28:17 am Harel Cohen wrote: > Danny, > > Why would you think this is a "circumvent"? I'm using a nice feature of 1.8 > where I can create any CDR field I like and populate it by using the > CDR(<fieldname>) function. While all other fields that I created are > populated properly (however before the 'dial' commences) it seems like at > this point of the dial plan the CDR is closed for editing even though I > configured endbeforehexten=no in my cdr.conf.
I agree, this is a perfectly valid use of the CDR. I do the same thing, btw. I think what you are seeing is that when your call starts, Asterisk creates a record, either in memory, or in a db transaction. When the call is torn down, the record is updated and committed to the db. The down-shot is that any changes you make to the db record get clobbered by this last update. I ended up making some of my updates in the hang-up phase via the "h" extension. See if that will do what you need. -- Take care and have fun, Mike Diehl. -- _____________________________________________________________________ -- 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
