[SR-Users] Authentication issue during registration

[Austin Einter]

I took SBC *out* from my test scenario.
So it is just endpoint -> Kamailio.

Then I found same issue, Kamalio challanges repeatedly.

One of the reason I suspect is, in my case for REGISTER message to uri and
from uri are different.
Can that cause Kamailio to challenge it repeatedly.

On Mon, Sep 14, 2015 at 6:36 PM, Austin Einter <austin.einter at gmail.com>
wrote:

> I took SBC from my test scenario.
> Then I found same issue, Kamalio challanges repeatedly.
>
> One of the reason I suspect is, in my case for REGISTER message to uri and
> from uri are different.
> Can that cause Kamailio to challenge it repeatedly.
>
> Thanks
> Austin
>
>
>
> On Mon, Sep 14, 2015 at 11:22 AM, Austin Einter <austin.einter at gmail.com>
> wrote:
>
>> Hi All
>> I have a typical requirement, where I have a forwarding SBC between an
>> endpoint and kamailio as shown below.
>>
>> Endpoint ----> SBC ------> Kamailio
>>
>> From endpoint I am sending REGISTER request. It reaches SBC. SBC sends
>> the REGISTER request to Kamailio, Kamailio challenges it (401), and
>> challenge response is received at endpoint through SBC.
>>
>> Next endpoint adds authorization header and sends REGISTER to SBC, SBC
>> forwards it to Kamailio.
>>
>> Now Kamailio again responds with 401.
>>
>> When we analysed Kamailio logs, we can see Kamailio log authorization
>> response token and response token that was sent by Endpoint are same.
>>
>> So my question is, why Kamailio sends 401 repeatedly even if it received
>> proper Authorization header.
>>
>> Is it because Kamailio received REGISTER from IP address different from
>> endpoint.
>>
>> Please guide, how can I avoid this issue.
>>
>> Thanks
>> Austin
>>
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150914/d39b37fa/attachment.html>