Debugging and, or Investigation of messages

From Yate Documentation
Revision as of 15:45, 11 April 2013 by Dana (Talk | contribs)

Jump to: navigation, search

The module msgsniff is for you to probe all the messages being generated and, or received by Yate and, or the modules compiled and enabled in yate.conf file.

This is a module you will use rather rarely, obviously it should be off by default.

The loading of msgsniff.yate is controlled by yate.conf like any other module.

The initial activation is controlled by msgsniff in [general] of same yate.conf file. The default status is off as it would flood the logs and hit the performance.

Contents

Enable msgsniff in configuration

The sniffer will dump the Yate messages to output or log file.

All Yate's messages will be seen and their parameters.

  • It can be enabled in yate.conf:
[general]
msgsniff=yes
modload=no
;Don't forget to load the sniffer module if modload parameter value is 'no'.

[modules]
;for debugging yate
rmanager.yate=yes
msgsniff.yate=yes

After enable the sniffer, start Yate with logging:

./run -vvvvv -l yate.log

Enable / Disable sniffer in telnet

The module must be loaded so that you can use this commands from telnet:

telnet 0 5038
sniffer on

and disabled with:

sniffer off

Apply filter messages with sniffer

  • Apply filter by specifying regex to match in telnet:
sniffer filter ^\(chan\.\|engine\.halt$\)
  • or in yate.conf:
[default]
; filtersniff: regexp: Default filter to apply to message sniffer at initialization
; If empty it will match all messages except engine.timer which is never displayed
; Example for a filter matching all chan.Anything messages and engine.halt:
filtersniff=^\(chan\.\|engine\.halt$\)

Example

  • Sniffer output example:


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers