[Asterisk-Dev] DISA broken

Benjamin Miller BGMiller at dccinc.com
Thu Jun 5 08:56:33 MST 2003

It would seem more consistent with the rest of the system if it simply
used the same digittimeout values that the main dial plan itself uses.
My understanding is that DISA is supposed to give you the same behavior
as if you were at a handset in the target context.  Adding arbitrary
terminators such as the "#" defeats this purpose.  I would vote for
simply using the digittimeout and if that does not work properly, for
_X. extensions that is a dial plan issue, not a DISA issue.   Possibly,
If DISA needs a dialing terminator, it should be an option on the
argument list.

-----Original Message-----
From: John Todd [mailto:jtodd at loligo.com] 
Sent: Wednesday, June 04, 2003 4:21 PM
To: asterisk-dev at lists.digium.com
Subject: Re: [Asterisk-Dev] DISA broken

Yes, that is the case.

Perhaps DISA can be told to wait for an optional timeout or "enter 
key" such as "#" before executing the match?


>I bet you have _X. in your outbound dial context, or something similar.

>DISA sees the "1" as matching that pattern and is taking it.  Let me 
>try to work on a fix for this.  Find me on IRC and beat me over the 
>head if you want it done.
>p.s.  Mom wants this feature too, believe it or not.
>On Tue, 3 Jun 2003, John Todd wrote:
>>  As noted in earlier mail, DISA does not work as expected.  It does  
>> not "collect" digits, and executes on the first digit pressed,  
>> leading almost always to dialing failure (unless you happen to have a
>>  single digit dialplan.)   I am calling it from a Zap line.
>>  I get the dialtone, but then pressing any key leaps to the context  
>> specified (in my example, "Outbound-Dial") with the single digit as  
>> ${EXTEN}.
>>  This extension in in the location where my Zap lines terminate:
>>  exten => 1999,1,DISA(no-password,Outbound-Dial)
>>  *CLI>     -- Starting simple switch on 'Zap/1-1'
>>  NOTICE[122896]: File chan_zap.c, Line 4134 (ss_thread): Got event 2
>>  (Ring/Answered)...
>>       -- Executing NoOp("Zap/1-1", "") in new stack
>>       -- Executing NoOp("Zap/1-1", "") in new stack
>>       -- Executing DigitTimeout("Zap/1-1", "9") in new stack
>>       -- Set Digit Timeout to 9
>>       -- Executing BackGround("Zap/1-1", "demo-congrats") in new
>>       -- Playing 'demo-congrats'
>>       -- Executing DISA("Zap/1-1", "no-password|Outbound-Dial") in 
>>new stack
>>  [I type 1999, get the dialtone, and press "1"]
>>  WARNING[122896]: File cdr.c, Line 224 (ast_cdr_init): CDR already
>>  initialized on 'Zap/1-1'
>>       -- Executing NoOp("Zap/1-1", "") in new stack
>>       -- Executing SetMusicOnHold("Zap/1-1", "random") in new stack
>>       -- Executing Goto("Zap/1-1", "Outbound-Dial-post|1|1") in new
>>       -- Goto (Outbound-Dial-post,1,1)
>>  WARNING[122896]: File pbx.c, Line 1726 (ast_pbx_run): Channel
>>  'Zap/1-1' sent into invalid extension '1' in context
>>  'Outbound-Dial-post', but no invalid handler
>>       -- Executing Macro("Zap/1-1", "record-cleanup") in new stack
>>  Expression is '1'
>>       -- Executing GotoIf("Zap/1-1", "1?5:2") in new stack
>>       -- Goto (macro-record-cleanup,s,5)
>>       -- Executing NoOp("Zap/1-1", "") in new stack
>>       -- Executing Hangup("Zap/1-1", "") in new stack
>>     == Spawn extension (macro-record-cleanup, s, 6) exited non-zero
>>  'Zap/1-1' in macro 'record-cleanup'
>>     == Spawn extension (Outbound-Dial-post, h, 1) exited non-zero 
>>on 'Zap/1-1'
>>       -- Hungup 'Zap/1-1'
>  > JT
>  >
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com

More information about the asterisk-dev mailing list