Woof!
On Fri, 10 Jul 2009 12:09:05 -0400, Anthony Minessale
wrote:
> The way it works by default is that if you send a www-authenticate, we
> *always* try to process it.
> HOWEVER, we have a accept-blind-auth sofia profile param (in fact it was
> invented just for sipX)
Then my understanding w
The way it works by default is that if you send a www-authenticate, we
*always* try to process it.
HOWEVER, we have a accept-blind-auth sofia profile param (in fact it was
invented just for sipX)
On Fri, Jul 10, 2009 at 10:56 AM, Andy Spitzer wrote:
> Woof!
>
> It is my understanding, that if I
accept-blind-auth is for this scenario
/b
On Jul 10, 2009, at 10:56 AM, Andy Spitzer wrote:
> Woof!
>
> It is my understanding, that if I set
>
> in a SIP profile, it shouldn't challenge for authentication under
> any circumstances.
>
> However, if an INVITE contains a a Proxy-Authoriza
Woof!
It is my understanding, that if I set
in a SIP profile, it shouldn't challenge for authentication under any
circumstances.
However, if an INVITE contains a a Proxy-Authorization header from another
proxy, Sofia DOES challenge with a 407.
I'm aware one can set accept-blind-auth to
