On Wed, Oct 15, 2014 at 9:31 PM, Murthy Gandikota <mgandik...@nts.net> wrote:
> Thanks, Matthew. I think CDR(answer) is, in the end, not very useful to > me if it changes from context to context. Suppose from AMI we generate a > status > I'm not sure what you mean by "changes from context to context". The answer time on a CDR is reflective of when the channel was answered. That can be altered if you choose to alter it in the dialplan via ForkCDR, but generally, that time is conveyed from one CDR to another. A specific example would help here. > event, what will be the CDR(answer)? I see that sometimes it is returned > as the literal "Production" instead of a Date/Time or a blank value. I don't know what you mean here either. What version of Asterisk are you using? Can you provide an example where you get said literal back, as well as the dialplan that produces this behavior? > I > am only puzzled that no one created a patch for the first timestamp when > a call is answered. If I get some free time, I will try to create one. > > -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- 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