Sangoma Netborder SS7, User Manual

Page: 157 / 317

v1.14
157
<action application="sleep" data="500"/>
<action application="playback" data="ivr/ivr-welcome_to_freeswitch.wav"/>
<action application="sleep" data="500"/>
</condition>
<condition field="${calling_user}" expression="^loser$">
<action application="playback" data="ivr/ivr-dude_you_suck.wav"/>
<anti-action application="playback" data="ivr/ivr-dude_you_rock.wav"/>
</condition>
</extension>
<extension name="Regex XOR example 3" continue="true">
<condition regex="xor">
<!-- If only one of these is true then the subsequent actions are added to execute list -->
<regex field="caller_id_name" expression="Some User"/>
<regex field="caller_id_number" expression="^1001$"/>
<action application="log" data="INFO Only one of the conditions matched!"/>
<!-- If *none* of the regexes is true then the anti-actions are added to the execute list -->
<anti-action application="log" data="WARNING None of the conditions matched!"/>
</condition>
</extension>
Basically, for this new syntax you can have a condition to have a "regex" attr instead of "field" and
"expression" etc. When there is a "regex" attr, that means you plan to have one or more <regex> tags
that are similar to the condition tag itself that it has field and expression in it.
The value of the "regex" attr is either "all" or "any" or "xor indicating if all expressions must match or
just any expression or only one must match(xor) . If it's set to "any" it will stop testing the regex tags
as soon as it finds one match, if it is set to "all", it will stop as soon as it finds one failure.
From there it will behave like a normal condition tag either executing the actions or anti-actions and
breaking based on the "break" attr.
The basic difference here is once there is a "regex" attr, the <regex> tags parsed for "all" or "any"
take the place of the single "field" and "condition"
NOTE: Also, if any captures are done in the "expression" attrs of a <regex> tag, only the data from
the newest capture encountered will be considered in the $n expansion or FIELD_DATA creation. In
addition, you can set DP_REGEX_MATCH_1 .. DP_REGEX_MATCH_N to preserve captures into
arrays.
<extension name="Inbound_external">