[Freeswitch-users] CHANNEL_HANGUP vs CHANNEL_HANGUP_COMPLETE

[Anthony Minessale]

As long as you are not looking for the CDR data?
The HANGUP_COMPLETE has more info in general because its after all the
detail processing.



On Fri, May 31, 2013 at 4:32 AM, Tihomir Culjaga <tculjaga at gmail.com> wrote:

> thanks for the info ...
>
> so we will use CHANNEL_HANGUP instead of CHANNEL_HANGUP_COMPLETE :=)
>
> T.
>
>
> On Wed, May 29, 2013 at 9:56 PM, Michael Jerris <mike at jerris.com> wrote:
>
>> 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 at 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 at gmail.com]
>> *To:* FreeSWITCH Users Help [mailto:freeswitch-users at 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 at 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 ?
>>>
>>>
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> 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
>>
>>
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> 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
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org
googletalk:conf+888 at conference.freeswitch.org
pstn:+19193869900
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130531/af434ded/attachment.html