Search results

Jump to: navigation, search

Page title matches

  • 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.
    16 KB (1,017 words) - 16:12, 15 December 2017
  • 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
  • Below you will find a list with all standards messages in Yate. ...This allows us to have a bigger flexibility than functions, mainly because messages in Yate can have an arbitrary number of parameters.
    3 KB (329 words) - 08:19, 25 May 2018
  • ...ule (the same goes for external scripts) you can have access to all Yate's messages. |class="yate-header-right"|YATE's Messages in JavaScript
    776 B (108 words) - 11:54, 1 November 2013
  • To have access to specific messages from Javascript you have to install a handler.
    763 B (112 words) - 11:10, 27 February 2014
  • ===How to convert SIP headers into SIP parameters and in what messages=== On incoming messages the SIP headers are added in Yate messages as '''sip_headername''' where headername is the lowercase version of the re
    2 KB (262 words) - 14:43, 31 October 2013
  • You can now enable chat messages between SIP clients or build custom applications based on SIP MESSAGE much ... configurations if you already allowed SIP calls in Yate, besides enabling messages in ysipchan.conf as seen in the configuration above.
    5 KB (739 words) - 15:42, 31 October 2013

Page text matches

  • Also, it can be overridden when sending DTMFs (chan.dtmf messages) by a '''methods''' parameter. It can be overridden in [[chan.dtmf]] messages by a parameter with the same name.
    3 KB (493 words) - 08:59, 4 November 2013
  • ...or conference room are taken from [[call.execute]] and [[call.conference]] messages.<br> * ''billing'' (default false) emits messages needed to bill conference participants
    6 KB (936 words) - 10:35, 4 November 2013
  • ...onstruct the message. But in voice and video calls this is very important. Messages have to come in the same order or at least the section that handles the rec
    9 KB (1,569 words) - 13:20, 20 March 2013
  • ...concerned with call signaling is used to complete the info carried by Q931 messages which is missing certain important things for a H323 transmission like the
    4 KB (562 words) - 15:04, 19 November 2012
  • ...real time multimedia session in numerous formats like voice, video or text messages.
    4 KB (564 words) - 14:00, 13 May 2013
  • ...ipt that handles: user.auth, user.register, user.unregister and call.route messages
    3 KB (452 words) - 12:06, 11 April 2013
  • ... basic routing functionality, this module allows custom handling for other messages and using global variables. ==Messages handled==
    20 KB (3,110 words) - 10:27, 4 November 2013
  • ...achine on" command. In this mode answers are machine parsable and also the messages are dumped just after being dispatched. The message text format is the same * [[Debugging and, or Investigation of messages]]
    7 KB (1,041 words) - 13:24, 4 June 2014
  • Note that the most important debugging messages have numerically lower levels. ...d terminal output with unimportant messages it is possible to only display messages with a level numerically lower (that is, more important) than a specific li
    6 KB (819 words) - 15:55, 31 October 2013
  • :The following parameters enable handling of individual messages. Each must be enabled manually in this config file: ...ing handlers on the "chan.disconnected", "call.answered" and "chan.hangup" messages. Defaults to no
    14 KB (2,155 words) - 10:47, 11 January 2014
  • == Defining messages priorities== In [general] section you can set the priority of the various messages handled by regfile and define file where registration information can be sa
    4 KB (539 words) - 13:59, 31 October 2013
  • The module works by selectively altering resource names in Yate's messages. Relevant parameters are prefixed with the node name of the server that sho ===Messages===
    3 KB (521 words) - 13:52, 31 October 2013
  • * [[How to convert SIP headers into SIP parameters names in messages]] * [[Using SIP MESSAGE or how to enable chat messages in SIP]]
    9 KB (1,376 words) - 10:01, 27 October 2017
  • Messages are intercepted by pbxassist at a high priority (default 15) and the state ...ation" message is enqueued. The module provides default handling for these messages by executing the requested operation.
    5 KB (832 words) - 11:08, 4 November 2013
  • There are no cause codes in IAX, only textual messages sent with the REJECT or HANGUP packet.
    3 KB (380 words) - 09:25, 4 November 2013
  • This page describes the flow of messages that deal with RTP forwarding and how to enable SDP forwarding.
    3 KB (449 words) - 09:20, 13 August 2013
  • * localaddress: Local address to set in sent messages
    8 KB (1,225 words) - 10:07, 6 July 2018
  • ... us to have a bigger flexibility than with plain functions, mainly because messages in Yate can have an arbitrary number of parameters, and can be sent to more
    811 B (119 words) - 13:48, 13 February 2013
  • ; imtochantext: boolean: Send received IM messages as chan.text if a channel is found ; chat: Send tones as chat messages
    9 KB (1,391 words) - 09:14, 4 November 2013
  • The flow for this messages is similar to the HTTP request/response transaction model. ... a user agent client (UAC) and a user agent server(UAS), and comprises all messages from the initial request to the final response.
    8 KB (1,261 words) - 08:43, 4 November 2013

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

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers