asterisk users - Oct 2009 - Busy app timeout

Using 1.4 svn, I want to implent the busy application.

With the following dialplan:

[inboundqueue]

exten => _X.,1,Answer()
exten => _X.,n,Goto(dropcall,1)

...

exten => dropcall,1,Busy(10)
exten => dropcall,n,hangup()

If I call any number in the inboundqueue, I get the following:

[Oct  1 12:06:44]     -- Executing [444678 at isdnspan1:1]
Answer("Zap/1-1", "") in new stack
[Oct  1 12:06:44]     -- Executing [444678 at inboundqueue:2]
Goto("Zap/1-1", "1?dropcall|1") in new stack
[Oct  1 12:06:44]     -- Goto (inboundqueue,dropcall,1)
[Oct  1 12:06:44]     -- Executing [dropcall at inboundqueue:1]
Busy("Zap/1-1", "10") in new stack
[Oct  1 12:06:44]   == Spawn extension (inboundqueue, dropcall, 1)
exited non-zero on 'Zap/1-1'

why does the busy not wait for 10 seconds before dropping the zap channel ?

show application Busy
foxtrot*CLI>
  -= Info about application 'Busy' =-

[Synopsis]
Indicate the Busy condition

[Description]
  Busy([timeout]): This application will indicate the busy condition to
the calling channel. If the optional timeout is specified, the calling channel
will be hung up after the specified number of seconds. Otherwise, this
application will wait until the calling channel hangs up.

Julian Lyndon-Smith wrote:
> Using 1.4 svn, I want to implent the busy application.
> 
> With the following dialplan:
> 
> [inboundqueue]
> 
> exten => _X.,1,Answer()
> exten => _X.,n,Goto(dropcall,1)
> 
> ...
> 
> exten => dropcall,1,Busy(10)
> exten => dropcall,n,hangup()
> 
> If I call any number in the inboundqueue, I get the following:
> 
> [Oct  1 12:06:44]     -- Executing [444678 at isdnspan1:1]
> Answer("Zap/1-1", "") in new stack
> [Oct  1 12:06:44]     -- Executing [444678 at inboundqueue:2]
> Goto("Zap/1-1", "1?dropcall|1") in new stack
> [Oct  1 12:06:44]     -- Goto (inboundqueue,dropcall,1)
> [Oct  1 12:06:44]     -- Executing [dropcall at inboundqueue:1]
> Busy("Zap/1-1", "10") in new stack
> [Oct  1 12:06:44]   == Spawn extension (inboundqueue, dropcall, 1)
> exited non-zero on 'Zap/1-1'
> 
> why does the busy not wait for 10 seconds before dropping the zap channel ?
Because (based on your log) the call came in over an ISDN circuit, and
when you run the Busy application Asterisk sends a 'BUSY' indication to
the calling switch, which then tears down the call. The timeout
specified to Busy() is only relevant for channel types where the calling
end will not drop the call on its own (like an analog channel).

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kpfleming at digium.com
Check us out at www.digium.com & www.asterisk.org