Woops, I think I mis-typed the proper terminology..<div><br></div><div>what I mean to say is that the caller is automatically hung-up after the consumer (or agent) disconnects the call (either by hangup, or pressing *). I would like instead for the caller to be passed back to the dialplan to continue execution.</div>
<div><br></div><div>--matt</div><div><br><div class="gmail_quote">On Tue, Mar 17, 2009 at 2:10 PM, Matt Hunter <span dir="ltr"><<a href="mailto:matt@hellohunter.com">matt@hellohunter.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have a situation where it would be useful for a consumer not to be hungup, after finishing the "fifo in" execution (when the agent disconnects the call or the agent hangs-up). The consumer is automatically hungup, in this situation. It would be preferable if the consumer channel went further along the dial plan. I thought I might get lucky implementing this setting with hangup_after_bridge to false, but fifo does not utilize this variable.<div>
<br></div><div>I tried looking thru the mod_fifo.c source, but my c skills are minimal. I also tried executing fifo in a lua app and setting setAutoHangup(false), but that also did not work. Any chance this could be done as a feature enhancement? Thanks.</div>
<div><br></div><font color="#888888"><div>--matt</div>
</font></blockquote></div><br></div>