Search results

Jump to: navigation, search
  • "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 follow
    8 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 the
    2 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. Current
    2 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 and
    1 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 NOTIFY
    574 B (72 words) - 15:04, 21 January 2013
  • I will notify the user when his/her subscriber status
    3 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 r
    3 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 great
    11 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 priority
    7 KB (1,115 words) - 10:47, 27 October 2017
  • mgcp sgcp disconnect notify mgcp sgcp restart notify
    6 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 channels
    36 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 sendin
    15 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

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

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers