Debugging and, or Investigation of messages

Revision as of 12:03, 10 April 2013

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.

Enable msgsniff in configuration

The sniffer will dump the Yate messages to output or log depending:

• It can be enabled in yate.conf:

[general]
msgsniff=yes

After enable the sniffer, start Yate with logging:

./run -vvvvv -l yate.log 

If there is no message in the console when you are making a call then the sniffer module is not loaded. Check if msgsniff.yate module is present in modules directory.

Enable sniffer in telnet console

sniffer on

and disabled with:

sniffer off

Example

• Enable msgsniff module from Yate's main configuration file:

yate.conf

[general]
modload=no

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

• The sniffer can be turned on and off from rmanager using the commands:

sniffer on
sniffer off

• Apply filter by specifying regex to match:

sniffer filter ^\(chan\.\|engine\.halt$\)

See also

• Modules
• Configuration Files
• Debug Output