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

Danny Nicholas danny at debsinc.com
Fri Mar 18 10:14:37 CDT 2011


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

On Tue, 15 Mar 2011 11:44:20 -0500, "Danny Nicholas"
<danny at debsinc.com> wrote:
>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.

Thanks for the info. After calling out through a call file, Asterisk
plays the MOH and detects that the callee has hung up, but either
doesn't jump to the extension or does jump to "h" but ${REASON} is
empty:

===============
[callback]
;how to wait until callee has answered?
exten => start,1,Wait(2)
exten => start,n,NoOp(${DEVICE_STATE(Dahdi/1)})

exten => start,n,Answer()

exten => start,n,Playback(manolo_camp-morning_coffee)
;exten => start,n,Hangup()
exten => start,n,Goto(${EXTEN}-${REASON})

;not run
;exten => failed,1,NoOp(Call ended with ${REASON})

;not run
;exten => s,1,NoOp(Call ended with ${REASON})

;empty
;exten => h,1,NoOp(Call ended with ${REASON})

;not run
exten => start-NOANSWER,1,NoOp(Call ended with ${REASON})
===============

Is this what you had in mind?

Thank you.

That's the ticket.




More information about the asterisk-users mailing list