<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><base href="x-msg://27767/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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><br><div><div>On May 29, 2013, at 3:02 PM, Dave R. Kompel <<a href="mailto:drk@drkngs.net">drk@drkngs.net</a>> wrote:</div><br class="Apple-interchange-newline"><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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 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; position: static; z-index: auto; "><hr><b>From:</b><span class="Apple-converted-space"> </span>Anthony Minessale [mailto:anthony.minessale@<a href="http://gmail.com">gmail.com</a>]<br><b>To:</b><span class="Apple-converted-space"> </span>FreeSWITCH Users Help [mailto:freeswitch-<a href="mailto:users@lists.freeswitch.org">users@lists.freeswitch.org</a>]<br><b>Sent:</b><span class="Apple-converted-space"> </span>Wed, 29 May 2013 11:19:02 -0700<br><b>Subject:</b><span class="Apple-converted-space"> </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 class="Apple-converted-space"> </span><span><<a href="mailto:tculjaga@gmail.com">tculjaga@gmail.com</a>></span><span class="Apple-converted-space"> </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; position: static; z-index: auto; "><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 class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></blockquote></div></div></blockquote></div></blockquote></div><br></div></body></html>