Search results

Jump to: navigation, search
  • In your regexroute.conf : [[Category:SIP]] [[Category:Regexroute]] [[Category:Routing]]
    2 KB (326 words) - 15:35, 31 October 2013
  • In regexroute.conf : [[Category:SIP]] [[Category:Regexroute]] [[Category:Routing]]
    980 B (147 words) - 15:36, 31 October 2013
  • In your regexroute.conf : [[Category:SIP]] [[Category:Routing]] [[Category:Regexroute]]
    1 KB (168 words) - 15:37, 31 October 2013
  • ====[[Regular expressions|Regexroute]] example==== Here is a regexroute.conf example:
    958 B (124 words) - 13:35, 31 October 2013
  • ...ascript|javascript global script]], external module, [[Regular expressions|regexroute]] etc.
    5 KB (739 words) - 15:42, 31 October 2013
  • * A simple conference can be executed via [[Regular_expressions|regexroute.conf]] like this
    6 KB (936 words) - 10:35, 4 November 2013
  • In the regexroute.conf file we put:
    6 KB (974 words) - 15:24, 31 October 2013
  • regexroute.conf
    10 KB (1,440 words) - 16:11, 31 October 2013
  • If you want to use RTP forward between the 2 endpoints you can setup in regexroute.conf something like: * [[Regular_expressions|regexroute.conf]]
    690 B (99 words) - 09:01, 4 November 2013
  • ...eways no matter the protocol used, other files are used as regfile.conf or regexroute.conf. From a [[Routing|routing module]] (e.g regexroute.conf) you can call an sip channel like this:
    4 KB (564 words) - 14:00, 13 May 2013
  • You can match incoming calls on a configured account in regexroute.conf preroute handler on the 'in_line' parameter and set the called number:
    3 KB (432 words) - 15:20, 31 October 2013
  • In regexroute.conf :
    2 KB (343 words) - 09:20, 4 November 2013
  • For [[regexroute.conf this route can be presented like this: ...ou cannot use variables ('${caller}', '${called}', '\1') such as you do it regexroute.conf in the return from SQL, instead you need to return the final routing d
    14 KB (2,155 words) - 10:47, 11 January 2014
  • In [[Regular expressions|regexroute.conf]]: * regexroute.conf: i.e. preroute=10 route=10
    1 KB (151 words) - 13:58, 31 October 2013
  • ...matter the protocol used, other files are used as '''regfile.conf''' or '''regexroute.conf'''.
    8 KB (1,261 words) - 08:43, 4 November 2013
  • The calls can be routed directly to a SIP channel from a routing module (e.g regexroute.conf). From a [[Routing|routing module]] (e.g regexroute.conf) you can call an sip channel like this:
    3 KB (422 words) - 08:08, 23 November 2017
  • A standard line for regexroute.conf will look like:
    18 KB (1,064 words) - 10:06, 4 November 2013
  • regexroute.conf:
    8 KB (1,151 words) - 12:20, 26 October 2017
  • ...he regexroute.conf.sample file in your chosen directory, under the name of regexroute.conf. This regulates the default routes to these tones.
    12 KB (2,088 words) - 15:15, 31 October 2013
  • ...umbers defined for testing purposes and you can find all of them in the '''regexroute.conf" file. When you call one of these, you'll get a standard telephony ton
    12 KB (1,986 words) - 15:13, 31 October 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers