[asterisk-dev] CDR issues - Can someone sanity check them?

[Steve Davies]

On 4 January 2012 13:26, Ryan Wagoner <rswagoner at gmail.com> wrote:
> On Wed, Jan 4, 2012 at 5:56 AM, Steve Davies <davies147 at gmail.com> wrote:
>>
>> Hi,
>>
>> I appreciate that CEL is probably the preferred call logging mechanism
>> these days, but I've found a couple of CDR issues, originally in 1.6.2
>> that still apply through 1.8.x and 10.x.
>>
>> https://issues.asterisk.org/jira/browse/ASTERISK-17826 was already
>> open against 1.6.2, but I've just updated it for v.10
>>
>> https://issues.asterisk.org/jira/browse/ASTERISK-19164 is new as I
>> discovered it while researching #17826.
>>
>
> I've found the CDR records to be buggy when transferring. Basic
> inbound/outbound calls are accounted for correctly. At the very least I
> would like to see transfers fixed, which is most likely the same issue for
> AMI redirects.
>
> https://issues.asterisk.org/jira/browse/ASTERISK-18733
>
> Having to parse CEL to produce my own CDR records seems like an extra step.
> If CEL was added so I can parse the records correctly why can't Asterisk? I
> know everyone has disagreements on how CDR records should be accounted for,
> but I don't think CDR data should be just left out.
>

Ryan,

I am glad I am not alone in wanting to persist with CDRs. I am
actually 95% through a CDR rewrite which does away with the very odd
behaviour of using a temporary bridge_cdr, and instead better defines
the meaning of a CDR on a calling and a called channel, and what to do
if a called channel becomes a calling channel and so forth.

The end results are identical to the original code for most cases, but
fixes all of the broken cases that I've identified to date. It is not
a simple patch, and it is currently only for 1.6.2, but I need a 1.8
and/or 10.0 version, so will submit that properly when I have it
ready. If I'm honest, I'm scared of it!

Regards,
Steve