<br><br><div class="gmail_quote">On Mon, May 25, 2009 at 8:19 AM, Dennis <span dir="ltr"><<a href="mailto:odermann@googlemail.com" target="_blank">odermann@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi,<br>
<br>
we encounter some small problems withing the past 2 days and we are<br>
trying to find out more about the problems. for this we downloaded the<br>
debug logfiles written by fs, but we do not manage to filter all<br>
log-entries for one single special call.<br>
<br>
we are using socket outbound and would like to see all entries<br>
(inbound/outbound) of one call.<br>
<br>
is this possible?<br>
<br>
kind regards<br>
dennis<br>
</blockquote></div><br>This isn't the easiest thing to do but it is possible. In the past I've used a combination of uuid and channel name with grep. Also, I recommend rotating log files using "fsctl send_sighup" which helps keep you from getting a 10GB freeswitch.log file. :) The first thing I do is find the call's uuid, either by manually searching through the log file or by using a CDR. (Use whichever works best for you.) Then use grep to find all the line numbers for that particular uuid. Here's a sample from my Mac where I used portaudio to call the main conference line:<br>
<br>grep -n b1f9e5ce-29a6-497a-a628-71f1bdefa0cb freeswitch.log<br><br><output snipped><br><br>In this case I found out my channel name is "portaudio/<a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a>" so I grep for it:<br>
<br>grep "portaudio/<a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a>" freeswitch.log<br><br><output snipped><br><br>It's not perfect but it helps narrow down your call.<br>
<br>-MC<br><br><br><br><br>