similar to: CDR written before hangup extension

Asterisk 11.1.0 One queue with strategy=leastrecent. (Full queues.conf below.) Occasionally (several times today), a caller will get "stuck" in the queue - there are operators available to take the call, but the caller stays in the queue for a long time. Any idea what might cause this, or where I can start looking to debug it? I'm going to start digging through the queue log

Trying to set some CDR fields in the "connected" macro of a queue command. None of the custom fields I set are stored in the database, but I can set "userfield" and it does get set. I think that the macro runs on the agent's channel, not the caller's, and this might contribute to the problem. From the sample below "userfield" (and its alias operatorid)

Dears, I need to save some information on userfield when calls end in Asterisk13, but I have two error cases: 1. With endbeforehexten=no in cdr.conf, I have a registry in cdr, but userfield is not set. 2. With endbeforehexten=yes, I have two lines in cdr, one with duration, src e dst correct, and a second line with userfield setting and dst h. I am using cdr_odbc.conf, with Asterisk11.14.0 it

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, 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

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

What would it do if you exten => h,1,ResetCDR(w) exten => h,2,NoCDR() exten => h,3,DEADAGI(get-unqiueid.php) I have not tried it but in theory it should write the first CDR and then kill the write of the second NO ANSWER CDR. Let me know if it works for you as I may need to do it on some of my h exten code as well. Bryant ---------------------------------------- From:

2013/3/29 Julian Lyndon-Smith <asterisk at dotr.com> > check out the endbeforehexten option in cdr.conf > > this needs to set to "yes" > > Julian > Unfortunately, this doesn't help. Let's drop the hangup handler at the moment, and focus on the "saving to file" part. Then my issue is I can't update CDR value is hangup exten. Here is a

Hi, I'm trying to migrate from Asterisk 1.8 to Asterisk 13 and can't figure this one out. I'm pretty sure the question has been already asked, but I failed to find a solution. Can you modify CDR values in an h-extension? My cdr.conf contains: [general] enable=yes unanswered=yes endbeforehexten=yes initiatedseconds=no batch=no The diaplan contains a simple "h" extension

Hi, I have the following code that operates when a channel is hung-up: [record-hangupcause]exten => 1,n,Set(CDR(hangupcause)=${HANGUPCAUSE})exten => s,n,Return() Before the dial a hangup handler is registered: Set(CHANNEL(hangup_handler_push)=record-hangupcause,s,1) The routine is called and the variables are being set, however not on the channel's CDR which made the call. I believe this

I have two version 1.6 Asterisks running. One is a small hobbyist thing just at home, and the other is handling calls for several customers. On both, I have added the line exten => h,1,Set(CDR(hangupcause)=${HANGUPCAUSE}) to all relevant contexts. On my little hobbyist box this works perfectly; all calls have their hangupcauses recorded with cdr_adaptive_odbc and cdr_custom. On the

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

Hello list, how does StopMixMonitor know which 'monitoring channel' to stop when there are multiple conversations that are being monitored/recorded ?? I want to use StopMixMonitor in a macro, called from within applicationmap (features.conf). Jonas. -------------- next part -------------- An HTML attachment was scrubbed... URL:

This was always possible in the past, however does not work in the current release. I believe this is a bug. To: asterisk-users at lists.digium.com From: cervajs at fpf.slu.cz Date: Fri, 9 Oct 2015 10:04:47 +0200 Subject: Re: [asterisk-users] Storing HANGUPCAUSE in CDR search in archives save the records to another table like cdr_extended Dne

Hi all, I use astersk 11.7.0 on Ubuntu 12.04.01 TLS (i386). I use cdr_adaptive_odbc to write CDR to my MySQL's cdr table. After my testing, this scenario is working well. After a long idle time, I didn't make any call to the asterisk server. When I try to make a call again after 8 hours, I found that the cdr lost. It cannot be inserted to cdr table. Also, I could not find the insert CDR

Hi all Using asterisk 16.25 I was trying to stop Mixmonitor using features. The code is executed but I realized that I was executing StopMixmonitor from another channel so I opted to use AMI. When I call MixMonitor I store the channel name in a var and then I use StopMixmonitor from AMI sending the stored channel name as parameter. What I've seen is that the app returns failure and going

Hi, I'm trying to get HANGUPCAUSE on my cdr the problem I'm facing is that this option: endbeforehexten=yes is not working at least on asterisk 1.6.0.1, so if I put yes o no I cant set CDR value with that value. It seems to finish the CDR record before h is executed. I'm using cdr_mysql. Any idea?? Thanks!! -------------- next part -------------- An HTML

Every once in a while (like 2 out of 7 times), I get the following message: [Nov 14 12:49:02] NOTICE[6855]: cdr.c:434 ast_cdr_free: CDR on channel 'SIP/5000-082508f0' not posted I look in the cdr table in mySQL and indeed, the record is not posted for that call. This makes me want to create hard file and a compare script between the file cdr and the odbc cdr, but I was wondering if

Hi, I am using Asterisk 1.6.2.13 and have an issue but I'm not sure if it's a bug or not. I am using the cdr_adaptive_odbc logging module and writing my CDR records to a MS-SQL server. I need to log which end hangs the call up and have placed the relevant CDR(myfield)=caller/callee commands where they need to be. When I watch the call on the console I can see the CDR field being set

Hello list, I'm having troubles implementing the ${CDR(duration)} & ${CDR(billsec)} variables in this scenario: PEER CALLS OUT -> CALL GOES TO PEER'S DEFAULT OUTGOING CONTEXT -> THE CALL IS SENT TO A MACRO AND GOES IN HANGUP -> THE CALL RETURNS TO EXTENSION h OF PEER'S DEFAULT OUTGOING CONTEXT (here I'm trying to print the variable)