*This message was transferred with a trial version of CommuniGate(tm) Pro* thomas schorpp wrote:
> replacing chan_sip by a closed source and proprietary licensed blob > will not help CW. Any why would it not help? What's wrong with having a choice? The situation with SIP isn't really unique. The available open source ISDN stacks aren't exactly the kind of quality that many paying customers expect when they pay money to have a telephone system set up for them. And as we have seen, Sangoma have realised this and decided its not worth the trouble for them nor for their customers, so they licensed a commercial ISDN stack from NetBricks to ship with their new BRI card. Same thing for SS7, there are at least two open source choices, but many companies have chosen to pay a little extra to use a commercial stack instead. So why should we not have that very same choice with SIP, too? You are not going to be forced to use it. You can continue to use chan_sip if you so desire. > remember GPL allows "commercial use" if You "provide warranty". > better lets get chan sip mature instead of replacing with a > proprietary. It would seem there is a bit of a misunderstanding about the term "potential replacement". It doesn't mean that chan_sip would be withdrawn. It simply means you get a choice to plug into a commercial alternative if you don't want to use chan_sip. As for getting chan_sip mature, .... ahem .... there is absolutely no way that anybody could achieve that by any other means than throwing it away and rewrite it from scratch. Not even the proverbial million monkeys on typewriters with infinite time could achieve such a miraculous transformation. _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
