Summary: | ASTERISK-04483: Dialplan timeout problem | ||
Reporter: | tbclark (tbclark) | Labels: | |
Date Opened: | 2005-06-26 06:07:27 | Date Closed: | 2008-01-15 15:39:54.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Beginning some time since the CVS-HEAD of 6/20/2005, a problem developed with this dialplan that depend on a timeout. The example I quote below is on a zap channels, but it exists on other channel types as well. Referring to the dialplan below, a call coming into the [nancymenu] context can successfully press '0' to transfer to the [mainmenu] context. However, a call that waits 7 seconds to get the default transfer to the [internal] context results in the channel disconnecting instead of getting transferred. The [general] section of the dialplan already contains autofallthrough=no, although I am not sure why that would make any difference. The dialplan is not at an endpoint when Asterisk hangs up the channel. It never goes to the 't' extension. ****** ADDITIONAL INFORMATION ****** Here is the relevant part of the dialplan: [nancymenu] exten => fax,1,Goto(internal,201,1) exten => s,1,Answer exten => s,2,Set(TIMEOUT(response)=7) exten => s,3,Background(clark-nancymain) exten => t,1,Goto(internal,nancy,1) exten => 0,1,Goto(mainmenu,s,1) exten => i,1,Playback(invalid) include => internal Here is what happens when a call comes into the context: -- Executing Goto("Zap/23-1", "nancymenu|s|1") in new stack -- Goto (nancymenu,s,1) -- Executing Answer("Zap/23-1", "") in new stack -- Executing Set("Zap/23-1", "TIMEOUT(response)=7") in new stack -- Response timeout set to 7 -- Executing BackGround("Zap/23-1", "clark-nancymain") in new stack -- Playing 'clark-nancymain' (language 'en') == Auto fallthrough, channel 'Zap/23-1' status is 'UNKNOWN' -- Hungup 'Zap/23-1' | ||
Comments: | By: zamsler (zamsler) 2005-06-27 13:53:01 I am seeing the same issue. Calls are coming in on ZAP. I also get == Auto fallthrough, channel 'Zap/foo' status is 'UNKNOWN' -- Hungup 'Zap/foo' I set the time outs to 20, but it still hangs up. By: SIP:ian@txrx.ca (weezey) 2005-07-04 08:21:01 The solution: Add the following to your extensions in that context. exten => s,4,WaitExten By: tbclark (tbclark) 2005-07-04 11:09:16 Using WaitExten is unrelated to the question of the 't' extension. After I figured out there was a problem, I removed all of my 't' extensions, and rewrote the dialplan to use only the WaitExten function, so I no longer have a personal interest in getting this fixed. It is, however, still an Asterisk issue. By: SIP:ian@txrx.ca (weezey) 2005-07-04 11:12:53 Agreed. It's basically just ignoring the autofallthrough setting which it shouldn't do. By: Kevin P. Fleming (kpfleming) 2005-07-05 15:24:04 Fixed in CVS HEAD. For a quick fix you can noload pbx_ael.so to get around the problem. By: Digium Subversion (svnbot) 2008-01-15 15:39:54.000-0600 Repository: asterisk Revision: 6028 U trunk/pbx/pbx_ael.c ------------------------------------------------------------------------ r6028 | kpfleming | 2008-01-15 15:39:54 -0600 (Tue, 15 Jan 2008) | 2 lines don't force autofallthrough to on (bug ASTERISK-4483) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=6028 |