On Fri, 18 Mar 2011 16:48:28 -0700 (PDT), Steve Edwards
asterisk@sedwards.com wrote:
Somehow, I'm guessing that 'failed' means that something failed while
processing the call file or that the call failed to answer, not that
somebody terminated the call.
Thanks guys. After testing with a PCI
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Gilles
Sent: Friday, March 18, 2011 10:45 AM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] [1.4] Failed callfile doesn't
jumptofailedextension
On Behalf Of Gilles
Unfortunately, it can only jump to h, and ${REASON} is empty.
On Fri, 18 Mar 2011, Danny Nicholas wrote:
I believe you will achieve the desired result by replacing ${REASON}
with ${HANGUP_CAUSE}.
REASON is documented as being valid in the 'failed' extension. If it is
On Fri, 18 Mar 2011 10:08:52 -0700 (PDT), Steve Edwards
asterisk@sedwards.com wrote:
On Fri, 18 Mar 2011, Danny Nicholas wrote:
I believe you will achieve the desired result by replacing ${REASON}
with ${HANGUP_CAUSE}.
REASON is documented as being valid in the 'failed' extension. If it is
On 03/18/2011 05:43 PM, Gilles wrote:
On Fri, 18 Mar 2011 10:08:52 -0700 (PDT), Steve Edwards
asterisk@sedwards.com wrote:
On Fri, 18 Mar 2011, Danny Nicholas wrote:
I believe you will achieve the desired result by replacing ${REASON}
with ${HANGUP_CAUSE}.
REASON is documented as being
On Fri, 18 Mar 2011 17:56:12 -0500, Anthony Messina
amess...@messinet.com wrote:
You need to define the 'failed' extension in your context to have the
${REASON} variable set (I've found).
exten = failed,1,NoOp(Failure reason is: ${REASON})
Thanks but for some reason, after calling out through a
On Sat, 19 Mar 2011, Gilles wrote:
Thanks but for some reason, after calling out through a call file,
Asterisk doesn't jump to it although the callee hangs up while
Asterisk is still playing:
Somehow, I'm guessing that 'failed' means that something failed while
processing the call file or
