Just remember that once the call ends, the "session" object you have is read-only. You can still do interesting things, but you cannot alter CDRs after the call ends, at least not in a session hangup hook. You are better off with XML CDRs and post-call logic. With all of the screwy transfer scenarios you have to account for you will absolutely need to do some post-processing logic. Sounds like lots of "fun". :P -MC On Wed, Aug 3, 2011 at 12:14 PM, Isaac Jurado <ijurado@econcept.es> wrote:
On Wed, Aug 3, 2011 at 7:56 PM, Avi Marcus <avi@avimarcus.net> wrote:
If the channel is hung up, then it's hung up.. that's what the hangup hook is, afaik. If you look at the wiki page for this: http://wiki.freeswitch.org/wiki/Variable_session_in_hangup_hook it only says that you can "access" the variable, not that the channel still exists or that you can set them.
It looks that the session object is only available through bindings like mod_lua. I'll have to check
Why do you need to use a hangup hook to set a variable? can't you set it at the start? Or import B leg into A leg's CDRs?
It's a bit tricker than that. We are trying to implement a stateless CDR processing and billing mechanism that works also across call transfers.
As I said, we will probably end up defining a Lua hook.
Thanks again for your quick response.
Cheers.
-- Isaac Jurado Internet Busines Solutions eConcept
_______________________________________________ Join us at ClueCon 2011, Aug 9-11, Chicago http://www.cluecon.com 877-7-4ACLUE
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