<div dir="ltr"><div>I have two xml config files with time of day routing, and I couldn&#39;t imagine why when it reached the first one, it just skipped the rest of the xml files, as such:</div><div><br></div><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> parsing [default-&gt;YLE1] continue=false</div>

<div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Regex (<b>PASS</b>) [<b>YLE1</b>] destination_number(t1105) =~ /^t1105$/ break=on-false</div><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Date/Time Match (<b>FAIL</b>) [<b>YLE1</b>] break=on-false</div>

<div>2010-12-27 01:36:09.410521 [DEBUG] switch_core_state_machine.c:119 (sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a>) State Change CS_ROUTING -&gt; CS_EXECUTE</div><div><br>

</div><div>But when I just edit the first and set continue=true, it suddenly now properly moves on. But it never matched the entire extension&#39;s condition tags, so why did it think it should not continue?</div><div>(xml files here: <a href="http://pastebin.freeswitch.org/14885">http://pastebin.freeswitch.org/14885</a>) </div>

<div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> parsing [default-&gt;YLE1] continue=true</div>

<div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Regex (PASS) [YLE1] destination_number(t1105) =~ /^t1105$/ break=on-false</div><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Date/Time Match (FAIL) [YLE1] break=on-false</div>

<div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> parsing [default-&gt;YLE2] continue=false</div><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Regex (PASS) [YLE2] destination_number(t1105) =~ /^t1105$/ break=on-false</div>

<div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Date/Time Match (PASS) [YLE2] break=on-false</div><div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> Regex (FAIL) [YLE2] time-of-day() =~ /08:00-22:00/ break=on-false</div>

<div>Dialplan: sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a> ANTI-Action voicemail(default ${domain} 1105) </div><div>2010-12-27 01:37:24.754671 [DEBUG] switch_core_state_machine.c:119 (sofia/internal/<a href="http://sip:1000@109.67.185.37:5072">sip:1000@109.67.185.37:5072</a>) State Change CS_ROUTING -&gt; CS_EXECUTE</div>

<div><br></div><div>And - it seems the anti-action is triggered no matter how &quot;off&quot; we are, is there a way to have a less agressive anti action? E.g. it only activates if the first condition is true? It&#39;s stopping the rest of my dial plan from executing.</div>

<div>When would one ever want an anti-action other than as his last &lt;extension&gt; in which case it could just be a new last extension with no condition tag. I don&#39;t understand why you would ever want them.</div><div>

<br></div><div>Understanding would be appreciated :)</div><div>-Avi Marcus</div></div>