On Wed, Aug 31, 2011 at 11:18 AM, Robert Kulagowski <rkulagow@xxxxxxxxx> wrote: > On Wed, Aug 31, 2011 at 10:17 AM, Jan Willamowius <jan@xxxxxxxxxxxxxx> wrote: >> Hi Robert, >> >> all messages for a call have the same callID and you can grep for >> that. Its a bit complicated by the fact that the messages are printed >> out over multiple lines, so its a job for a small Perl script or >> similar. If you want to take it a step further you can do 2 passes, one >> to find all calls for a specific endpoint ID and then collect all >> messages for those calls in the 2nd pass. >> >> Doing that server side would be a major hassle and imagine how >> inconvenient all those trace files would be if you have hundreds of >> calls at the same time. Jan, have you given any thought to adding a "per-host" option for logging in a future version of GnuGk? I know that it may not be useful with 100's of hosts/simultaneous calls, but in my environment, with 100 endpoints and 11 to 12 simultaneous calls that often last longer than 60 minutes, it would be immensely useful during troubleshooting to be able to maintain a consistent mental "thread" as debugging is occurring. Even just being able to specify at the status port that a certain endpoint needs to be logged to a special file would be great. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
