If you are writing a cdr module, you should be using the on_reporting state handler, not the event handler for hangup complete.

Mike

On May 29, 2013, at 3:02 PM, Dave R. Kompel <drk@drkngs.net> wrote:

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.
 
--Dave

From: Anthony Minessale [mailto:anthony.minessale@gmail.com]
To: FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org]
Sent: Wed, 29 May 2013 11:19:02 -0700
Subject: Re: [Freeswitch-users] CHANNEL_HANGUP vs CHANNEL_HANGUP_COMPLETE

Hangup is when it hangs up, hangup_complete is after the cdr processing is complete right before destroy.



On Tue, May 28, 2013 at 3:50 PM, Tihomir Culjaga <tculjaga@gmail.com> wrote:
hello


im wondering what should we track as hangup event ... CHANNEL_HANGUP or CHANNEL_HANGUP_COMPLETE ...

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.

now , A hangs up, FS sends just CHANNEL_HANGUP event ... not CHANNEL_HANGUP_COMPLETE ...


im wondering if it is supposed to be like that or we need to get CHANNEL_HANGUP_COMPLETE ?