Try:

cause = session:getVariable("originate_disposition")

cause2=session:getVariable("bridge_hangup_cause")

I'm not exactly sure what gets into which variable... But I think I needed both because sometimes "user_busy" was only in the second one. I'm not 100% sure...

Here's my production error script here: https://gist.github.com/4602781

(if the user accessed via a the calling card IVR, it passes them back to the menu. Otherwise, it hangs up on them. Remove or keep as appropriate.)

Please share your results if you are able to make it cleaner.

-Avi Marcus
BestFone

On Wed, Jan 23, 2013 at 5:18 AM, Benoit Raymond <benoit.raymond@amiconcept.com> wrote:

Hello,

Is there a way in lua to figure out why the b-leg hung up? I have an inbound call that I need to bridge so when lua is invoked, there is a session created for the inbound call and then I use session:execute(“bridge”, “the b-leg path”) and either the call is bridged or call_timeout kicks in. I need to continue my script based on the hangup cause whether the b-leg produced a NO_ANSWER, USER_BUSY or any other condition. The session:hangupCause is of no use since my session is still active.

I found the variable “bridge_hangup_cause” on the wiki but it returns nil if I do session:getVariable(“bridge_hangup_cause”).

I am using 1.3.13

Thanks much.

Benoit Raymond

AMI Concept Inc.
Business VoIP Solutions / Web Design
Phone: (450) 553-1231

http://www.amiconcept.com

_________________________________________________________________________
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