<div dir="ltr">The extension that executed the intercept app is the one that will be able to move on in the dialplan after the call because it's the effective A leg and that is the extension that had a dialplan instruction set.<br>
<br>BTW,<br>you can execute transfer with the -bleg option to perform the transfer on the opposite leg of the call.<br><br><br><br><div class="gmail_quote">On Thu, Aug 14, 2008 at 3:07 PM, Francisco de Ezcurra <span dir="ltr"><<a href="mailto:francisco@deezcurra.com.ar">francisco@deezcurra.com.ar</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The fix works if i hangup the channel that makes the intercept. The other leg<br>
goes back to the fifo. But when i hangup the other leg the channel that made<br>
the intercept is hung up.<br>
<br>
What I expect with this (ext. 2101) dialplan is that the channel that makes<br>
the intercept executes the transfer to 2102 when the other leg hangs up.<br>
<br>
Is this possible? I can not use the variable api_hangup_hook on the channel<br>
created in the originate via MES because I don't know at that moment the<br>
other leg.<br>
<br>
<br>
Thanks<br>
Panchi<br>
<br>
<br></blockquote></div><br>
</div>