On Fri, 2009-05-29 at 11:54 -0700, Todd Hodgen wrote: > I see many emails on the User-list from some obviously very talented > programmers who are helping others get their sipx products up and > running. I for one am grateful for the assistance you provide > everyone, and it is what makes your product successful today. Of > course I often wonder if we are wasting the time of this talent and > keeping great features from being developed or tested because of it. > Understanding it’s a learning experience for the software team as > well, I’m wondering if what they learn from that experience can be put > to use after learning it, and allow them to move to other issues and > discussions. > > > > 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. > >
Todd, 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. For instance, take an area that frequently causes issues and see if we can find a way to detect and suggest solutions for this situation. We have started to make some progress in this area with the test features put into sipXconfig in 4.0. Specifically the DNS Advisor (despite its faults) tries to help an admin understand why their DNS is or isn't working. Kevin _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
