[Asterisk-Dev] dev conf topic: better CDRs

[Race Vanderdecken]

The CDR Id is as unique as the code that wrote it.

Normaly  a GUID is used. Some peoplel like part of the ID to reflect the
user account or the server IP/name where the CDR is coming from.

You have control over the CDR Id.

Seeding is great, but it is going to drive you nuts at debug time, it
really need to be unique within your billing system.

Race "The Tyrant" Vanderdecken

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Matthew
Boehm
Sent: Wednesday, February 23, 2005 3:16 PM
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] dev conf topic: better CDRs

I've already got CDRs off the asterisk box. They are being dumped into a
dedicated mysql server. A problem that I am worried about is having
multiple
asterisk boxes writing CDRs to the same table.

Just exactly how unique is the unique id in a CDR? Is there a way to
"seed"
each server so that the random id is more random?

-Matthew

----- Original Message ----- 
From: "Race Vanderdecken" <asteriskdev at codetyrant.com>
To: "'Asterisk Developers Mailing List'" <asterisk-dev at lists.digium.com>
Sent: Wednesday, February 23, 2005 1:40 PM
Subject: RE: [Asterisk-Dev] dev conf topic: better CDRs


> Greetings,
>
> One way to improve the CDR is to move to RADIUS to log the CDRs.
> Yes, I know this involves getting RADIUS to work better under asterisk
> but I created code that did this, and if I can do, 5% of you could do
> it. You also have to create mysql CDR tables.
>
> I am going as fast as I can to get the RADIUS stuff for Asterisk
> available, but other contracts are getting in line first, mostly
because
> of money.
>
> But the Idea of using RADIUS to put the CDRs into mysql does work and
is
> a path people should try. Mainly because it gets the processing of the
> CDRs off the asterisk box and does the mysql off loaded.
>
> The time it takes to do the offload of the CDR via RADIUS to mysql is
> about 2/1000th of a second per call, so time is not an issue. 50 calls
> per second is fast. If you are doing more than 4,000,000 calls day,
give
> me a call and I will try to make it run faster.
>
> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Matthew
> Boehm
> Sent: Tuesday, February 22, 2005 12:51 PM
> To: asterisk-dev at lists.digium.com
> Subject: [Asterisk-Dev] dev conf topic: better CDRs
>
> There are many Asterisk users out there than need better/more detailed
> CDRs.
> Our class 4/5 switch spits out over 80 different columns for each call
> that
> passes thru. Most notably are the differences between "true" number
and
> "translated" number.
>
> If a call comes into our switch as 8005551212, that is the
> "destination".
> Most of the time, an 800 number gets translated. This becomes the
> "ringto".
> Both are necessary for billing purposes. Sometimes we have triple
> translation, where an 800 number gets translated to local which has
> call-forwarding on busy to another local number. We still have the 800
> as
> dest, but the final number gets saved as 'ringto'.
>
> One of the biggest irritations I see on -users is the fact that a
person
> calls 5551212, which gets sent to SIP/2033 and 2033 gets put into the
> cdr as
> the dest. Technically that 'is' the destination of the call but it is
> not
> the number that was dialed.
>
> Off the bat, I'd like to add 1 column and modify 2: src needs to stay
as
> source. If you change the callerID, thats fine, just don't also change
> the
> src. If necessary, split callerid into two columns for name and number
> then
> you can still search for the 'translated' source number. The column
> 'rtn'
> (ring-to number) needs to be added. The rtn is the actual number that
is
> ringed. 'dst' should be renamed to 'cdn' (called-destination number).
> This
> is the actual number that someone dialed. rtn would be any
translations
> of
> cdn.
>
> Examples:
>
> SIP/3044   dials 5124512424 (src: 3044       rtn: 5124512424 cdn:
> 5124512424)
> 5124512424 dials 8005699985 (src: 5124512424 rtn: 3044       cdn:
> 8005699985)
>
> bug #3595 seems that it might provide for this, but i'm weary on its
> database/RealTime support.
>
> Thoughts...suggestions..
> -Matthew
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev