similar to: Simple CDRs

Hello! Most are probably bored seeing another letter about this, but I've put in a fair amount work on a spec for rewriting the CDR system in Asterisk, and I have some questions: First, please look at what I've written so far: svn co http://svn.digium.com/svn/asterisk/team/murf/RFCs and look at the file "CDRfix2.rfc.txt" in the RFCs dir. The spec SIGNIFICANTLY alters the way

I've taken the liberty of starting a new thread to discuss the design of the Asterisk CDR mechanism. The discussion has been kindly initiated by murf putting together a proposal: http://svn.digium.com/svn/asterisk/team/murf/RFCs. After reading the proposal I still don't think it's the right way to go. To my mind adding more channel variables increases the complexity in a situation

I've taken the liberty of starting a new thread to discuss the design of the Asterisk CDR mechanism. The discussion has been kindly initiated by murf putting together a proposal: http://svn.digium.com/svn/asterisk/team/murf/RFCs. After reading the proposal I still don't think it's the right way to go. To my mind adding more channel variables increases the complexity in a situation

Hello, I have a setup with asterisk 16.8.0, I'm facing a problem where calls that fail (CONGESTION) don't have filled in some extra fields we add to the CDRs in the database. We use cdr_adaptive_odbc with MySQL as backend. To simplify the scenario: [sub-hanguphandler] exten => s,1,Set(CDR(foo)=${bar}) same => n,Return() [default] exten => _X.,1,NoOp(New test call) same =>

Hey, I just found this in ML archives. I have pretty the same situation - i had very well written CDR processing engine on asterisk, making use of ResetCDRs, however now when we're migrating to 1.4, it's a bit pain to deal with extra CDR records. My engine is built so that MYSQL CDR can be used directly for reports (imagine - you get whatever report you need immediately). So, this way i

Hi everyone, I am facing lots for problem with CDRs in 1.6 and above versions,its shows wrong records when I do transfer(caller side and calee side),callforward,call parking.Is the present CDRs in 1.6 is enough for Complete billing.?What I need to do to make it proper.Please help me on this. Thanks Nikhil

On Sat, 2009-02-07 at 15:51 -0500, Alexander Lopez wrote: > > > -----Original Message----- > > From: Steve Murphy [mailto:murf at digium.com] > > Sent: Saturday, February 07, 2009 1:59 PM > > To: Alexander Lopez > > Subject: RE: [asterisk-dev] 1.4 and CDRs -- The Breaking Point > > > > On Fri, 2009-02-06 at 12:28 -0500, Alexander Lopez wrote: >

This is just a note that the fixes in the CDRfix4 and CDRfix6 branches are getting closer to being merged into 1.4, trunk, and 1.6.x. If CDR's are important to you, and you ignore this notice, then you deserve what you get! These branches address various long-standing bugs, most of which are regressions from 1.2. It is hoped that these fixes will solve most of the problems introduced by the

How is the billsec field calculated in CDRs? I have a situation where billsec is being reported as 0 despite the call being answered and a conversation occurring. An example record follows: '2007-11-06 21:36:50', '6495566778', '6495566778', '0116495566778', '1100012_1', 'Local/0116495566778 at 1100012_1-887b,2',

I have created an asterisk.org blog entry: http://www.asterisk.org/node/48358 to describe what I will shortly be committing to trunk to correct the weaknesses of CDRs, that asterisk users and developers have been complaining about for quite some time. Highlights: Restructuring the code and philosophy of CDRs. Plans to eliminate the ForkCDR() application Plans to create

I am trying to get cdr via odbc to work on Asterisk 13.7.2 but I keep getting this error: [Feb 9 16:21:43] WARNING[2088]: cdr_odbc.c:160 execute_cb: cdr_odbc: Error in ExecDirect: -1, query is: INSERT INTO cdr (calldate,clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,duration,billsec,disposition,amaflags,accountcode,uniqueid,userfield,peeraccount,linkedid,sequence) VALUES ({ts

I'm having an issue with CDR. Basically, I expect to have all "legs" of a call having the same linkedid and differing only by the sequence value. That does happen, but I'm getting null dst values after doing an attended transfer. I'm not sure if this is a bug or I'm doing something wrong. I'm running Asterisk 13.2.0. Here's the console log, step by step: First,

Hi Steve, > .. I'll try to sort all this out, and then I'll attack this > problem. Hopefully, I get it all into svn before the next release of > 1.4...! Just wondering if any new CDR functionality made it into the 1.4.16.2 release? I have looked through the ChangeLog for the 1.4.15 and 1.4.16.2 releases but didn't spot anything to do with changes in CDR handling. I for one

Hello all: I upgraded to 1.4.3 last night and use MySQL for CDR. I have noticed that 1.4.3 seems to log a lot of "crap" to CDR that 1.4.2 did not. I use a few macros in my dialplan to handle outgoing calls (lcr type stuff) and in addition to the proper CDR for the call itself I also have records to 's' in the same dest-context and entries to 's' in the default context.

With endbeforehexten=no I actually get two CDR entries. One for the call and a second one for the "h" extension. "","13","10","sip-locals","""13"" <13>","SIP/13-00000006","SIP/10-00000007","Dial","SIP/10","2015-08-04 06:28:44","2015-08-04

Hi, okay heres what I want to do .. simple ivr, we take a call, answer it, play a menu, dial out based on options. No problems so far. The CDR always shows the call as answered as I answer the 1st leg to play the prompts, I am actually more interested in if the 2nd leg - the outbound part - has been answered or not before the call is hungup. How can I get this and record the information in

Hello, CDR fans! I'm looking at some issues brought forward over time: 12726/10668: someone wants me to revert the changes I made via bug 10668, last Sept; (that's they are messing him up. And I didn't do the change suggested in ForkCDR, for fear of lousing up folks depending on current behavior. Which probably sparked: 11721 :

Hi, Reading this old thread, may I ask if keeping hangup handlers from updating CDR values still enforced in Asterisk 15 ? If positive, would it be very complex to add in Asterisk, a configuration option allowing a system administrator to list in cdr.conf, the CDR fields allowed to be updated in hangup handlers ? I'm planning to store some RTCP stats. Saving them in CDR(userfield) would be

I would like to send the CDR records from all our machines around the world to a single database. But I need the hostname included with each record for monitoring purposes. Is there a better way than using the userfield and adding SetCDRUserfield for every call to set the userfield to the name of the host? Thanks...

I'd like to know how everyone else is going about getting correct CDR information for calls. Right now I notice that if a call come in and gets parked the CDR info doesn't how the correct info on who picked that call up, also when someone transfer a call there isn't a new record being made so the duration of the call shows up for who received the call and transferred it. I started