I’ve been using it in several production systems for nearly a year now on the 16 branch and it has yet segfault. My remaining chan_sip Asterisk 13 systems dump code at least once or twice every 3 months or so. I feel very safe saying chan_pjsip is stable enough for my production needs.
Sent from my iPhone > On Nov 15, 2019, at 8:38 PM, Troy Bowman <t...@lump.net> wrote: > > >> On Fri, Nov 15, 2019 at 3:56 PM John Kiniston <johnkinis...@gmail.com> wrote: > >> I do not recommend using chan_sip, chan_sip is no longer receiving >> development. >> chan_pjsip is where the development focus is at. > > Sure, chan_pjsip is where the feature development focus is, but is it truly > stable enough for production now? It seems I still see a lot of bug fixes > for seemingly constant problems, while chan_sip's code is so mature that it > just works hands-off. I'm still afraid of using chan_pjsip in production > just like I am still afraid of Linux's btrfs in production, and btrfs has > been in development for over a decade. > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
