similar to: CDR changes in 1.4.3?

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.

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

Hi All My dial plan has the following context: [sip-guest] exten => _!.,1, Answer exten => _!.,n, verbose(1,[${EXTEN}@${CONTEXT}]) exten => _!.,n, resetcdr(w) exten => _!.,n, resetcdr(w) exten => _!.,n, set(DNIS=${EXTEN}) exten => _!.,n, resetcdr(w) exten => _!.,n,

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

Ok I can't get my CDR values to set from the h extension in either 1.6.2 or 1.8 What is wrong? Here is what I found in the cdr.conf ; Normally, CDR's are not closed out until after all extensions are finished ; executing. By enabling this option, the CDR will be ended before executing ; the "h" extension so that CDR values such as "end" and "billsec" may

Hi all, I have a strange situation on a Asterisk 1.2.17 with FreePBX 2.2.1 Doing a select in the CDR table I noticed there are some calls with billsec greater than duration, duration is always 0 in those calls. How can this happens ? Am I missing something ? Tnx in advance Regards Edoardo Serra WeBRainstorm S.r.l.

Hello, I am wondering if someone has got any ideas that can help solve this problem. I have a dial plan that you call into, and depending on certain conditions it calls out on a number grabbed from a database. Something like this : exten => s,n,Do something exten => s,n,Do something else exten => s,n,Dial(ZAP/g1/${OUTBOUND},${timeout}) I need to log the time the person

Dear all, I'm trying to configure Asterisk to be able to ask the caller to enter a given password in order to continue dialplan execution. I've tested this feature using the Authenticate application like this: exten => _X./5219,1,Answer exten => _X./5219,2,Authenticate(1234,a) exten => _X./5219,3,Playback(pin-number-accepted) exten => _X./5219,4,Dial(SIP/${EXTEN},120)

Hi, In my application I jump to different extensions For example: [begin] exten => s,1,Goto(starts,s,1) [start] exten => s,1,Play(welkom) ..... exten => h,1,Goto(end,s,1) [end] exten => s,1,Macro(end_call) exten => s,n, Hangup When I look at my CDR record I see three different CDR's in my record. Is there a way to use one CDR on every call, and not

Can someone tell me what I am doing wrong? Why doesn't CDR(duration) or CDR(billsec) return the correct values? cdr.conf endbeforehexten=yes extensions.conf [macro-Dial] ; ${ARG1} - Dial String exten => s,1,Dial(${ARG1},,M(post-dial)) exten => h,1,NoOp(Call was hung up - ${CDR(duration)} seconds long, billed for ${CDR(billsec)} seconds) The log shows: -- Executing [h

Hi, I'm stuck on a silly thing. I need to get the "billsec" CDR value after a call. But I'm finding its always 0. Here's my test code: exten => *244*,1,Dial(Local/test@custom-tests/n,,g) exten => *244*,n,Noop(after dial duration is ${CDR(duration)} billsec is ${CDR(billsec)}) exten => *244*,n,Hangup [custom-tests] exten => test,1,Answer exten =>

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

hi i've made some test calls, i've notice that a call of the duration of 1:29 minutes is recorded in the cdr database as 1:45 minutes, is it normal? i think that 15 seconds are too many... how can i correct this? thanks

Hi I have a question if there was a major change in CDR? Few days ago I have upgraded to 1.4.12.1 from 1.4.4 and something bizarre happened. After the upgrade I have no call details in the cdr table when the call did not go through because of for example: Unable to create the channel of type Sip - no route to destination. In such situation the call does not exist in the cdr table while it was

Hi, in dialplan -Asterisk 16.2 from Debian Buster- we have  same = n,Dial(PJSIP/101&PJSIP/102&PJSIP/103,15,tT) If thew call is not answered after 20 seconds, we launch a new dial with same and/or other extensions  same = n,Dial(PJSIP/101&PJSIP/104&PJSIP/110,20,tT) Looking in CDR we have at the end of the call (here we called 3 extensions which where ringing, let say 110

Hi to all. What can i do if a customer needs to log in the CDR all the dialpan actions related to a call? I mean, not only the lastapp e the lastdata but all the dialpan actions! I know that the actual CDR system store one record for each call (and for billing purposes this can be correct) but in some cases the approach needed is something similar to the queue_log. I know that exists ResetCDR

Hi, I am moving my call center to 1.4. Previously I was recording calls in agents.conf with the following config recordagentcalls=yes recordformat=wav createlink=yes So I had the filename in all calls which was *connected to agents*. I am looking for a similar functionality for 1.4. I am now recording calls using the following configuration. [general] persistentmembers = no eventwhencalled =

Greyman-- I'm taking this discussion to the list. Folks, what we are talking about here, is me trying to get a grasp around Greyman's (Aaron's) request for a bare-bones CDR generation that describes just total connect time for channels, stripping out all the details. Who cares about xfer, park, hold, etc.? So in the following is our discussion about what *should* be there, and in

For a new project, I have written a dialplan and it is pretty straight forward: The [dialout] context dials out a number, and h extension in this context writes the CDR. But what is happening is that if the callee hangs up first, all values in the CDR are fine, but if the caller hangs up first, the 'dst' column is always 'h'. I put a NoOp right in the begining of this macro to

Hello, I've migrated from CSV CDR to MySql CDR and the customization of my CDR's is not working anymore. Do you know if the cdr_mysql is supporting custom cdr's ? If not, is there any alternative/workaround ? Best regards, Patrick