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

[Faidon Liambotis]

On 11/13/12 13:14, Saúl Ibarra Corretgé wrote:
> I have some experience in this area and I can tell you we had to patch
> PJSIP and there was no way around.

If that's the case, then I'd say that PJSIP would be the wrong choice then.

> Well, dependencies can be troublesome, look at libstrp. Upstream looks
> abandoned and the version some distros package didn't contain all fixes
> which were on CVS and some of them were pretty critical. Guess what,
> PJSIP bundles it. And PortAudio. And more of them, see third_party/.

Yikes! So, this embedding effect recurses into PJSIP, where it bundles
all kinds of forked libraries within it? Where does that stop? This is
no way to maintain a project, that's a maintainability and security
nightmare.

> I think you are over optimistic about how PJSIP's internals work and how
> easy it is to integrate it with another project.

Note I've stated many times that everything I said should be applied as
criteria for *picking* a stack. If PJSIP can't be made to work like this
then I wholeheartedly believe that it shouldn't be used.

Regards,
Faidon