there is no point in sending 401 Unauthorized to a UAS that sent us a properly-format...
commit8f3c6d0d98092c0eb6556c4a5f44310a282bb2f5
authorkpfleming <kpfleming@614ede4d-c843-0410-af14-a771ab80d22e>
Tue, 4 Sep 2007 16:40:39 +0000 (4 16:40 +0000)
committerkpfleming <kpfleming@614ede4d-c843-0410-af14-a771ab80d22e>
Tue, 4 Sep 2007 16:40:39 +0000 (4 16:40 +0000)
tree102eee2086471632134f2725d18759b209eead6d
parent026e37d70b7bfa0cb833f1e1bd0b6182f7e5d4b0
there is no point in sending 401 Unauthorized to a UAS that sent us a properly-formatted Authentication header with the expected username and nonce but an incorrect response (which indicates the shared secret does not match)... instead, let's send 403 Forbidden so that the UAS doesn't retry with the same authentication credentials repeatedly

git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@81442 614ede4d-c843-0410-af14-a771ab80d22e
channels/chan_sip.c