Search results
Page title matches
- Queues notify module has three sections: * ''events'' - this section configures the status set in resource.notify messages when a queued call status changes;2 KB (269 words) - 11:20, 4 November 2013
Page text matches
- ...es-title">[[Modules#Resource_subscribe.2Fnotify_modules|Resource Subscribe/Notify Modules]]</font></div>8 KB (1,086 words) - 09:08, 31 July 2018
- * ''notify'' (default empty) enables generating notification messages for conference e * ''interval'' - time interval for receiving chan.notify with event ''speaking''. Default value is 3 sec.6 KB (936 words) - 10:35, 4 November 2013
- * NOTIFY - Notify SIP clients when an event's state changed4 KB (564 words) - 14:00, 13 May 2013
- SIP features module that implements SUBSCRIBE and NOTIFY Methods. SIP features module that implements SUBSCRIBE and NOTIFY methods.8 KB (1,083 words) - 11:49, 27 October 2017
- ...:<id>:<time>:chan.attach::consumer=wave/record//sounds/test.al:notify=myid42:single=true:id=myid42 ...lt;id>:<time>:chan.attach::recordstop=true:consumer=wave/record/-:notify=myid42:single=true:id=myid423 KB (444 words) - 13:31, 15 April 2014
- '''notify''' :::the id of the target that should recieve the chan.notify message that is send when the source or consumer reach end of data2 KB (246 words) - 16:02, 18 January 2013
- Message sent to request or notify changes in parameters of channels having active calls. This message is usua2 KB (245 words) - 10:47, 21 January 2013
- :::Mandatory - The name of the SIP method to use in the request (e.g. NOTIFY)2 KB (274 words) - 09:02, 4 November 2013
- ; A T1 line can detect link failures and notify the upper layer17 KB (2,660 words) - 08:04, 21 June 2018
- * SIP Methods like SUBSCRIBE and NOTIFY are required. * NOTIFY - Notify SIP clients when an event's state changed3 KB (456 words) - 09:16, 9 April 2015
- '''resource.notify''' is a message sent by a module to notify a resource event state change or a subscription termination ;notifyto2 KB (219 words) - 15:22, 21 January 2013
- : Notify the client and the remote peer on transaction state change. ...id request from as remote peer to create a new transaction, creates it and notify the client, unless the new transaction is an internally processed one (such3 KB (399 words) - 11:45, 4 November 2013
- ==Resource subscribe/notify modules== Handle sip.subscribe and resource.notify messages12 KB (1,662 words) - 13:25, 1 October 2019
- ...<id>:<time>:chan.attach::consumer=dbwave/record/arbitrary.alaw:notify=myid42:single=true:consumer_account=dbaccount:consumer_query=INSERT INTO ta3 KB (409 words) - 10:10, 4 November 2013
- ; notify: string: Target ID for notification messages about queue activity ; detail: bool: Notify when details change, including call position in queue4 KB (575 words) - 11:09, 4 November 2013
- Queues notify module has three sections: * ''events'' - this section configures the status set in resource.notify messages when a queued call status changes;2 KB (269 words) - 11:20, 4 November 2013
- ....wikipedia.org/wiki/DNIS DNIS] is detected the module masquerades a [[chan.notify]] as the channel to which it is attached. ;notify2 KB (387 words) - 11:22, 4 November 2013
- The '''chan.notify''' message is sent back to a channel driver when a specific event has occur :::unique identifier originally provided as the "notify" parameter to the chan.attach message. Is not necessary the same thing as t434 B (65 words) - 16:17, 18 January 2013
- ...[Subscriptions|subscriptions.conf]] the actual logic for sending subscribe/notify.25 KB (3,811 words) - 10:09, 6 July 2018
- notify = yate.msg("chan.notify", {"targetid": notify}) notify = yate.msg("chan.notify", {"targetid": notify})5 KB (788 words) - 11:53, 4 November 2013
- "notify": peerid, yield self.client.onmsg("chan.notify",9 KB (821 words) - 12:17, 4 November 2013
- * NOTIFY - Notifies all subscribers of an event. This happens when Yate sends NOTIFY requests to the users that subscribed to a certain event. Or you can follow8 KB (1,099 words) - 18:29, 13 March 2014
- ...gy independence. Each module that needs something from another or tries to notify about some event creates and emits a message. The message flows through the2 KB (324 words) - 11:32, 13 November 2015
- * [[chan.notify]] * [[user.notify]]3 KB (329 words) - 08:19, 25 May 2018
- '''chan.replaced''' is used to notify other modules when the topology of a chain of circuits has changed. Current2 KB (180 words) - 10:31, 21 January 2013
- : The operation to fulfill or notify. : The number of contacts in the list. This parameter must be set when notifying update/delete from server.2 KB (239 words) - 13:37, 15 November 2012
- '''monitor.notify''' message is emitted by the monitoring module to announce the values for c ...e index. For the number specified by count, there will be that number of ''notify.i - value.i'' pairs of message parameters which specify a notification and1 KB (228 words) - 11:01, 23 January 2013
- :::The operation to fulfill or notify. JabberServer Module will process message user.update with notify: 'delete' and will close the stream after user deletion.<br>1,015 B (147 words) - 15:37, 18 January 2013
- :::keyword indication the operation. The operation is NOTIFY574 B (72 words) - 15:04, 21 January 2013
- I will notify the user when his/her subscriber status3 KB (469 words) - 08:59, 13 February 2013
- $m->params["notify"] = "conf-monitor/cs-$conference_id"; In parameter 'notify' will be set the id of the conference which will set the record that will r3 KB (468 words) - 09:42, 20 May 2013
- ...ding message to all connected clients except the newly inactivated one, to notify them that if they desire to activate a Routing Context now will be a great11 KB (1,842 words) - 09:53, 27 October 2017
- ; The network will notify the router about its destination(s) and priority ; The network will notify the router about its destination(s) and priority7 KB (1,115 words) - 10:47, 27 October 2017
- mgcp sgcp disconnect notify mgcp sgcp restart notify6 KB (921 words) - 11:10, 26 October 2017
- .... If the localmaintchanged flag is specified the ISUP call controller will notify the remote party. The flag will be reset when the circuit (un)blocking mess ; The call controller will notify the other side of the link of idle channels36 KB (5,180 words) - 12:18, 26 October 2017
- * '''notify''': Target id for notification. Ignored for synchronous requests ...essage).<br>This parameter is ignored for synchronous requests or empty '''notify'''.<br>This parameter may be used by modules using full asynchronous sendin15 KB (2,067 words) - 13:35, 9 November 2020
- ;notifyto : The URI used as destination when notifying * [[resource.notify]]906 B (122 words) - 09:28, 18 January 2013
- * '''notifymsg''': string: Name of the notification message sent on timeout. : Usually it should be [[chan.notify]] or [[call.drop]], empty disables the message.6 KB (870 words) - 14:12, 10 January 2014
- ; oscillate_interval : int: Time in milliseconds that stop this module from notifying about CPU load,3 KB (424 words) - 12:54, 18 July 2016
- :*accounts: bool: Activate client registrations on "user.notify" and "engine.timer". Defaults to no :*statusquery update account status after receiving an user.notify.14 KB (2,155 words) - 10:47, 11 January 2014