It's though to diagnose authorization problems, because the computation of the hash is fairly complex.
Set the logging level to DEBUG and see if /var/log/sipxpbx/sipstatus.log reports anything interesting. One thing to check is that when the UA re-sends the SUBSCRIBE after being challenged, that it uses the same from-tag. The interop server configuration notes: sipXinterop/http_rootdir/index.html.pre.in The authentication nonces provided by sipXecs are specific to the from-tag in the request. Section 8.1.3.5 of RFC 3261 requires that a re-sent request has the same from-tag as the original request, so the nonce that sipX returns in a 401/407 response can always be used in a re-send of the request. In general, checking the hashes is a tedious computation. The program extras/calculate-auth-hash can be used to repeat the calculation. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
