Search results

: - view logs

Optionally the output can be colorized for either type of console but not for logs. To avoid cluttering the logs and terminal output with unimportant messages it is possible to only displa

Below are the modules and some tips you can use when writing call logs. You use this modules to obtain billing information. How to write call logs to a database

It is also important to provide '''-r''' so logs can be rotated without stopping Yate.

'''IMPORTANT''': The spandsp library logs '''only to file'''. You will not see any output in rmanager. Always copy th

You should instead examine the logs that will hold the reason the exec() has failed.

...l] of same yate.conf file. The default status is off as it would flood the logs and hit the performance.

The end reports displayed on screen and written to logs will look like:

== Event Logs== ..., appended and immediately closed. It should be safe to move or rename the logs during operation.

=== Prepare logs rotation=== ...rmally runs daily so make sure you collect signifficantly less than 2GB of logs in 24 hours.

...he configuration. It runs as a daily cron job. Yate doesn't rotate its own logs, but integrates into "logrotate" by providing a configuration file for it. ===Prepare logs rotation===

* Logs, preferably with the highest [[Debug Output|level of debugging]]. Please en * Ethereal packet captures or at least tcpdump logs (tcpdump -nn is usually enough) if you suspect network related problems.

... configuration file is register.conf. It also allows to write the cdr(call logs) in the database. ... must be enabled. They are used for routing the calls and writing the call logs in the database.

* by following the logs from the file * at runtime - use [[rmanager]] module that allows you to see logs in real time and control the logging level.

...itten [[#Writing call logs to a file|in a file]] or in the [[#Writing call logs to the database|database]]. Using this module makes it easier to follow the call logs, but it's only recommended for simple setups.

[[Eventlogs]] is a module that allows you to keep multiple logs when your Yate is daemonified, separated by specific criteria.

; Debug name as reported in Yate logs, default is derived from component name ::Show the current state of each route in the logs (and rmanager if debug is on).