[Kamailio-Users] Handling 302s

[Graham Wooden]

Well, I got the 407 solved - I didn't have my loopback or enet address in
the trusted table.

So, I am closer. Next step is to get a B2BUA installed, like rtpproxy to
handle the audio, since I don't proxy any audio.  Any examples out there
where I can initiate the audio for this type of call?  Again, I don't
currently nor do I want to handle the audio for 'every' call.

Thanks,

-graham

On 10/12/08 12:45 PM, "Graham Wooden" <graham at g-rock.net> wrote:

> 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 at 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
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users