Hey Gabe, thanks for these suggestions. I actually found out that a LUA script that is called in a hangup hook will receive the the full landscape of the env variables, including the hangup_cause. Thanks a bunch, I'm glad I escaped your famous replies. :P Cheers, Emrah On Nov 6, 2012, at 1:33 AM, Gabriel Gunderson <gabe@gundy.org> wrote:
On Mon, Nov 5, 2012 at 1:01 PM, Emrah <lists@kavun.ch> wrote:
It makes sense that hangup_cause is blank because at the time the variable is set, the channel hasn't been hanged-up…
Depending on what you're doing, you may have to look to the CS_REPORTING state. This is where you get your CDRs written out to disk, HTTP, DB or whatever.
http://wiki.freeswitch.org/wiki/Channel_States
Is listening on the event socket an option? How about watching for CDRs to be written to disk?
Good luck, Gabe
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org