> On Fri, 2009-05-29 at 11:54 -0700, Todd Hodgen wrote: > > I’m am wondering if those efforts could be served even better by > > development of a tool that looks through logs and searches for common > > issues – maybe flagging items that seem out of place in a normal call > > flow, or events that are not happening in the same or correct > > sequence, etc. I’m sure there are far too many to do an outstanding > > job, but maybe as common issues are identified they could be put into > > a script that helps to identify them in the future? > > > > > > > > Logs are great, and SIPXViewer is an outstanding tool. Would the next > > step in that evolution be some intuitiveness in reading the logs and > > creating a report. Similar to a broken links report in some of the > > web development tools, or similar to some of the scripts that check > > for spybots, etc. and report anomalies that they find? > > > > > > > > As a non-career hacker of some very basic code, and nothing serious > > like this, I admit I don’t understand all the nuances, but maybe > > someone with that experience can say whether that is feasible or not. > > An evolving tool that grows as lessons are learned. I assume it could > > be a module that is written and doesn’t have to be integrated to the > > rest of the project to be effective.
On Fri, 2009-05-29 at 15:10 -0400, Kevin Thorley wrote: > > Personally, I think this is a great idea. An expert system that can > troubleshoot sipX would be very useful. I think the first step in such > a task would be to break this suggestion into more manageable chunks. There is a good collection of sipviewer issues at: http://track.sipfoundry.org/secure/IssueNavigator.jspa?reset=true&&pid=10130&resolution=-1&component=10381&sorter/field=issuekey&sorter/order=DESC&sorter/field=updated&sorter/order=DESC Most of those issues are focused on either making sipviewer more usable or better integrating it into the environment, but sipviewer also has much of the information available - having it also be able to do expert system style analysis of what's happening would not be all that complex. There are many common failures in SIP that it could be made to recognize. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
