Hi, I just have some troubles when using SIPp with OpenIMSCore. OpenIMSCore recently upgraded the authentication algorithm to support the qop-parameter. That's fine.
The WWW-Authenticate header field in "401 Unauthorized" response from OpenIMSCore now contains the qop parameter: qop="auth,auth-int". But the next REGISTER request sent by SIPp contains an Authorization header field with a qop parameter with wrong syntax and semantic: qop=auth,auth-int. Only one of the alternatives "auth" or "auth-int" should be selected in the qop parameter. According to RFC 2617 the value of the qop parameter MUST be one of the alternatives the server indicated in the WWW-Authenticate header. So a qop parameter qop=auth-int would be perfect if the response parameter is also calculated correctly. A correct Authorization header field should look like: Authorization: Digest username="[EMAIL PROTECTED]",realm="net1.test",nonce="AlzSH3r4r3XJVFejmXb9cfot nn/KHwAA3jMuEhKyjzE=",uri="sip:net1.test",algorithm=AKAv1-MD5,response="a7e0 dde1b0aae6f0d9e93370380b05f9",qop=auth-int,nc=00000001,cnonce="9756535152495 749" Can that be corrected in SIPp? regards Franz ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
