[asterisk-users] CDR Design

[Vlasis Hatzistavrou (KTI)]

Hello Andy,

> But, wouldn't it be better if you could ignore the CDR's completely and
> use an event based system?  This would give you ALL the information you
> need.  All that remains is to filter out the un-required bits.

I'd disagree. In some cases a event based system would be the best 
solution, but in systems with high call volumes, scanning through events 
looking for the proper billing information and parsing them would be a 
hard job compared to CDRs. In most cases where there are no transfers, 
calls on hold etc, but only basic dial-in & dial-out operations, using 
events instead of CDRs would probably be an overkill.

> Like I said earlier - the CDR's aren't reliable enough for a billing
> platform (as you've rightly pointed out) but are OK for very basic call
> logging (something the customer can look at).

I'm not sure I understand what you mean exactly. If you have in mind 
cases of transfers, calls on hold etc and you refer to Asterisk's CDRs 
at this point in time, then indeed, Asterisk's CDRs are not reliable in 
many cases.

However, CDRs in general on other platforms tend to be very reliable and 
useful for billing. My opinion is to transform Asterisk's CDR 
capabilities to something more carrier-grade in mind, configurable by 
the user.

Best regards,
Vlasis Hatzistavrou.


> 
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Grey Man
> Sent: 05 December 2008 09:37
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] CDR Design
> 
> On Fri, Dec 5, 2008 at 8:26 AM, Andrew Thomas <andy at datavox.co.uk>
> wrote:
>> In summary: Leave CDR exactly as it is and create a new CEL (Call
> Event
>> Logging) module (optional in modules.conf) that puts out (and does not
>> accept) call event information (ie. a one-way fire-and-forget output
>> from Asterisk).
>>
> 
> Hi Andrew and Others,
> 
> This thread is actually part of a discussion that has been going on
> for over a year. The links below provide the background to the whole
> thing.
> 
> http://www.asterisk.org/node/48358
> http://bugs.digium.com/view.php?id=11849
> http://lists.digium.com/pipermail/asterisk-users/2008-January/204856.htm
> l
> 
> Up until recently the approach was to try and fix the specific bugs
> with transfer CDRs as a typical bug. There is now a realisation that
> that is a lot trickier than inially thought so it's been decided to
> try and come up with a good design for the Asterisk CDR sub-system.
> 
> Regards,
> 
> Greyman.
> 
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>