Search results
Page title matches
- #H323chan sends a '''call.route''' and waits for a returned value #H323chan sends a '''call.execute''' based on the returned value of the '''call.route'''2 KB (383 words) - 16:07, 18 November 2013
Page text matches
- ...dule or script that handles: user.auth, user.register, user.unregister and call.route messages3 KB (452 words) - 12:06, 11 April 2013
- ...e routing modules. A routing module is a module that handles (sees) the [[call.route]] message.3 KB (433 words) - 09:01, 10 March 2016
- * the '''call.route''' message that tries to map a called number to a string describing the tar This is a list of usual parameters found in the [[call.route|call.route]] message. Arbitrary parameters can be added by any module.20 KB (3,110 words) - 10:27, 4 November 2013
- :*call.route: bool: Activate handler on the "call.route" message. Defaults to no ==== Section [call.route]====14 KB (2,155 words) - 10:47, 11 January 2014
- This is impossible using the ''call.route'' message but there is the option of altering the parameters of the ''call.12 KB (1,844 words) - 11:24, 5 June 2014
- ; route setups the call.route handler priority ...al routing modules then you have to pay attention to the priorities of the call.route message handler for each module.4 KB (539 words) - 13:59, 31 October 2013
- * '''call.route''' - to detect internal calls within the cluster ; call.route: int: Priority of route message handler (on target node)3 KB (521 words) - 13:52, 31 October 2013
- #H323chan sends a '''call.route''' and waits for a returned value #H323chan sends a '''call.execute''' based on the returned value of the '''call.route'''2 KB (383 words) - 16:07, 18 November 2013
- The parameters in the [[call.route]] message are set in the '''message''' variable.3 KB (425 words) - 10:03, 22 March 2015
- ====[[call.route]]==== The incoming call module must set the following in the "[[call.route]]" message:3 KB (449 words) - 09:20, 13 August 2013
- ...th target as called parameter and then '''call.execute''' with result of [[call.route]] message.2 KB (314 words) - 13:18, 22 January 2013
- * Tell YATE that this script is interested in call.route messages * Wait for [[call.route]] messages to come in from YATE2 KB (400 words) - 10:10, 4 November 2013
- * [[call.route]]719 B (108 words) - 10:42, 21 January 2013
- ...tor endpoints will set the type, format and callsource parameters of the [[call.route]] message. The 'type' parameter will have the value 'record', the 'format'17 KB (2,660 words) - 08:04, 21 June 2018
- ;Activate handler on the "call.route" message call.route=yes3 KB (472 words) - 09:00, 4 November 2013
- ...essages (based on the callto parameter) and redispatching the message as [[call.route]]. If the routing succeeds the callto parameter is replaced with the result2 KB (356 words) - 07:22, 23 May 2014
- ====call.route==== In the call.route message:2 KB (302 words) - 11:11, 4 November 2013
- ...here are 3 incoming calls with context=abc and 2 with context=xyz in a new call.route with context=abc it will set:<br> ...'' in [general] section in callcounters.conf then no matter the context in call.route it will set:<br>747 B (101 words) - 14:03, 31 October 2013
- The LNP query is performed on the [[call.route]] message. ; call.route: int: Priority of the call.route handler5 KB (700 words) - 10:31, 4 November 2013
- To mantain the LNP cache the module implements two [[call.route]] message handlers.<br> ...he called number in cache. If the item is found copy its parameters in the call.route message, set '''querylnp=false''' and '''npdi=true''' parameters. If the it12 KB (1,922 words) - 10:32, 4 November 2013