From 10905ab2d73c86a8dbdd86ea16922c169478bc24 Mon Sep 17 00:00:00 2001 From: Terry Wilson Date: Thu, 9 Feb 2012 22:03:51 +0000 Subject: [PATCH] Note that CDRs are immutable once a bridge is torn down CDRs cannot be modified after a bridge is torn down, (e.g. after Dial() returns) even though the CDR() function may be called. Since modifying the CDR code to change this behavior could very easily break all kinds of things, this patch just documents this limitation. (closes issues ASTERISK-16923) Review: https://reviewboard.asterisk.org/r/1720/ ........ Merged revisions 354749 from http://svn.asterisk.org/svn/asterisk/branches/1.8 git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/10@354750 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- funcs/func_cdr.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/funcs/func_cdr.c b/funcs/func_cdr.c index dc71096598..25e10a2fa4 100644 --- a/funcs/func_cdr.c +++ b/funcs/func_cdr.c @@ -140,7 +140,9 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$") with this function, and this variable will be stored on the cdr. For setting CDR values, the l flag does not apply to setting the accountcode, userfield, or - amaflags. + amaflags.CDRs can only be modified before the bridge + between two channels is torn down. For example, CDRs may not be modified after the + Dial application has returned. Raw values for disposition: