Hi Iñaki, I undretsand your frustration, however we at MBDSYS are very small team, so (and I suppose others contributors on the list are in similar situation), we have to make decisions based on priorities of paying clients. Othre bugs are sorted by triviality of the fix, so what happens is that trivial bugs are fixed quickly, and complicated are fixed mostly when paying client request it. We do hovewer appreciate VERY MUCH bug submissions. They get eventually fixed, it simply takes time.
Now about SIP stack. : We do have plan to switch to newer versions of eXosip and oSIP stacks, this will improve SIP conformance greatly. This will hapen however near the end of the year. Of course the best way to get things fixed is to submit a patch. The smaller the better. We LOVE small patches :) Thanks Vadim Le 19 mai 09 à 18:02, Iñaki Baz Castillo a écrit : > Hi, don't take me wrong, but I've been reporting several bugs [*] in > trac.qutecom.org, most of them related to SIP, others to the GUI, and > have received no replies for them in long time. > I'd really like to be a programmer and contribute to Qutecom with code > and patches, but it's not my case unfortunatelly, so I just can test > it and report bugs as detailed and explained as I can. But, does > somebody read them? at least, any comment or reply is welcome, it > means that somebody has read it :) > If definitively nobody will fix/improve bugs related to SIP, please > tell it to me so I leave checking and reporting them. > > Also, I've been checking the source code and the commits. If I'm not > wrong, there are no commits about SIP since long time (months or > years). Is there aim in improving SIP support in Qutecom? > > I've read about a future implementation of IAX protocol. Well, don't > take me wrong, but.. why?? IAX is a poorly designed protocol, and it's > not designed for phones (since it requieres signalling and media going > together). IAX is basically designed to interconnect Asterisk boxes, > no more. It was born since its creator didn't understand SIP and > wanted to have his own draft/RFC. The lazy excuse "IAX is better for > NAT" is something I'm tired to hear (always coming from people with no > real VoIP and telephony knowledge). > Instead of doing this stuff, I'd suggest to improve the current SIP > stack which is very buggy (of course, you developers decide in which > subjects to spent your time, I'm just giving my opinion). > > Again, please don't take me wrong, I'm just a bit disappointed. In any > other project in which I report bugs I usually get feedback on them > and this encourages me on reporting more bugs and doing more testing. > :) > > Again, I offer myself to improve the SIP features of Qutecom by giving > you info and specifications on how some SIP features should work > according to standards. If you want, ask for such a questions to me > and I'll try to reply the best I can. > > Best regards. > > > [*] > http://trac.qutecom.org/ticket/76 > http://trac.qutecom.org/ticket/85 > http://trac.qutecom.org/ticket/86 > http://trac.qutecom.org/ticket/87 > http://trac.qutecom.org/ticket/88 > http://trac.qutecom.org/ticket/89 > http://trac.qutecom.org/ticket/93 > http://trac.qutecom.org/ticket/94 > http://trac.qutecom.org/ticket/97 > > > -- > Iñaki Baz Castillo > <[email protected]> > _______________________________________________ > QuteCom-dev mailing list > [email protected] > http://lists.qutecom.org/mailman/listinfo/qutecom-dev _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
