hi, we encounter some small problems withing the past 2 days and we are trying to find out more about the problems. for this we downloaded the debug logfiles written by fs, but we do not manage to filter all log-entries for one single special call. we are using socket outbound and would like to see all entries (inbound/outbound) of one call. is this possible? kind regards dennis
On Mon, May 25, 2009 at 8:19 AM, Dennis <odermann@googlemail.com> wrote:
hi,
we encounter some small problems withing the past 2 days and we are trying to find out more about the problems. for this we downloaded the debug logfiles written by fs, but we do not manage to filter all log-entries for one single special call.
we are using socket outbound and would like to see all entries (inbound/outbound) of one call.
is this possible?
kind regards dennis
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: grep -n b1f9e5ce-29a6-497a-a628-71f1bdefa0cb freeswitch.log <output snipped> In this case I found out my channel name is "portaudio/ sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org>" so I grep for it: grep "portaudio/sip:888@conference.freeswitch.org<sip%3A888@conference.freeswitch.org>" freeswitch.log <output snipped> It's not perfect but it helps narrow down your call. -MC
participants (2)
-
Dennis
-
Michael Collins