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
  • regexroute.conf
    3 KB (556 words) - 07:52, 31 May 2013
  • For example, in regexroute.conf you can have:
    16 KB (2,483 words) - 09:12, 4 November 2013
  • In regexroute.conf you can set this to transmit a fax: ====regexroute.conf====
    6 KB (1,040 words) - 10:09, 4 November 2013
  • * [[Example of forking a call using lateroute]] - using lateroute from regexroute.conf
    2 KB (356 words) - 07:22, 23 May 2014
  • In routing modules like regexroute.conf:
    1 KB (174 words) - 11:06, 4 November 2013
  • ...emote echo device is another Yate server it can have the following line in regexroute.conf: If the remote runs another Yate analyzer use in regexroute.conf:
    2 KB (376 words) - 07:16, 23 May 2014
  • ...ication requirement for all inbound calls add in the [[Regular expressions|regexroute.conf]] file: ...er registered users, PSTN, gateways you need to edit [[Regular expressions|regexroute.conf]]. <br>
    5 KB (888 words) - 13:05, 10 March 2015
  • ...ication requirement for all inbound calls add in the [[Regular expressions|regexroute.conf]] file: ...er registered users, PSTN, gateways you need to edit [[Regular expressions|regexroute.conf]]. <br>
    6 KB (967 words) - 14:56, 8 January 2014
  • A simple conference can be executed via regexroute.conf. Choose a number that will join people in a conference:
    3 KB (468 words) - 09:42, 20 May 2013
  • In regexroute.conf, the line setting it from callername would look like: ...est header from an incoming to an outbound call you should do like this in regexroute.conf:
    2 KB (262 words) - 14:43, 31 October 2013
  • In regexroute.conf :
    988 B (152 words) - 15:40, 31 October 2013
  • regexroute.conf example: regexroute.conf example:
    3 KB (462 words) - 07:54, 21 October 2013
  • Example routing in regexroute.conf:
    724 B (91 words) - 08:34, 4 November 2013
  • '''regexroute.conf''' '''regexroute.conf'''
    5 KB (643 words) - 12:23, 26 October 2017
  • Here is a basic example in regexroute.conf:
    2 KB (268 words) - 09:22, 27 October 2017
  • Example in regexroute.conf:
    3 KB (434 words) - 14:13, 26 October 2017
  • * '''regexroute.yate''' – located in modules. ''' 5.regexroute.conf''' - you specify what rules are applied to calls. Mainly:
    8 KB (1,258 words) - 15:25, 31 October 2013

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

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers