Hi Adam, I have attached a new patch that disables a particular check for the presence of the qop paramater in the sipXproxy code in http://track.sipfoundry.org/browse/XX-7997.
I have check the digest verification functions of sipx and the implementation does allow qop to be absent. However I currently have no means to test it due to the absence of a RFC 2069 only UA. I talked to Douglas and he is willing to create a patched RPM for you to test with. If you can test it with your client we could permanently commit the patch to the master branch and have it with the next update for 4.4. Joegen On 03/22/2012 06:29 AM, Adam Newman wrote: > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To:<[email protected]> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8<66816> > Message-ID:<[email protected]> > > > > *Bump* > > Please note that I have been scouring the issue tracker for > this problem and all I can see is that SIPXecs has been made > to meet RFC 2617. I couldn't find any reference to > backward-compatibility with RFC 2069, with the exception of > the quote in my previous post which was done (exactly) two > years ago to the day. > > I'm quite new to sipfoundry so please let me know if there > is something obvious that I am missing here. Should I raise > this as a bug on the issue tracker? Any help would be much > appreciated. > > Cheers, > Adam. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
