I couldn't apply all patch "19051-19065.diff" because the code repository, for which it is made, differs from that which is accessible for me (http://github.com/dhubler/sipxecs). I have decided that for multiple "Accept:" lines problem it is enough to use a patch for "HttpMessage" function (http://track.sipfoundry.org/secure/attachment/26640/HttpMessage_patch.diff). I built a new "sipXtackLib" RPM package with this patch. After installation of the new package "415 Unsupported Media Type or Content Encoding" error has disappeared, however phone continued to reply with an error "501 Not Implemented" to sipXecs SUBSCRIBE messages. "501 Not Implemented" messages have disappeared after I have set SIP-B mode support in SPA942 phone. However in SIP-B compatible mode new problems were appeared. I have made a new snapshot: http://track.sipfoundry.org/secure/attachment/26641/sipx-snapshot-BLF-problem--SPA942-SIP-B-server-type-Broadsoft.tar.gz In my sipXecs configuration BLF is used by users 203 and 209.
-- Sincerely yours, Alexey Kanukhin On Wed, Sep 8, 2010 at 8:04 PM, Worley, Dale R (Dale) <[email protected]> wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Alexey Kanukhin > [[email protected]] > > Dale, thanks for the issue analysis. I have set Server Type to > Broadsoft in phone’s settings and the "Supported: replaces, eventlist" > header has appeared. However, with a new SPA942 configuration sipXecs > sends the reply with an error "415 Unsupported Media Type or Content > Encoding" to the phone’s SUBSCRIBE message. I have read your message > concerning the same error in the sipx-users mailing list. > _______________________________________________ > > You've run into the same problem as Jean-Hugues Royer, that multiple Accept > lines in SUBSCRIBE requests aren't handled correctly: > > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Jean-Hugues Royer > [[email protected]] > > Finally the RLS is not compliant with RFC4662 (and even RFC3261) because > it only accepts subscription with a single "Accept" line: > > Accept: application/dialog-info+xml,application/rlmi+xml,multipart/related > > while RFC4662 shows in its examples (and RFC3261 allows) multiples > "Accept" lines: > > Accept: application/dialog-info+xml > Accept: application/rlmi+xml > Accept: multipart/related > _______________________________________________ > > That's fixed in the patch 19051-19065.diff to XX-8474. > > Dale > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
