[Home]

Summary:ASTERISK-17068: ${CHANNEL} broken in 'failed' extension
Reporter:Jeremy Kister (jkister)Labels:
Date Opened:2010-12-05 11:25:23.000-0600Date Closed:2011-06-07 14:04:51
Priority:MinorRegression?No
Status:Closed/CompleteComponents:PBX/pbx_spool
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) callfile.txt
( 1) console.txt
( 2) console-answered.txt
( 3) extensions.conf
( 4) sip.conf
Description:the ${CHANNEL} variable is set to 'OutgoingSpoolFailed' instead of the real channel that the call came from.

   -- Executing [failed@alarm-ack:3] NoOp("OutgoingSpoolFailed", "CHANNEL is: OutgoingSpoolFailed") in new stack
   -- Auto fallthrough, channel 'Local/121@extensions-0fa2;2' status is 'NOANSWER'

I think ${CHANNEL} in this case should be "Local/121@extensions-0fa2;2"
Comments:By: Leif Madsen (lmadsen) 2010-12-07 13:16:04.000-0600

Can you please provide the entire console output and not just a snippet, along with the dialplan you are executing to get this condition? We need to be able to reproduce it and not enough information has been provided to do so.

By: Jeremy Kister (jkister) 2010-12-07 14:22:36.000-0600

to reproduce:

move the attached callfile.txt to /var/spool/asterisk/outgoing

don't answer the call when x143 rings.

By: Leif Madsen (lmadsen) 2011-01-18 10:12:23.000-0600

This might actually be what the MASTER_CHANNEL() dialplan function is for.