Ahh right now I get what you are saying, I thought from the wiki that I would have to set the feature on and then tell it what cause codes I wanted to trap. Will fix up my dialplan cause I don't want it to trap other causes for this scenario.
Thanks! On Tue, May 26, 2009 at 6:09 PM, Jason White <[email protected]> wrote: > Jim Burke <[email protected]> wrote: >> If I understand your comment correctly, I did not have both of the >> above snippets in the dialplan at the same time. The dialplan was >> modified continually to get the correct vars that worked for my >> situation and then reloadxml to get them working. > > Right, you can't have > <action application="set" data="continue_on_fail=79"/> > <action application="set" data="continue_on_fail=true"/> > one after the other like this, because it is equivalent to > <action application="set" data="continue_on_fail=true"/> > since you're overriding the setting of the variable in the very next line. > > > _______________________________________________ > Freeswitch-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > _______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
