[Freeswitch-users] Option to hang-up both legs in a bridge

[Anthony Minessale]

did you see my reply to the other thread?

set the channel variable hangup_after_bridge=true on the a leg

your script must not be checking for the case when b leg hangs up that A leg
does not hangup unless that var is set.


On Fri, Dec 4, 2009 at 2:03 PM, Nik Middleton <
nik.middleton at noblesolutions.co.uk> wrote:

>  Hi,
>
>
>
> Is there an option to hang-up both call legs in a bridge when one leg hangs
> up?
>
>
>
> In my lua script I only ever see the hang-up for the call I’m in, not for
> the bridged b leg.  That said, I can see both a hang-up and un bridge event
> being fired for the B leg.  However my issue is that the A leg is still up,
> and if I’ve called 2 Pots numbers, the phone network will maintain the
> bridge.
>
>
>
> Is my only option to subscribe to the unbridge event and fire a hang-up
> event using the ‘other leg’ UID?
>
>
>
> Regards,
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>


-- 
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale at hotmail.com <MSN%3Aanthony_minessale at hotmail.com>
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com<PAYPAL%3Aanthony.minessale at gmail.com>
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org <sip%3A888 at conference.freeswitch.org>
iax:guest at conference.freeswitch.org/888
googletalk:conf+888 at conference.freeswitch.org<googletalk%3Aconf%2B888 at conference.freeswitch.org>
pstn:213-799-1400
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20091204/b3a7c9e0/attachment-0002.html