similar to: CDR Hangupcause

Displaying 20 results from an estimated 7000 matches similar to: "CDR Hangupcause"

2015 Oct 07
2
Storing HANGUPCAUSE in CDR
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
2015 Oct 09
2
Storing HANGUPCAUSE in CDR
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
2008 Dec 29
1
1.6, CDR and h extension
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
2010 Dec 22
8
Possible Bug (Include ${HANGUPCAUSE} in CDR)
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
2010 Dec 22
0
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
2009 Jun 29
0
FW: re: Asterisk Outbound with Failover, alarm notification, dial status and hangupcause capturing to CDR from Dialplan
Managed to implement this on asterisk v1.4.24.1, Also, Hangupcause updating to user field. However, this only works on the edge of my voice network (demarcation point) It does not work on my internal routing boxes as I use IAX to route between remote sites. I was thinking of using some sort of SIP variables to transport these results over the IAX trunk.. Any bright ideas folks???
2014 Nov 20
1
Error saving cdr at h exten in Asterisk13
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
2006 Apr 21
0
HANGUPCAUSE on SIP channels
Hopefully I'm not just missing some little detail here. We're trying to set the HANGUPCAUSE on SIP channels to have our softswitch play the proper recording instead of answering the call on Asterisk to play the message. It appears that no matter what the HANGUPCAUSE is set to, Asterisk always just sends "603 Declined". I looked through the source code briefly and it appears
2012 Dec 21
0
CDR written before hangup extension
asterisk 11.1 Documentation in cdr.conf for endbeforehexten reads: 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 and hangup handlers so that CDR values such as "end" and "billsec" may be retrieved inside of of this extension. I have
2013 Mar 29
1
Asterisk 11 - Change CDR in hangup exten [Was: CDR values changed in hangup handler not saved]
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
2010 Dec 22
0
CDR on MySQL
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:
2015 Aug 04
2
Modifying CDR values from a hangup extension in Asterisk 13
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
2018 Mar 14
2
DIALSTATUS vs HANGUPCAUSE
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
2011 Jan 26
0
Variable HANGUPCAUSE always empty with DAHDI
Hi, I am using Asterisk: 1.6.1.20 LibPRI: 1.4.11.4 DAHDI: 2.3.0.1 Echo Canceller: MG2 Wanpipe-Driver: 3.5.15 Sangoma-Firmware: 43 (A104d) I handle some calls with my own PHP-AGI-Script. After a dial-command I use "GET FULL VARIABLE ${answeredtime}" or "GET FULL VARIABLE ${dialstatus}" and get valid information. Sometimes "dialstatus" has the value
2018 Mar 14
2
DIALSTATUS vs HANGUPCAUSE
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
2009 May 18
0
${HANGUPCAUSE} is not printed when call ends or is interrupted
Today I get the remark that a call got disconnected after 10 minutes. This what my VERBOSE-logfile tells me : [May 18 15:36:30] VERBOSE[3940] logger.c: -- Executing [00493516426 at intern:1] NoOp("SIP/51-b76023b8", "Gesprek naar GSM-nummer via Telenet") in new stack [May 18 15:36:30] VERBOSE[3940] logger.c: -- Executing [00493516426 at intern:2]
2006 Apr 13
0
Hangupcause to handle Called party disconnect ? PSTN----E1----OldPBX---E1--Asterisk
Hi, I've been debuging the call disconnection problem in our architecture: PSTN---E1---OldPBX---E1---Asterisk This is our problem: -SIP user agent "A" calls a pstn phone "B". -"B" hangs up the call. -SIP user agent "A" starts listenning busytones... But the call still on. (and being payed). - Call only ends when it is correctly hanged up in the
2018 Feb 20
2
Modifying CDR values from a hangup extension in Asterisk 13
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
2015 Aug 03
2
Modifying CDR values from a hangup extension in Asterisk 13
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
2006 Apr 04
5
Hangupcause is not enough on PRI
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