[Freeswitch-dev] hangup_after_bridge and intercept application

[Anthony Minessale]

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.

BTW,
you can execute transfer with the -bleg option to perform the transfer on
the opposite leg of the call.



On Thu, Aug 14, 2008 at 3:07 PM, Francisco de Ezcurra <
francisco at deezcurra.com.ar> wrote:

> The fix works if i hangup the channel that makes the intercept. The other
> leg
> goes back to the fifo. But when i hangup the other leg the channel that
> made
> the intercept is hung up.
>
> What I expect with this (ext. 2101)  dialplan is that the channel that
> makes
> the intercept executes the transfer to 2102 when the other leg hangs up.
>
> Is this possible? I can not use the variable api_hangup_hook on the channel
> created in the originate via MES because I don't know at that moment the
> other leg.
>
>
> Thanks
> Panchi
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20080814/bd191bd8/attachment.html