>
> I saw a developer politely asking if there would be interesting on some
> alternative proprietary well-written SIP stack.
how do You know "well-written" if closed source?
FM: The bottom line is you don't know. But you don't know because it hasn't been tried and used yet, not because its closed source. When this project is complete, people will be able to try and use it. If the implementation is superior to the existing chan_sip, it will continue to be used. If it is not superior, it will not be used. That's the market doing its job.
> The answer is YES, there
> are people who want this kind of support specially if bundled with the
> patent encumbered codecs that will not make into callweaver any time
> soon.
stay on topic pls. codecs are not in a session initiation protocol (SIP).
and we shouldn't give a shit on that U.S. lawyers trivial software patents bullshit.
besides, the community has nearly always managed to give reverse-engineered
and clean room designed replacements for codecs, since mp3 times.
FM: This is an interesting topic. The Cornfed client does include a G.729 codec and Cornfed is able to manage the payments of royalties to the patent holder. This is unfortunate but its just the way it is. If there are customers that need G.729, this could provide an option for them.
>
> I hope you have not scared the man. :-)
he must take it. this sounds like censorship.
FM: With all due respect, I wish I had a dime for all the criticism I've taken over time from open-source advocates. My skin is thick...
BTW, this project is going to go forward. Based primarily on other feedback besides what I've heard from this list there appears to be a need and so we are going to go ahead with the development
Thanks,
FM
_______________________________________________ Callweaver-dev mailing list Callweaver-dev@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-dev
