similar to: Possible Bug (Include ${HANGUPCAUSE} in CDR)

I am trying to include the ${HANGUPCAUSE} in my mySQL cdr tables. I have a field called cause_code but it won't write. I belive it is because the record has already been written by the time I hit the h section of the code. How might I get this info into the CDR. I need this info for Quality of Service as well as route checking. Any ideas would be apperciated. Here is my dial line and my h

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

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

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

So... I'm trying to access CDR(duration) and CDR(billsec) inside h... I keep getting 0. Can I access the CDR function inside a hangup extensions? Asterisk 1.4.13 Thanks, Doug. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

Hello, We have a strange situation (asterisk 1.6.2.14), where we get a result for DIALSTATUS for BUSY and No-ANSWER, but nothing for CANCEL. This is the (relevant) test dialplan: -------------------------------- [incoming-private] exten => _X., n, Dial(SIP/1001,30) exten => _X., n, NoOp(${DIALSTATUS}) exten => _X., n, Gosub(incoming-status,s-${DIALSTATUS},1) [incoming-status] exten

Hello list, Hope all doing well! I've been checking some cases when a Dial fails and dialplan execution continues to handle this. I am finding it a little confusing how we should handle the DIALSTATUS and the HANGUPCAUSE in this situation.... More specifically, I am facing a case in version 13.6.0 where I am getting a DIALSTATUS=BUSY and HANGUPCAUSE=19 after receiving a 480 SIP error. Seems

Thanks Dovid! Indeed looks a bug but regardless of this, this problem made me think that the HANGUPCAUSE could be used for this purpose with benefits. I couldn't find an explanation about when DIALSTATUS would actually be better. The HANGUPCAUSE was reworked in version 11 ( https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause) but I didn't find someone actually stating it is a better

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'm using Asterisk and a TE110P E1 PRI in Chile. When I call to a disconnected number or any not operational number, the telco sends the Hangupcause disconnection code and an audio message notifying the disconnection cause to the user. Asterisk does not allow the user to hear the audio message form the telco, instead it cuts the call. Any other legacies PRI PBX I've tested allow

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

I'd like to grab the SIP response code that comes back from an INVITE. The HANGUPCAUSE gives the converted ISDN cause code. Anyone know of a way to get the SIP response code instead? Doug. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML

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

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

Hello. I have a problem with the native Android SIP client, not acknowledging the call. Sent a message to the list for some weeks ago containing a sip debug log, but it only got stuck in moderation queue due to too large size (and it said I would get a message if moderators rejected it, but did not get message and I don't think it got posted to list either) This ONLY happens when

Hi, Is there any way to tell Asterisk not to generate additional headers like: X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 I can't find any relevant option in sip.conf file :-( Thanks for help. Chris

Hello, On your BRI or PRI's what do you guys get as HANGUPCAUSE when dialing an unalocated number? I always get 3 (no route) which is less than helpful.

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

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