-
Parameters that are needed for conference room are taken from [[call.execute]] and [[call.conference]] messages.<br>
* for [[call.execute]] the ''callto'' parameter must be of the form "conf/''NAME''" (default emp
6 KB (936 words) - 10:35, 4 November 2013
-
For each target a ''fork slave'' is created, that generates a ''[[call.execute]]'' message to create the outgoing call leg.
* The '''callto''' parameter of the call.execute message must be 'fork'.<br>
12 KB (1,844 words) - 11:24, 5 June 2014
-
* '''call.execute''' - so calls are forwarded to the server that can place them to the final
; call.execute: int: Priority of execute message handler (on source node)
3 KB (521 words) - 13:52, 31 October 2013
-
#H323chan sends a '''call.execute''' based on the returned value of the '''call.route'''
2 KB (383 words) - 16:07, 18 November 2013
-
...| 34 || ? || ? || ? || Could not connect to outgoing channel or network || call.execute
3 KB (380 words) - 09:25, 4 November 2013
-
====[[call.execute]]====
Later the same message becomes "[[call.execute]]" and is received by the call target module.
3 KB (449 words) - 09:20, 13 August 2013
-
...ge module sends [[call.route]] with target as called parameter and then '''call.execute''' with result of [[call.route]] message.
2 KB (314 words) - 13:18, 22 January 2013
-
...the call. Internally, the [[SIP_Configuration_File|Sip Channel]] sends a [[call.execute]] request to YATE requesting to be connected to a dumb/ channel.
* After processing the [[call.execute]], sip/1's Data Source is connected to dumb/1's Data Consumer and sip/1's D
2 KB (400 words) - 10:10, 4 November 2013
-
; 1. If a language is specified in the call.execute or chan.attach message,
18 KB (1,064 words) - 10:06, 4 November 2013
-
message="call.execute";
2 KB (248 words) - 08:26, 14 February 2014
-
*[[call.execute]]
916 B (142 words) - 10:38, 21 January 2013
-
* [[call.execute]] make an outgoing call
17 KB (2,660 words) - 08:04, 21 June 2018
-
:The 'call.execute' message must have a '''trunkout'''=true parameter
16 KB (2,483 words) - 09:12, 4 November 2013
-
To create an outgoing fax call send a '''call.execute''' message with:
6 KB (1,040 words) - 10:09, 4 November 2013
-
The matching [[call.execute]], [[chan.attach]] and [[chan.record]] messages are modified just before be
For [[call.execute]] (when routing directly to the module) the relevant parameter is '''callto
3 KB (409 words) - 10:10, 4 November 2013
-
...ber is dialed an instance of the voicemail.php script is launched and the "call.execute" message is passed to it (even if it didn't install a handler) so it can pi
2 KB (408 words) - 15:09, 31 October 2013
-
...e routing decision in Yate's message flow. Routing is possible in the '''[[call.execute]]''' message, setting a module for the outbound call leg.
The module works by intercepting specific [[call.execute]] messages (based on the callto parameter) and redispatching the message as
2 KB (356 words) - 07:22, 23 May 2014
-
For outgoing calls you should use the '''copyparams''' parameter of the [[call.execute]] message to copy parameters from incoming call leg to the outgoing one.
10 KB (1,558 words) - 13:22, 13 January 2014
-
The data must be specified in the 'source' parameter of [[call.execute]].
* [[call.execute]] used to park the call
1 KB (174 words) - 11:06, 4 November 2013
-
===[[call.execute]]===
Set the 'callto' parameter of a [[call.execute]] message to something like:
1 KB (145 words) - 11:08, 4 November 2013
-
%%>message:0xb59f6f11.327305252:1326117799:call.execute::callto=dumb/:target=person1
%%<message:0xb59f6f11.327305252:true:call.execute::callto=dumb/:target=person1:id='''dumb/47''':peerid='''sip/134''':targetid
1 KB (204 words) - 10:26, 21 January 2013
-
; call.execute: int: Priority of call.execute handler
;call.execute=
4 KB (575 words) - 11:09, 4 November 2013
-
; priority: int: Priority of the call.execute handler
3 KB (459 words) - 11:15, 4 November 2013
-
sniffer on filter call.execute
17 KB (1,082 words) - 13:07, 18 August 2022
-
... message or directly divert the call to another target by masquerading a [[call.execute]] to a specified target.
2 KB (387 words) - 11:22, 4 November 2013
-
...sferred to another channel (which can be another IVR) by masquerading a "[[call.execute]]" message. As soon as the caller is connected to the transfer target chann
3 KB (471 words) - 18:55, 10 March 2014
-
execute = yate.onwatch("call.execute",
2 KB (223 words) - 11:54, 4 November 2013
-
execute = yield yate.onwatch("call.execute",
2 KB (207 words) - 11:58, 4 November 2013
-
execute = self.client.msg("call.execute",
execute = self.client.msg("call.execute",
8 KB (666 words) - 12:04, 4 November 2013
-
{"message": "call.execute",
execute = self.client.msg("call.execute",
9 KB (821 words) - 12:17, 4 November 2013
-
; call.execute: int: Priority of the call.execute message handler
;call.execute=20
1 KB (173 words) - 11:27, 4 November 2013
-
* [[call.execute]]
3 KB (329 words) - 08:19, 25 May 2018
-
...all target is known, the incoming channel attaches its CallEndPoint to a [[call.execute]] message(4). On receiving this message, the destination channel connects i
1 KB (189 words) - 21:07, 10 March 2014
-
The parameters that are needed for conference room are taken from [[call.execute]] and [[call.conference]] messages.
$m->params["message"] = "call.execute";
3 KB (468 words) - 09:42, 20 May 2013
-
call.execute 80 onExecute roaming:80 module ybts
3 KB (387 words) - 09:46, 21 August 2017
-
...l object support a second parameter: object with parameters to be added to call.execute message
m.message = "call.execute";
5 KB (575 words) - 16:05, 27 February 2014
-
*[http://docs.yate.ro/wiki/Call.execute call.execute] make an outgoing ISUP/ISDN call
36 KB (5,180 words) - 12:18, 26 October 2017
