Search results

Jump to: navigation, search
  • This is a special module that allows intercepting and mangling ISUP messages that pass through the STP. ; defaultpointcode: string: DPC of the ISUP messages to match
    2 KB (359 words) - 13:06, 26 October 2017
  • The module works by intercepting specific [[call.execute]] messages (based on the callto parameter) and redispatching the message as [[call.rou
    2 KB (356 words) - 07:22, 23 May 2014
  • ...decisions.<br> The context parameter must be generated in the [[call.cdr]] messages by the [[CDR Build Module|cdrbuild]] module. ; This parameter must exist in the call.cdr messages by adding a line
    2 KB (302 words) - 11:11, 4 November 2013
  • Cdrbuild module reads messages from other channel modules ([[H323_channel_module|h323chan]], [[SIP_Configu * '''status''': bool: Emit [[call.cdr]] status messages for the call duration. The default value is:
    10 KB (1,558 words) - 13:22, 13 January 2014
  • ; flags: int: Miscellaneous flags for the SIP messages ; flags: int: Miscellaneous flags for the SIP messages
    5 KB (700 words) - 10:31, 4 November 2013
  • ...param: string: Template used to build a cache entry id value when handling messages ; parameter value of handled messages)
    12 KB (1,922 words) - 10:32, 4 November 2013
  • ; notify: string: Target ID for notification messages about queue activity
    4 KB (575 words) - 11:09, 4 November 2013
  • ; waitflush: int: Milliseconds to wait at script shutdown after waiting messages
    3 KB (459 words) - 11:15, 4 November 2013
  • The module '''msgsniff''' is for you to probe all the messages being generated and, or received by Yate. The sniffer will dump the Yate messages to output or log file.
    17 KB (1,082 words) - 13:07, 18 August 2022
  • ...rator can be controlled from the rmanager as it processes "engine.command" messages or from Yate's command line. Callgen messages can be generated from Yate's command line like this:
    3 KB (388 words) - 11:12, 4 November 2013
  • * ''events'' - this section configures the status set in resource.notify messages when a queued call status changes; ; This section configures the status set in resource.notify messages when
    2 KB (269 words) - 11:20, 4 November 2013
  • ...ttaches data consumers by handling the [[chan.attach]] and [[chan.record]] messages.
    2 KB (387 words) - 11:22, 4 November 2013
  • ;rmanager control return status messages:
    1 KB (211 words) - 15:33, 8 February 2013
  • ; port on which the module listens for SNMP messages. Defaults to 161.
    11 KB (1,779 words) - 11:28, 4 November 2013
  • ; role: string: Role to be set in messages sent by connections using this listener ; for INVITE/REGISTER/SUBSCRIBE/OPTIONS messages if the flood protection is on.
    25 KB (3,811 words) - 10:09, 6 July 2018
  • ...ll: you can call your own Google Voice number and say check your voicemail messages.
    8 KB (1,258 words) - 15:25, 31 October 2013
  • ... is an application that can be used for playing prompts to users, register messages or configure other functionalities for the users. ...caller and giving commands to Yate - all these by handling or generating [[Messages]].
    3 KB (471 words) - 18:55, 10 March 2014
  • Messages are one of the main parts of Yate's architecture. We use them for the commu Messages can be dispatched or enqueued. Dispatching a message is done synchronously
    8 KB (1,217 words) - 20:38, 10 March 2014
  • ... this library is to help you write your own scripts to handle events, send messages or set message handlers in Yate using [[External Module|external module]]. * Sending messages
    1 KB (168 words) - 07:23, 23 May 2014
  • YAYPM allows to create deferreds for specified YATE messages. ===Waiting for messages===
    5 KB (788 words) - 11:53, 4 November 2013

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

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers