12 Oct
2008
12 Oct
'08
8:45 p.m.
Gotcha. Well, I re-ran the capture on another test call and ended the
capture a few seconds after I hung up, and still shows the same path.
Ok, here is my proxy_challenge; I put that xlog in it, and sure enough it's
entering. Now, I have my provider's IP in my trusted table, so I am not
sure why it's challenging...
if (!(method=="REGISTER"))
{
if (!allow_trusted())
{
if (!proxy_authorize("", "subscriber")) {
$var(debug) = proxy_authorize("",
"subscriber");
xlog("L_INFO", "Proxy authentication failed -
M=$rm
RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n");
proxy_challenge("", "0");
exit;
}
fix_nated_sdp("11");
consume_credentials();
# at this point caller is authenticated
}
}
On 10/12/08 12:32 PM, "Juha Heinanen" <jh(a)tutpro.com> wrote:
Graham Wooden writes:
Yeah, I see that 407 Proxy Auth too, but I am not
sure where to check for
that.
Here is my only challenge statement:
if (is_method("REGISTER"))
{
if (!www_authorize("", "subscriber"))
{
www_challenge("", "0");
exit;
}
407 comes from proxy_challenge. either your config has one or not all
packets were shown in capture.
this starts to consume too many cycles that are away from writing code.
dig into your config file and make sure that wireshark captures all
packets.
-- juha