[Asterisk-Dev] dev conf topic: better CDRs

[Paul Cadach]

Hello,

Matthew Boehm wrote:

[skip]
> 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'.

Usually such fields named as 'connected number' (CN), not 'ringto'.

Also, for redirections next parameters available/exists usually:
1) redirection count (RC);
2) original called number (OCN);
3) redirecting number (RN).

For first redirection (RC=1) OCN equal exactlt to RN, so OCN could be ommited, but for second and other redirection
(RC>1) OCN is a number where FIRST redirection was occured while RN is a number where LAST redirection was done.

Together with CN, redirection information should be included into CDRs to allow better analysis of calls flow. Also,
making CN available everywere within Asterisk could make possible to notify PSTN about real connected number when PSTN
"lies" to calling party with PRI's general/main number, not DDI.

As for encoding of CDR records there is X.825 specification describes extensible form for CDRs, and already have most of
important fields such as bearer capability, supplementary service information used for a call,
calling/called/redirected/connected/dialed numbers, etc. But X.825 have non-readable form (ASN.1 BER encoded), so
XER/XML could be used for make CDRs readable by peolpe without usage of additional format converters).


WBR,
Paul.