[asterisk-dev] Recommendations for using a SIP stack with Asterisk

[Russ Meyerriecks]

On Tue, Nov 13, 2012 at 07:57:25PM +0100, Daniel Pocock wrote:
> But imagine if that is a user space library embedded in 50 different
> packages in Debian, another 30 packages in Fedora, etc.

> This is why distributions draw a line in the sand with this issue.

> If you just send a patch upstream, and don't invest the time to
> integrate it, make it work for users other than Asterisk, etc, then
> don't assume other people will invest that effort.  Your code will
> eventually diverge.  This also means more effort for you keeping track
> of patches/upgrades from upstream - and eventually they will start
> conflicting with your own code.

> If you are not `in' the project, and you just send patches, then I agree
> they won't get released as quickly as your users need them.

> This was my first experience of contributing to reSIProcate: supporting
> non-standard URIs from Cisco devices, and supporting the SER format of
> nonce in DIGEST.  Rather than hacking a fix that everybody else would
> have screamed about, I submitted generalized solutions:

> Those are valid points, but I feel that I've demonstrated that they
> don't have to lead to the same conclusion that you reached.
> 
> It really is important to think about the wider community of SIP users
> and developers out there.  Having a strong SIP stack used by many
> projects will greatly boost compatibility between products, which is
> absolutely essential if we are not all going to be squashed by Microsoft
> with their Skype/Lync monopoly.  You can already see them merging MSN
> into Skype, and cutting off Asterisk.  They must have been rubbing their
> hands in glee when they saw this:

+1 These are all great points.

-- 
Russ Meyerriecks
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
direct: +1 256-428-6025
Check us out at: www.digium.com & www.asterisk.org