I found this in the sipstatus.log: "2010-10-20T08:46:36.635044Z":756:AUTH:DEBUG:test.voip.ikt-bs.de:SubscribeServerThread:B6D61B90:SipStatus:"SubscribeServerThread::isAuthenticated() - No Credentials for mailboxUrl=\"<sip:2...@test.voip.ikt-bs.de:5060>;transport=udp\", reqRealm=\"test.voip.ikt-bs.de\", reqUser=\"203\""
Does that mean the credentials are wrong or that it's not supplying the parts it needs for an MWI subscription? The from tag matches. Also BLF subscriptions (from the OpenStage phone to a Snom phone, subscribing to an OpenStage phone won't work and has a tendency to crash the phone's SIP system) work. Am 19.10.2010 18:58, schrieb Worley, Dale R (Dale): > 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 > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
