Search results

Jump to: navigation, search
  • ... the system you will have to use another module like [[Regular_expressions|regexroute]]. * [[Regular_expressions| Regexroute module]]
    656 B (90 words) - 13:57, 31 October 2013
  • Regular expression Route Module(regexroute) provides a simple way of routing telephony calls inside Yate.<br> This mod There are two messages handled by default by the regexroute module:
    20 KB (3,110 words) - 10:27, 4 November 2013
  • The regexroute module offers a ''transcode'' function to build an extended list. You shoul You can put this line in regexroute.conf section [contexts] that handles call.preroute:
    2 KB (301 words) - 11:06, 3 April 2013
  • 1. To use as a fallback routing module you should add in regexroute or your routing module something like: 3. Implementation in regexroute.conf:
    12 KB (1,844 words) - 11:24, 5 June 2014
  • '''Note''': If you also use regexroute.conf for routing, you have to set priority of route. By default they both h ...t the access to make calls only to autenticated users you have to setup in regexroute.conf in section [default] this line:
    4 KB (539 words) - 13:59, 31 October 2013
  • ...|callfork]] module with the ''rotate'' function from [[Regular expressions|regexroute]] it is possible to implement round-robin routing, with or without fallback We set in regexroute.conf an entry like this:
    3 KB (380 words) - 14:01, 31 October 2013
  • ... accfile, you have to use a [[routing]] module, like [[Regular expressions|regexroute]] or make the routing from an external script using the [[External Module|e ====How to route calls from regexroute through the line====
    8 KB (1,225 words) - 10:07, 6 July 2018
  • ; endpoint to the local gatekeeper, you must make a route in regexroute (or In regexroute.conf:
    13 KB (1,916 words) - 09:08, 4 November 2013
  • [[Regular_expressions|regexroute]]
    773 B (112 words) - 10:46, 21 January 2013
  • * [[Regular expressions|regexroute]]
    12 KB (1,662 words) - 13:25, 1 October 2019
  • In the example above the construction '''$($){data}''' is specific to regexroute. The raw string required is '''${data}'''
    3 KB (409 words) - 10:10, 4 November 2013
  • In Yate the IVR functionality is not related to routing, therefore regexroute - or any other routing module - will not help writing an IVR. In Yate an IV
    2 KB (408 words) - 15:09, 31 October 2013
  • regexroute.conf holds: Again, ''regexroute.conf'' will contain:
    3 KB (419 words) - 14:03, 31 October 2013
  • param['handlers'] = 'javascript:15,regexroute:100' ...pt:15,regexroute:100,javascript:15,cdrbuild:50,iax:100,h323:100,jingle:100,regexroute:100,sip:100,regfile:100,analog:100,sig:100'
    17 KB (1,082 words) - 13:07, 18 August 2022
  • ...ndling of the message is custom and can be done from [[Regular_expressions|regexroute]]/[[External_Module|external module]]/custom yate module. ...u can see a test setup where the handling is done in [[Regular expressions|regexroute]].
    5 KB (843 words) - 18:34, 13 March 2014
  • If the routing it is done from regexroute.conf. Route all calls through sip and set copyparams parameters with your p * [[Regular_expressions|Regexroute module]]
    3 KB (495 words) - 14:44, 31 October 2013
  • In [[Regular_expressions|regexroute.conf]] file: [[Category:Routing]] [[Category:Cluster]] [[Category:regexroute]]
    1 KB (191 words) - 14:02, 31 October 2013
  • which you can place in regexroute.conf ...at to assign unique numbers to my customers (Their fixed line numbers). If regexroute.conf has the highest actual priority, these customers always will be routed
    6 KB (833 words) - 15:07, 31 October 2013
  • ...rules. Basic rules (for few users) could be added in [[Regular expressions|regexroute]] but most of the time this won't be enough. The rules are usually stored i
    4 KB (715 words) - 15:20, 31 October 2013
  • ccongestion queuesnotify* regexroute wavefile rmanager extmodule
    9 KB (1,268 words) - 15:48, 31 October 2013

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

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers