Summary:ASTERISK-07232: ResetCDR(w) resets CDR data before writing it
Reporter:Roy Sigurd Karlsbakk (rkarlsba)Labels:
Date Opened:2006-06-26 10:10:31Date Closed:2006-09-06 12:22:21
Versions:Frequency of
Description:It seems ForkCDR(w) resets data before dumping it, so it renders this option quite useless. See below for output. This was in the middle of a call, so lots of data should exist here.


from standard custom CDR log

""21973558" <21973558>","21973558","91326310","default","Local/91326310@default-72cc,2","","ResetCDR","w","2006-06-26 17:40:01","","2006-06-26 17:40:01","0","0","NO ANSWER","DOCUMENTATION","","1151336401.22",""
Comments:By: Russell Bryant (russell) 2006-07-02 22:46:33

I do not see any 'w' option to ForkCDR so I have no idea what you are talking about.  Is this patched?

By: Roy Sigurd Karlsbakk (rkarlsba) 2006-07-04 07:05:09

Sorry. I meant ResetCDR :)

By: Russell Bryant (russell) 2006-08-05 03:45:36

What exactly would you expect to see differently in the CDR record you have provided?

By: Roy Sigurd Karlsbakk (rkarlsba) 2006-08-05 10:35:22

1. Call starts
2. Call pickup
3. Some action causes ResetCDR(w) to be called
4. ResetCDR logs CDR data with call length and so on
5. New CDR entry is started

That is what it does, also, except it resets CDR data before logging the entry at step four. Currently it does indeed log an entry at step four, but the CDR entry is reset before logging it, making it rather unusable.


By: Roy Sigurd Karlsbakk (rkarlsba) 2006-08-05 10:48:48

Doing a little RTFS, I can't see why this is happening. I'll do some more testing and get back here within a few days.

By: Serge Vecher (serge-v) 2006-08-21 14:37:58

ok, a few days have a passed and ...

By: Serge Vecher (serge-v) 2006-09-06 12:22:20

looks like not a reproducible bug here.