From 5eaf8450d6e71d391e60e238195da5c0b69232e9 Mon Sep 17 00:00:00 2001 From: Steve Murphy Date: Tue, 5 Aug 2008 23:45:32 +0000 Subject: Merged revisions 135799 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r135799 | murf | 2008-08-05 17:13:20 -0600 (Tue, 05 Aug 2008) | 34 lines (closes issue #12982) Reported by: bcnit Tested by: murf I discovered that also, in the previous bug fixes and changes, the cdr.conf 'unanswered' option is not being obeyed, so I fixed this. And, yes, there are two 'answer' times involved in this scenario, and I would agree with you, that the first answer time is the time that should appear in the CDR. (the second 'answer' time is the time that the bridge was begun). I made the necessary adjustments, recording the first answer time into the peer cdr, and then using that to override the bridge cdr's value. To get the 'unanswered' CDRs to appear, I purposely output them, using the dial cmd to mark them as DIALED (with a new flag), and outputting them if they bear that flag, and you are in the right mode. I also corrected one small mention of the Zap device to equally consider the dahdi device. I heavily tested 10-sec-wait macros in dial, and without the macro call; I tested hangups while the macro was running vs. letting the macro complete and the bridge form. Looks OK. Removed all the instrumentation and debug. ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@135821 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- main/cdr.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'main/cdr.c') diff --git a/main/cdr.c b/main/cdr.c index f8fc2c634..9402ae674 100644 --- a/main/cdr.c +++ b/main/cdr.c @@ -157,6 +157,11 @@ void ast_cdr_unregister(const char *name) AST_RWLIST_UNLOCK(&be_list); } +int ast_cdr_isset_unanswered(void) +{ + return unanswered; +} + /*! Duplicate a CDR record \returns Pointer to new CDR record */ -- cgit v1.2.3