From 7e9febbf86f7a9aa0cc1d9852d1ed1b77f25b3ce Mon Sep 17 00:00:00 2001 From: Matthew Jordan Date: Thu, 19 Dec 2013 00:50:01 +0000 Subject: app_cdr,app_forkcdr,func_cdr: Synchronize with engine when manipulating state When doing the rework of the CDR engine that pushed all of the logic into cdr.c and made it respond to changes in channel state over Stasis, we knew that accessing the CDR engine from the dialplan would be "slightly" non-deterministic. Dialplan threads would be accessing CDRs while Stasis threads would be updating the state of said CDRs - whereas in the past, everything happened on the dialplan threads. Tests have shown that "slightly" is in reality "very". This patch synchronizes things by making the dialplan applications/functions that manipulate CDRs do so over Stasis. ForkCDR, NoCDR, ResetCDR, CDR, and CDR_PROP now all use Stasis to send their requests over to the CDR engine, and synchronize on the channel Stasis topic via a subscription so that they return their values/control to the dialplan at the appropriate time. While going through this, the following changes were also made: * DISA, which can reset the CDR when a user successfully authenticates, now just uses the ResetCDR app to do this. This prevents having to duplicate the same Stasis synchronization logic in that application. * Answer no longer disables CDRs. It actually didn't work anyway - calling DISABLE on the channel's CDR doesn't stop the CDR from getting the Answer time - it just kills all CDRs on that channel, which isn't what the caller would intend. (closes issue ASTERISK-22884) (closes issue ASTERISK-22886) Review: https://reviewboard.asterisk.org/r/3057/ ........ Merged revisions 404294 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@404295 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- CHANGES | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'CHANGES') diff --git a/CHANGES b/CHANGES index 6112c6a93..ada66405a 100644 --- a/CHANGES +++ b/CHANGES @@ -191,6 +191,12 @@ AlarmReceiver * Added configuration option no_group_meta. If enabled, grouping of metadata information in the AlarmReceiver log file will be skipped. +Answer +------------------ + * It is now no longer possible to bypass updating the CDR on the channel + when answering. CDRs reflect the state of the channel and will always + reflect the time they were Answered. + BridgeWait ------------------ * A new application in Asterisk, this will place the calling channel -- cgit v1.2.3