<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">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. <br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Nov 15, 2019, at 8:38 PM, Troy Bowman <troy@lump.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Fri, Nov 15, 2019 at 3:56 PM John Kiniston <<a href="mailto:johnkiniston@gmail.com">johnkiniston@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>I do not recommend using chan_sip, chan_sip is no longer receiving development.</div></div>chan_pjsip is where the development focus is at. <br></div></blockquote><div><br></div><div>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.</div><div><br></div></div></div>
<span>-- </span><br><span>_____________________________________________________________________</span><br><span>-- Bandwidth and Colocation Provided by http://www.api-digital.com --</span><br><span></span><br><span>asterisk-dev mailing list</span><br><span>To UNSUBSCRIBE or update options visit:</span><br><span> http://lists.digium.com/mailman/listinfo/asterisk-dev</span></div></blockquote></body></html>