[Serusers] WG: rpid again

[Greger V. Teigre]

Silly me, I didn't look too closely at your auth if structure, just assumed 
it was ok.
You need something like this (from the onsip.org auth example):
        # -----------------------------------------------------------------
        # INVITE Message Handler
        # -----------------------------------------------------------------
        if (!proxy_authorize("","subscriber")) {
                proxy_challenge("","0");
                break;
        }
        Lookup avps;
        append avps;

Your if only look up avps for the first INVITE (when ser sends back 
unauhtorized to the client).  Thus, you need to break after the proxy 
challenge. The next INVITE will then not enter the proxy_challenge call and 
continue (because proxy_authorize will be true if credentials are present 
and correct).

I recommend you to look at the ONsip.org Getting Stared document and the 
configs. They are meant to be best practice references that people can build 
their configs around.
g-)



----- Original Message ----- 
From: "Dirk Willbrandt" <dw at terralink.de>
To: <serusers at lists.iptel.org>
Sent: Wednesday, June 01, 2005 09:59 AM
Subject: Re: [Serusers] WG: rpid again


> Hi Greger,
> Hi list,
>
> I'm using the CVS Version from yesterday.
> I tried the Sip-Rpid=number but i get the same problem.
>
> Yesterday i tried some other things, append some hfs at another place and 
> so on.
> I can append a hf before the invite and befor the radius_proxy_authorize() 
> but when i copy the append-row after the proxy authorize it seems that it 
> would never be executed. Why ?
>
> Thanks
>
> Dirk
>
> Greger V. Teigre wrote:
>
>> The change done to ser 0.9.0 where Sip-Rpid RADIUS avpair was changed to 
>> Sip-AVP=rpid:number was rolled back. I believe CVS head has this change 
>> (though backwards compatible).  Hence: Use Sip-Rpid=number instead of 
>> SIP-AVP=rpid:number.
>> g-)
>> Dirk Willbrandt wrote:
>>
>>> Hi list !
>>>
>>> I have a Problem with the appending of an rpid with the
>>> functions avp_load_radius(), append_rpid_hf().
>>>
>>> In my Radius DB i have an SIP-AVP field which is filled with the Value
>>> rpid:[NUMBER]
>>> When i run manuall the Radius Reply-Query i get the correct value for
>>> SIP-AVP.
>>>
>>> Now, i reconfigured my ser.cfg so that an avp_load_radius() is
>>> executed after an incoming INVITE.
>>> My Radius is answering on the command and sends the correct SIP-AVP
>>> Value for the User.
>>>
>>> Now my Problem:
>>> I can't append the RPID or anything else to the SIP-Header after the
>>> answer from the Radius.
>>> So the call is going out without the rpid in the Header.
>>>
>>> Can anyone help me ?
>>>
>>> Here is the Configure-Snip:
>>>
>>> if (method=="INVITE") { # here comes the invite
>>>   if (!radius_proxy_authorize("")) { # for the digest avp_load_radius
>>> it seems that i must use an proxy auth
>>>      proxy_challenge("","0");       # and an proxy challenge
>>>      if(!avp_load_radius("digest")) {  # here i get the SIP-AVP from
>>> the radius
>>>         log(1,"Failure with the AVP-Value\n"); # if it fails i'll get
>>> a message
>>>         break; # go out
>>>      }
>>>      avp_print(); # print all avp's (this command is never executed
>>>      :( ) append_hf ("Remote-Party-ID: 111222333\r\n"); # append this
>>> silly row - it is never executed
>>>      append_rpid_hf("",
>>> ";party=calling;id-type=subscriber;screen=yes"); # append the rpid
>>>      from SIP-AVP - and this command is also never executed break; #
>>>   go out };
>>> route(3); # go to route block 3
>>> break; # end
>>> }
>>>
>>> I tried also this snippet without the breaks and proxy-commands but it
>>> doesn't work.
>>> I don't know what is wrong - please help me :s
>>>
>>> Thanks !
>>>
>>> Dirk
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> serusers at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>