[asterisk-users] [1.4] Failed callfile doesn't jump to "failed"extension

[Danny Nicholas]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Gilles
Sent: Tuesday, March 15, 2011 11:31 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] [1.4] Failed callfile doesn't jump to
"failed"extension

Hello

	For some reason, when dialing out through a call file and the remote
line is busy, Asterisk doesn't jump to the "failed" extension in the
context used by the call file:

====== call file
Channel: Zap/1/5551234
Context: callbacktest
Extension: start
Priority: 1
MaxRetries: 1

====== extension.conf
[callbacktest]
exten => start,1,NoOp(Status is ${DIALSTATUS})
exten => start,n,Wait(10)
exten => start,n,Hangup

exten => failed,1,NoOp(Reason call file failed is ${REASON})

====== CLI
ip04*CLI>
-- Attempting call on Zap/1/5551234 for start at callbacktest:1 (Retry 1)
   > Channel Zap/1-1 was answered.
== Starting Zap/1-1 at callbacktest,start,1 failed so falling back to
exten 's'
== Starting Zap/1-1 at callbacktest,s,1 still failed so falling back
to context 'default'
-- Hungup 'Zap/1-1'
[Mar 15 16:22:11] NOTICE[368]: pbx_spool.c:351 attempt_thread: Call
completed to Zap/1/5551234
======

I followed this tutorial, and don't understand why Asterisk tries to
jump to extension "s":

www.voip-info.org/wiki/view/Asterisk+auto-dial+out

Thank you.

Don't depend on the tutorials you read to be 100% accurate or up-to-date.
The default action on a failure in Asterisk is usually going to be an "s"
jump, either to s,1 or s+100.  Personally, I would replace failed,1 with
start-NOANSWER,1.