On Sun, Dec 26, 2010 at 5:49 PM, Avi Marcus <
Avi@amarcus.com> wrote:
> I have two xml config files with time of day routing, and I couldn't imagine
> why when it reached the first one, it just skipped the rest of the xml
> files, as such:
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 parsing [default->YLE1]
> continue=false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Regex (PASS) [YLE1]
> destination_number(t1105) =~ /^t1105$/ break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Date/Time Match (FAIL)
> [YLE1] break=on-false
> 2010-12-27 01:36:09.410521 [DEBUG] switch_core_state_machine.c:119
> (sofia/internal/
sip:1000@109.67.185.37:5072) State Change CS_ROUTING ->
> CS_EXECUTE
> But when I just edit the first and set continue=true, it suddenly now
> properly moves on. But it never matched the entire extension's condition
> tags, so why did it think it should not continue?
> (xml files here:
http://pastebin.freeswitch.org/14885)
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 parsing [default->YLE1]
> continue=true
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Regex (PASS) [YLE1]
> destination_number(t1105) =~ /^t1105$/ break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Date/Time Match (FAIL)
> [YLE1] break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 parsing [default->YLE2]
> continue=false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Regex (PASS) [YLE2]
> destination_number(t1105) =~ /^t1105$/ break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Date/Time Match (PASS)
> [YLE2] break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 Regex (FAIL) [YLE2]
> time-of-day() =~ /08:00-22:00/ break=on-false
> Dialplan: sofia/internal/
sip:1000@109.67.185.37:5072 ANTI-Action
> voicemail(default ${domain} 1105)
> 2010-12-27 01:37:24.754671 [DEBUG] switch_core_state_machine.c:119
> (sofia/internal/
sip:1000@109.67.185.37:5072) State Change CS_ROUTING ->
> CS_EXECUTE
> And - it seems the anti-action is triggered no matter how "off" 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's stopping the rest of my dial plan from
> executing.
> When would one ever want an anti-action other than as his last <extension>
> in which case it could just be a new last extension with no condition tag. I
> don't understand why you would ever want them.
> Understanding would be appreciated :)
> -Avi Marcus