[asterisk-app-dev] ChannelLeftBridge vs StasisEnd

Ben Merrills b.merrills at mersontech.co.uk
Mon Apr 18 08:34:26 CDT 2016


Hi Nitesh,

Neither of the events signify that channel has hungup. You should have another event Hangup when a channel is hung up, or destroyed if it’s part of an unanswered/timeout Originate (if I remember right).

How you decide to clean up or manage your code really depends on what you’re doing. When you say building a mixing bridge, do you mean a simple conference? Two way call? What you do in your code depends on what you want to happen when one party hangs up!

Skrusty

From: asterisk-app-dev-bounces at lists.digium.com [mailto:asterisk-app-dev-bounces at lists.digium.com] On Behalf Of Nitesh Bansal
Sent: 18 April 2016 14:18
To: Asterisk Application Development discussion <asterisk-app-dev at lists.digium.com>
Subject: [asterisk-app-dev] ChannelLeftBridge vs StasisEnd

Hello,
I'm building a mixing bridge with ARI and Asterisk 13.
Now when a channel hangs up, I can see two StasisEvents:
'ChannelLeftBridge' and 'StasisEnd'.
To me, there should be just one event when a channel hangs up, if
it hangs up, it should automatically leave the bridge.
Is there any specific order that these two events should come from
Asterisk?
Which event should I rely on to write the cleanup code for a channel?
Thanks,
Nitesh

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7539 / Virus Database: 4545/12056 - Release Date: 04/18/16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20160418/f423a536/attachment.html>


More information about the asterisk-app-dev mailing list