similar to: DIALSTATUS vs HANGUPCAUSE

Displaying 20 results from an estimated 4000 matches similar to: "DIALSTATUS vs HANGUPCAUSE"

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
2004 Dec 03
2
DIALSTATUS weirdness (CHANUNAVAIL instead of BUSY, NOANSWER instead of CHANUNAVAIL)
Just throwing this out here, hopefully someone can tell me why. *CLI> show version Asterisk CVS-HEAD-11/17/04-10:16:38 built by root@wanderer on a i686 running Linux Zap/g1 is pri_cpe to Bell Canada 5551234 is a normal POTS line I have busied out (handset offhook) exten => 1234,1,Dial(Zap/g1/5551234,,g) exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is
2007 Aug 03
2
DIALSTATUS not set
I'm trying to write a dialplan that will allow me to "stress" test it. I want to be able to dial an extension, or pretend that the extension is busy or out of order (so that I can see what to do) given the dialplan snippet: [outbound] exten => _X.,1,NoOp(${TEST}) exten => _X.,n,Dial(SIP/${EXTEN}) exten => Busy,1,Busy(2) exten => Busy,n,Hangup() exten =>
2005 Sep 15
3
${DIALSTATUS} problems
Hi. I'm dialling two numbers - one that's unobtainable, one that's busy. ${DIALSTATUS} is coming back ANSWER each time right before the channels hang up. Am using the following dialplan macro to dial out. [macro-advdial] exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status
2009 Aug 13
1
Autofallthrough delays before hanging up calling channel?
I am seeing some curious behaviour with a 1.2.32 system, which I do not understand and so can't work out how to fix it. I have a PRI routed to context default. Here is the complete default context: [default] exten => _9X.,1,Dial(IAX2/m1peer/${EXTEN:1}) exten => _20XX,1,Dial(IAX2/sipeer/${EXTEN}) exten => _X.,1,Dial(IAX2/m1peer/${EXTEN}) exten =>
2009 Dec 15
2
member (In use)
Hello list. We just upgraded to 1.6.1.11. We are using real time information stored on mysql databases. That is all running fine. Now, since we upgraded, some member don't get calls from queues. In CLI: "queue show" shows something like: 611 (Local/611 at agents) with penalty 20 (realtime) (*In use*) has taken no calls yet We use the extension 611 in different computers, in the
2018 Apr 23
4
Alias for country in indications.conf
Hello list, Hope you all doing fine! I've tried to use the 'alias' directive in the indications.conf file but apparently it doesn't work.... It looks like maybe this feature was removed, because old sample for the indications.conf file have example using the alias parameter, but newer samples don't have it anymore.... also I couldn't find any ticket saying this parameter
2015 Mar 25
2
TRUNK Dial failed due to CONGESTION HANGUPCAUSE: 34
hello list, i have asterisk 11.15.0 and i have some trunks sip from my provider we have some ip phone astra 6731i each Ip-phone is configured with trunk and we call no ihave configured another trunk from the same provider in my asterisk i can call all numbers just the numbers are configured in thses ip phones. but when i configured the same trunk in x-lite i can call theses ip-phones without
2004 Dec 04
1
more DIALSTATUS/HANGUPSTATUS woes with IAX2
Phone - TDM430P - home* - IAX2 - office* - PRI - Telco I dial a busy number from the Phone. Home* shows this in the CLI: -- Executing Macro("Zap/1-1", "dial-wu|2922004") in new stack -- Executing Dial("Zap/1-1", "IAX2/andrew@wu-ast/2922004||g") in new stack -- Called andrew@wu-ast/2922004 -- Call accepted by wu-ast (format gsm) --
2013 Apr 01
0
Getting DIALSTATUS via agi
Hi all, Hopefully, I just need a second set of eyes on this one, but I just can't figure out what I'm doing wrong. I'm using an agi script to dial a number, check the dial result, and act accordingly. The problem is that I'm not getting anything back from DIALSTATUS, or HANGUPCAUSE. Here is the relevant perl code: ===============================================================
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]
2015 Feb 27
1
603 Declined > Dialstatus Busy
Hello Everyone. In my outbound contexts, I'm using "${DIALSTATUS}" to fail over to other routes if the chosen route rejects the call. Now, My current scenario is if I get "BUSY" back from the first provider, I send a busy back to my customer. If I get something like CHANUNAVAIL (Like a SIP 503) I advance to the next carrier and attempt the call. This works
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
2011 Apr 15
5
Possible bug in Hangup() (Asterisk 1.4.x)
Hello, On an Asterisk 1.4.33.1 in a simple scenario: [test] exten => _X.,1,Dial(SIP/12345 at peer01,,,) exten => i,1,Hangup(${HANGUPCAUSE}) exten => t,1,Hangup(${HANGUPCAUSE}) exten => h,1,Hangup(${HANGUPCAUSE}) I have noticed that no matter what value we set in the Hangup(<cause code>) commands, if the call is not answered by peer01 for any reason, the actual cause code
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 20
5
DIALSTATUS on CANCEL
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
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???
2017 Nov 14
2
RTCP + Stasis causing high memory consumption
Hello Asterisk list, I've facing a memory allocation issue that happens occasionally but on a consistent basis. The problem happens as follow, suddenly Asterisk starts consuming a lot of memory, in a rate of more than 1GB per hour. Kernel will eventually kill it via the OOM killer when memory is really exausted... This situation does not generate backtrace because Asterisk is responsive
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
2018 Nov 27
2
PJSIP add header on forwarded call
Le 27/11/2018 à 12:13, Joshua C. Colp a écrit : > On Tue, Nov 27, 2018, at 5:49 AM, Administrator TOOTAI wrote:[...] >> >> [TOOTAiAudio] >> ; >> ; Call our gateway >> >> exten = s,1,Set(PJSIP_HEADER(add,X-TOOTAiAudio-CALLED)=${ARG1}) >>  same = n,Dial(PJSIP/${ARG1}@TOOTAiAudio,,T) >>  same = n,Return >> >> exten = h,1,NoOp()