Accessing fax variables/status after rxfax/txfax
Hello everyone, Looking through the code it appears that txfax/rxfax automatically hangup channels when they're called and set a hangup cause that more or less makes sense depending on how the fax went. My question is - can I have them not hangup the channel automatically so I can continue execution somehow? Alternatively, can I somehow continue execution based on the hangup cause? I'm thinking something like api_hangup_hook that has access to the hangup/fax status. Thanks! -- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.com
On Thu, Oct 21, 2010 at 10:45 AM, Kristian Kielhofner <kris@kriskinc.com>wrote:
Hello everyone,
Looking through the code it appears that txfax/rxfax automatically hangup channels when they're called and set a hangup cause that more or less makes sense depending on how the fax went. My question is - can I have them not hangup the channel automatically so I can continue execution somehow? Alternatively, can I somehow continue execution based on the hangup cause? I'm thinking something like api_hangup_hook that has access to the hangup/fax status.
Kristian, I think you need this: http://wiki.freeswitch.org/wiki/Channel_Variables#session_in_hangup_hook It will let the call hang up but a copy of the session will be available to your hangup hook so you can access all the channel variables even after the channel has actually hung up. -MC
Dang, that's a big page! Did I really make that many vars =0 On Thu, Oct 21, 2010 at 7:57 PM, Michael Collins <msc@freeswitch.org> wrote:
On Thu, Oct 21, 2010 at 10:45 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
Hello everyone,
Looking through the code it appears that txfax/rxfax automatically hangup channels when they're called and set a hangup cause that more or less makes sense depending on how the fax went. My question is - can I have them not hangup the channel automatically so I can continue execution somehow? Alternatively, can I somehow continue execution based on the hangup cause? I'm thinking something like api_hangup_hook that has access to the hangup/fax status.
Kristian,
I think you need this: http://wiki.freeswitch.org/wiki/Channel_Variables#session_in_hangup_hook
It will let the call hang up but a copy of the session will be available to your hangup hook so you can access all the channel variables even after the channel has actually hung up. -MC
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
On Thu, Oct 21, 2010 at 8:57 PM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
Dang, that's a big page! Did I really make that many vars =0
Yeah, and we we're still finding vars we haven't documented yet. :P -MC
participants (3)
-
Anthony Minessale
-
Kristian Kielhofner
-
Michael Collins