Skip to content

F
freeswitch
切换分支/标签
  1. 13 8月, 2006 4 次提交
  3. 12 8月, 2006 3 次提交
  5. 11 8月, 2006 9 次提交
  7. 09 8月, 2006 1 次提交
  9. 07 8月, 2006 6 次提交
  11. 01 8月, 2006 2 次提交
  13. 31 7月, 2006 2 次提交
  15. 29 7月, 2006 1 次提交
  17. 28 7月, 2006 1 次提交
  19. 27 7月, 2006 4 次提交
  21. 26 7月, 2006 7 次提交
    • Brian West's avatar
      git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2172… · b7f075ec
      由 Brian West 提交于 
      git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2172 d0543943-73ff-0310-b7d9-9358b9ac24b2
      b7f075ec
    • Brian West's avatar
      Small name changes to reflect the actual module name. · 6f44fc9e
      由 Brian West 提交于 
      /b


git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2171 d0543943-73ff-0310-b7d9-9358b9ac24b2
      6f44fc9e
    • Brian West's avatar
      Adding linker options. · f077c889
      由 Brian West 提交于 
      
git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2170 d0543943-73ff-0310-b7d9-9358b9ac24b2
      f077c889
    • Anthony Minessale's avatar
      dox · 3481f29c
      由 Anthony Minessale 提交于 
      git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2169 d0543943-73ff-0310-b7d9-9358b9ac24b2
      3481f29c
    • Brian West's avatar
      Trying to solve dyld_stub_binding_helper issue on PPC · 4e32a890
      由 Brian West 提交于 
      /b



git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2168 d0543943-73ff-0310-b7d9-9358b9ac24b2
      4e32a890
    • Anthony Minessale's avatar
      Modify XML Dialplan · c4d890e0
      由 Anthony Minessale 提交于 
      BTW, forget what I said yesterday RE: the strftime app I was at McDonalds, how can I concentrate there eh? 
see below....


The Definitive Guide To XML Dialplan:

The "dialplan" section of the freeswitch.xml meta document may contain several contexts

<?xml version="1.0"?>
<document type="freeswitch/xml">
  <section name="dialplan" description="Regex/XML Dialplan">
    <!-- the default context is a safe start -->
    <context name="default">

    <!-- one or more extension tags -->

    </context>
    
    <!-- more optional contexts -->
  </section>
</document>

The important thing to remember is that the dialplan is parsed once when the call
hits the dialplan parser in the RING state.  With one pass across the XML the result
will be a complete list of instructions installed into the channel based on
 parsed <action> or <anti-action> tags.

Those accustomed to Asterisk may expect the call to follow the dialplan by executing the 
applications as it parses them allowing data obtained from one action to influence the next action.
This not the case with the exception being the %{api func} {api arg} field type where an pluggable api call from
a module may be executed as the parsing occurs but this is meant to be used to draw realtime info such as
date and time or other quickly accessible information and shold *not* be abused.


The anatomy of an <extension> tag.

Legend: 
Text wrapped in [] indicates optional and is not part of the actual code.
a '|' inside [] indicates mutiple possible values and also is not part of the code.
Text wrapped in {} indicates it's a description of the parameter in place of the param itself.

<extension name="{exten_name}" [continue="[true|false]"]> 

continue=true means even if an extension executes to continue
parsing the next extension too

The {exten_name} above may anything but if it's 
an exact match with the destination number the parser will leap to this extension
to begin the searching that does not mean it will execute the extension.

Searching will either begin at the first extension in the context or at the point
the the parser has jumped to in the case described above.

Each condition is parsed in turn first taking the 'field' param.
The parser will apply the perl regular expression to each 'field' param encountered.

If the expression matches, it will parse each existing <action> tag in turn and add 
the data from the <application> tags to the channels todo list.	

If a matched expression contains any data wrapped in () the variables
$1,$2..$N will be valid and expanded in any of 'data' params from the subsequent action tags.

If the expression does NOT match, it will parse each <anti-action> tag in turn and add 
the data from the <application> tags to the channels todo list.
*NOTE* since there was no match the () feature is not availabe in anti-actions

The 'break' param indicates how to behave in relation to matching:
*) 'on-true'  - stop searching conditions after the first successful match.
*) 'on-false' - stop searching after the first unsuccessful match.
*) 'always'   - stop at this conditon regardless of a match or non-match.
*) 'never'    - continue searching regardless of a match or non-match.

<condition field="[{field name}|${variable name}|%{api func} {api arg}]" expression="{expression}" break="[on-true|on-false|always|never]">
  <action application="{app name}" data="{app arg}"/>
  <anti-action application="{app name}" data="{app arg}"/>
</condition>

  <!-- any number of condition tags may follow where the same rules apply -->
</extension>




git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2167 d0543943-73ff-0310-b7d9-9358b9ac24b2
      c4d890e0
    • Brian West's avatar
      $(HOME) instead of hard coded path. · 41c091e7
      由 Brian West 提交于 
      
git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2164 d0543943-73ff-0310-b7d9-9358b9ac24b2
      41c091e7