Make ForkCDR e option not set end time of the newly forked CDR log
authorJonathan Rose <jrose@digium.com>
Fri, 13 Apr 2012 16:12:17 +0000 (16:12 +0000)
committerJonathan Rose <jrose@digium.com>
Fri, 13 Apr 2012 16:12:17 +0000 (16:12 +0000)
commitba0f044bde5e5417cec7c3daf2bed907224423e6
tree2e161020943a0f7966ff16c4bec669cbff6e364b
parentc0b9fe8530fa14f707bb4e3fa037f26acccb7149
Make ForkCDR e option not set end time of the newly forked CDR log

Prior to this patch, ForkCDR's e option would immediately set the end time of the forked
CDR to that of the CDR that is being terminated. This resulted in the new CDR's end time
being roughly the same as it's beginning time (which is in turn roughly the same as the
original's end time).

(closes issue ASTERISK-19164)
Reported by: Steve Davies
Patches:
cdr_fork_end.v10.patch uploaded by Steve Davies (license 5012)
........

Merged revisions 362082 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........

Merged revisions 362084 from http://svn.asterisk.org/svn/asterisk/branches/10

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@362085 65c4cc65-6c06-0410-ace0-fbb531ad65f3
apps/app_forkcdr.c