<div dir="ltr">As long as you are not looking for the CDR data?<div>The HANGUP_COMPLETE has more info in general because its after all the detail processing.</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, May 31, 2013 at 4:32 AM, Tihomir Culjaga <span dir="ltr"><<a href="mailto:tculjaga@gmail.com" target="_blank">tculjaga@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">thanks for the info ...<div><br></div><div>so we will use CHANNEL_HANGUP instead of CHANNEL_HANGUP_COMPLETE :=)</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>T.</div></font></span></div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">
On Wed, May 29, 2013 at 9:56 PM, Michael Jerris <span dir="ltr"><<a href="mailto:mike@jerris.com" target="_blank">mike@jerris.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div style="word-wrap:break-word">If you are writing a cdr module, you should be using the on_reporting state handler, not the event handler for hangup complete.<div><br></div><div>Mike</div><div><div><br><div>
<div>On May 29, 2013, at 3:02 PM, Dave R. Kompel <<a href="mailto:drk@drkngs.net" target="_blank">drk@drkngs.net</a>> wrote:</div><br><blockquote type="cite"><div style="font-style:normal;font-variant:normal;font-weight:normal;font-size:10pt;line-height:normal;font-family:Tahoma,Verdana,sans-serif;letter-spacing:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div>Also worth noting, CHANNEL_HANGUP_COMPLETE is the event you use to write CDRs if you're going to do your own CDR module, or do it external.</div><div> </div><div>--Dave</div><br><blockquote style="border-left-color:rgb(0,0,255);border-left-width:2px;border-left-style:solid;padding-left:5px;margin-left:5px;margin-right:0px">
<hr><b>From:</b><span> </span>Anthony Minessale [mailto:<a href="mailto:anthony.minessale@" target="_blank">anthony.minessale@</a><a href="http://gmail.com" target="_blank">gmail.com</a>]<br><b>To:</b><span> </span>FreeSWITCH Users Help [mailto:<a href="mailto:freeswitch-" target="_blank">freeswitch-</a><a href="mailto:users@lists.freeswitch.org" target="_blank">users@lists.freeswitch.org</a>]<br>
<b>Sent:</b><span> </span>Wed, 29 May 2013 11:19:02 -0700<br><b>Subject:</b><span> </span>Re: [Freeswitch-users] CHANNEL_HANGUP vs CHANNEL_HANGUP_COMPLETE<br><br><div>Hangup is when it hangs up, hangup_complete is after the cdr processing is complete right before destroy.<div>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 3:50 PM, Tihomir Culjaga<span> </span><span><<a href="mailto:tculjaga@gmail.com" target="_blank">tculjaga@gmail.com</a>></span><span> </span>wrote:<br>
<blockquote class="gmail_quote" style="border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid;margin:0px 0px 0px 0.8ex;padding-left:1ex"><div>hello<div><br></div><div><br></div><div>im wondering what should we track as hangup event ... CHANNEL_HANGUP or CHANNEL_HANGUP_COMPLETE ...</div>
<div><br></div><div>i have a situation where A calls FS, an ESL application answers this call, originates a new call to B and bridges A and B... than ESL originate another call towards C and joins all 3 channels into a conference.</div>
<div><br></div><div>now , A hangs up, FS sends just CHANNEL_HANGUP event ... not CHANNEL_HANGUP_COMPLETE ...</div><div><br></div><div><br></div><div>im wondering if it is supposed to be like that or we need to get CHANNEL_HANGUP_COMPLETE ?</div>
<span><font color="#888888"><div><br></div></font></span></div></blockquote></div></div></blockquote></div></blockquote></div><br></div></div></div><br></div></div><div class="im">_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></div></blockquote></div><br></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900
</div>