[asterisk-dev] 13 November, 2012 New SIP stack update
Daniel Pocock
daniel at pocock.com.au
Wed Nov 14 16:20:21 CST 2012
On 14/11/12 21:47, Saúl Ibarra Corretgé wrote:
> Hi,
>
>> Hi Saúl,
>>
>> I'd be interested to hear your feelings about pjsip/python-sipsimple
>>
>> For example,
>>
>> - why did you end up keeping patches locally, was it awkward to work
>> with upstream, or license issues, or something else?
>>
>
> Disclaimer: What I'm sharing here are my personal thoughts and
> experience :-)
>
> It's mostly that not everything we do can be applied upstream. We have
> advanced reINVITE handling, but for most PJSUA users it's not useful, so
> the patch has been sitting there for years. We also embed the WebRTC
> AEC. And there are some APIs we broke because of how we interact with
> the library from Python. There is probably more which I don't recall
> from the top of my head.
>
> On top of that, PJSIP's design is not modular in that it doesn't
> dynamically load modules such as codecs at runtime, everything is
> embedded, so I fail to see how a single build would fit all.
That is a useful insight - do you see that changing upstream?
This suggests that packaging pjsip would be troublesome too, at least in
the current form
More information about the asterisk-dev
mailing list