Sounds like a bug to me. Could you file a jira on this? Mike On Aug 21, 2012, at 4:50 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hi Mike,
On 8/21/12 10:27 PM, Michael Jerris wrote:
auth-calls false means we won't challenge invite, accept-blind-auth means if auth headers are there, we ignore them.
it is what I expected from auth-calls (and worked like this in the past), but now even if set to false, the calls are challenged with 407 reply for authentication. Only when I set accept-blind-auth to false there is no 407.
Overall, it gets me what I need, access being granted on IP acl, but I wanted to double check if such change in behaviour of auth-calls was done on purpose. I will review my changes comparing with the default configs to see if I modified other params that could result in this situation, although I think there is no other related parameter.
Cheers, Daniel
Mike
On Aug 21, 2012, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
in the past I used to set:
<param name="auth-calls" value="false"/>
in the sip profile in order to skip user authentication for calls.
Lately I started to play a bit with 1.2 stable branch and seems that setting auth-calls to false is no longer doing what I expected, calls being challenged for user authentication.
Setting instead the accept-blind-auth to false got me what I wanted, like:
<!-- accept any authentication without actually checking (not a good feature for most people) --> <param name="accept-blind-auth" value="true"/>
But from the comment (checked the wiki as well, but has the same text) is a bit unclear what is the real purpose for it.
Isn't auth-calls=false supposed to accept calls without user authentication anymore?
For this particular case, I play some announcements, like 'user not available', and should work also for calls coming from outside. The access is restricted by IP address ACL, allowing SIP traffic only from my Kamailio instance.