On Mon, Apr 17, 2017, at 02:05 PM, Steve Murphy wrote: <snip>
> > Many thanks, the above gives me a glimpse into the workings and > organsization in pjsip! > > > I have asked (again) the groups, and the folks that have reported > problems > with pjsip, > > are standing by their claims. The 53i and the 57i (iirc) are not able to > hold registration > on Asterisk 13.5, with either the as-is chan_sip driver, or the as-is > pjsip > driver. > > I am trying, without success so far, to get an old 53i going under pjsip > in > my own > environment. It has been frustrating. > > We have a patch for chan_sip dating back to the 1.6 days, that solves the > problem, > but only for chan_sip (even the one in 13.5). > > If this is a bug in pjsip, and the framework of the existing driver is > truly already checking > the status of the "first" request vs the incoming request, then mayhaps > we > can apply > the same sort of fixesin pjsip. Is this a bug, then? Should I file a bug > report? It would be a different underlying fix as the registrar in PJSIP is actually doing things according to spec. The chan_sip implementation is simpler and basic. This should indeed be filed as a bug[1] with configuration and console output with SIP traffic. [1] https://issues.asterisk.org/jira -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- 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
