Right now the best item for this is to enable the uuid stamp on all debug lines in the freeswitch.log file. In conf/autoload_configs/logfile.conf.xml enable this: <!-- <param name="uuid" value="true" /> --> restart fs or reload mod_logfile and from that point on each log line will have the associated uuid if there is one. As for your other idea, right now there isn't anything like that and it would probably take a fair amount of time and energy to come up with something like that. It would be great to have that ability, however it is not a simple endeavor. -MC On Wed, Oct 13, 2010 at 1:58 PM, Bernhard Suttner <bernhard.suttner@winet.ch

wrote:

Hi,

is there a idea how to improve the freeswitch debugging possiblities if freeswitch does run on a high used system - maybe also clustered? I think this is maybe still a problem if the system is under high load and how have to get debug informations because e.g. the call from user 7777 is always not successful.

Like a api command (debug_all_from sip-user 7777) which will then write kind of debug stuff from and to this user (log messages, sip debug messages, ...) to a special syslog server, log file, ...)

Any other idea how to improve that or is there already a nice way to get that?

Best regards, Bernhard

_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org