On Mon, Mar 21, 2011 at 1:01 PM, Avi Marcus <avi@avimarcus.net> wrote:
You need ALL the conditions to match for freeswitch to do the action, and you can't change that!
I don't think so. If some condition evaluates to true, its nested actions are always executed no matter what preceded it. But of course the condition should be evaluated first, that's where various break values come into play.
No way - the dialplan is always run on a "match all conditions" to do the actions! How else would multiple conditions EVER work?
Completely wrong. And I don't see relevant logs in your message. Here is mine. A dialplan fragment: <extension name="condition-test"> <condition wday="6" break="never"/> <condition hour="9-18" break="on-true"> <action application="info"/> </condition> </extension> log: Dialplan: sofia/internal/1000@192.168.121.66 parsing [default->condition-test] continue=false Dialplan: sofia/internal/1000@192.168.121.66 Date/Time Match (FAIL) [condition-test] break=never Dialplan: sofia/internal/1000@192.168.121.66 Date/Time Match (PASS) [condition-test] break=on-true Dialplan: sofia/internal/1000@192.168.121.66 Action info() Guess what? The first condition fails but the action is still scheduled for execution (and indeed executed later) - Dmitry Bely