[Asterisk-Users] SIP Testing

[Chris Witte]

>>
>
> Maybe I just need to make a page where we can vote :)
>
> Mark
>

Not sure if the implication here was to be create  a page that collects 
votes on how to proceed with testing, or one that collects votes on the 
quality of the current SIP code in CVS?

Seems to me that a good approach would be to create a linux client that 
could report SIP test results to a server  where they could be tallied 
and displayed.  The client could either automatically collect (or pull 
from a .rc file) lots of mundane info that the reporter wouldn't want to 
key in every time, and would be likely to key incorrectly (if they type 
like me:-)

Some stuff the client might be able to collect automatically...

1) Current release number of * (possiby date/tstamp/chksum info for each 
src member, to ensure the client build is complete and current)
2) hardware platform, (client device list), kernel/module info
3) auto-attach error logs from * (too big brother-ish?  bandwidth 
concerns? )
4) automatically authenticate and identify the tester
5) configurable prompts, so the tester only has to answer questions 
relevant to their hardware platform

...you get the idea.  Anyway, I like the idea of encouraging people to 
submit test results, and the easier it is to do, the more likely users 
are to submit them.  Most developers can relate to the frustration of a 
bug report w/o enough supplementary info to recreate the problem.  This 
approach seems like it could help both sides.

Chris.