Hi David, Vitaly! Thank you for your answers. Will try to implement your advices. Best, Kirill 13.09.2012 14:52, Виталий Давудов пишет:
Hi, Kirill!
I solved it by adding lua-script after "bridge" application in my dialplan:
endpoint_disposition = session:getVariable("endpoint_disposition") last_bridge_hangup_cause = session:getVariable("last_bridge_hangup_cause") if (last_bridge_hangup_cause == "USER_BUSY" and endpoint_disposition == "EARLY MEDIA" ) then session:hangup(); end
You can see these variables by adding "info" application in the corresponding extension.
12.09.2012 17:53, iam пишет:
Hi Vitaly!
Did you ever solve this problem? I have the same continue_on_fail behaviour.
http://jira.freeswitch.org/browse/FS-4232
Vitaly added a comment - 26/Jun/12 3:14 AM Sorry for the long absence, but the problem is still actual for me. I replaced in my dialplan continue_on_fail to "true", but it's not give desired effect. May be some additional variables can help me?
Regards, Kirill
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Variable-continue-on-fail-tp74... Sent from the freeswitch-users mailing list archive at Nabble.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