[reSIProcate] Authentication failed

Thu Sep 27 11:37:08 CDT 2007

	I have tried this using resip's code, and it is not giving the same  
result that is in the trace. I can't get resip to generate the  
response you're seeing with the stuff in the Authorization header.  
Furthermore, resip's code generates the same response as the M-CAS  
user agent. Can you send full DEBUG-level logging? Also, if you can,  
apply the attached patch to your checkout of resip (this will add a  
logging statement that should ensure that your configuration is what  
you think it is).

Best regards,
Byron Campen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: logDigest.patch
Type: application/octet-stream
Size: 886 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070927/775fcb6e/attachment.obj>
-------------- next part --------------


> The password is the same, that is: test1
>
> Thanks a lot.
> Sean.
>
>
> --- Byron Campen <bcampen at estacado.net> wrote:
>
>> 	So, about the only thing we can do at this point is
>> to try to figure
>> out if it is a config problem (whitespace at the end
>> of a password or
>> something similar). What is the password for test1?
>>
>> Best regards,
>> Byron Campen
>>
>>> can anyone help me on this problem?
>>> is there any problem on resiprocate's
>> authentication
>>> part?
>>>
>>>
>>> --- Sean <yunjnz at yahoo.com> wrote:
>>>
>>>> Thanks for your help.
>>>> The following is the succeeded SIP messages
>>>> transported by other UAs and the same server:
>>>>
>>>> REGISTER sip:192.168.0.161 SIP/2.0
>>>> Via:SIP/2.0/UDP
>>>> 192.168.0.50:5060;branch=z9hG4bKC7BF07D991
>>>>
>>>
>>
> From:<sip:721 at 192.168.0.161;user=phone>;tag=6E3D02005F254009004E48F4
>>>> To:<sip:721 at 192.168.0.161;user=phone>
>>>> Contact:<sip:192.168.0.50>
>>>> Expires:3600
>>>>
>>>
>>
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2 at 192.168.0.50
>>>> CSeq:1 REGISTER
>>>> Max-Forwards:70
>>>> User-Agent: M-CAS/1.0 (AD100SE 91.11;
>>>> NTTEAST/NTTWEST)
>>>> Content-Length:0
>>>>
>>>> SIP/2.0 401 Unauthorized
>>>> Via:SIP/2.0/UDP
>>>> 192.168.0.50:5060;branch=z9hG4bKC7BF07D991
>>>>
>>>
>>
> From:<sip:721 at 192.168.0.161;user=phone>;tag=6E3D02005F254009004E48F4
>>>>
>>> To:<sip:
>>>
>>
> 721 at 192.168.0.161;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.5e5
>>
>>> 3
>>>>
>>>
>>
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2 at 192.168.0.50
>>>> CSeq:1 REGISTER
>>>> WWW-Authenticate: Digest realm="192.168.0.161",
>>>> nonce="46d619bf3cbdd395f431c45152d54c98d1de88ed"
>>>> Server: OpenSER (1.2.2-notls (i386/linux))
>>>> Content-Length: 0
>>>>
>>>> REGISTER sip:192.168.0.161 SIP/2.0
>>>> Via:SIP/2.0/UDP
>>>> 192.168.0.50:5060;branch=z9hG4bK2514E4D993
>>>>
>>>
>>
> From:<sip:721 at 192.168.0.161;user=phone>;tag=6E3D02005F254009004E48F4
>>>> To:<sip:721 at 192.168.0.161;user=phone>
>>>> Contact:<sip:192.168.0.50>
>>>> Expires:3600
>>>> Authorization:Digest
>>>>
>>>
>>
> username="test1",realm="192.168.0.161",nonce="46d619bf3cbdd395f431c451
>>
>>> 52d54c98d1de88ed",uri="sip:
>>>
>>
> 192.168.0.161",response="968582fa56dc59346550d18425adbafa"
>>>>
>>>
>>
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2 at 192.168.0.50
>>>> CSeq:2 REGISTER
>>>> Max-Forwards:70
>>>> User-Agent: M-CAS/1.0 (AD100SE 91.11;
>>>> NTTEAST/NTTWEST)
>>>> Content-Length:0
>>>>
>>>> SIP/2.0 200 OK
>>>> Via:SIP/2.0/UDP
>>>> 192.168.0.50:5060;branch=z9hG4bK2514E4D993
>>>>
>>>
>>
> From:<sip:721 at 192.168.0.161;user=phone>;tag=6E3D02005F254009004E48F4
>>>>
>>> To:<sip:
>>>
>>
> 721 at 192.168.0.161;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.2a6
>>
>>> 6
>>>>
>>>
>>
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2 at 192.168.0.50
>>>> CSeq:2 REGISTER
>>>> Contact: <sip:192.168.0.50>;expires=3600
>>>> Server: OpenSER (1.2.2-notls (i386/linux))
>>>> Content-Length: 0
>>>>
>>>>
>>>>
>>>>
>>>> --- Byron Campen <bcampen at estacado.net> wrote:
>>>>
>>>>> 	Can you also send a trace of the other UA? It
>> is
>>>>> possible that ser
>>>>> is nitpicking parts of the Authorization header
>>>> (for
>>>>> instance, the
>>>>> uri portion does not match the From header,
>> which
>>>>> some
>>>>> implementations don't like)
>>>>>
>>>>> Best regards,
>>>>> Byron Campen
>>>>>
>>>>>> The following is the SIP messages captured:
>>>>>>
>>>>>> REGISTER sip:192.168.0.161 SIP/2.0
>>>>>> Via: SIP/2.0/UDP
>>>>>>
>>>>>
>>>>
>>>
>>
> 192.168.0.170:5160;branch=z9hG4bK-d8754z-5579f2ea1793031c-1---
>>>>>
>>>>>> d8754z-;rport
>>>>>> Max-Forwards: 70
>>>>>> Contact:
>>>>>>
>>>>>
>>>>
>>>
>>
> <sip:789 at 192.168.0.170:5160;rinstance=385a6960bf7c71df>
>>>>>> To: <sip:789 at 192.168.0.161>
>>>>>> From: <sip:789 at 192.168.0.161>;tag=6cf8ed5b
>>>>>> Call-ID:
>>>>> NzAyMjkxYTYxOWJmZWNlZWFmYmNlYTBkZDQ0MzA1MTU.
>>>>>> CSeq: 1 REGISTER
>>>>>> Expires: 3600
>>>>>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
>> NOTIFY
>>>>>> User-Agent: vosip
>>>>>> Content-Length: 0
>>>>>>
>>>>>> SIP/2.0 401 Unauthorized
>>>>>> Via: SIP/2.0/UDP
>>>>>>
>>>>>
>>>>
>>>
>>
> 192.168.0.170:5160;branch=z9hG4bK-d8754z-5579f2ea1793031c-1---
>>>>>
>>>>>> d8754z-;rport=5160
>>>>>> To:
>>>>>>
>>>>>
>>>>
>>>
>>
> <sip:789 at 192.168.0.161>;tag=329cfeaa6ded039da25ff8cbb8668bd2.b17d
>>>>>> From: <sip:789 at 192.168.0.161>;tag=6cf8ed5b
>>>>>> Call-ID:
>>>>> NzAyMjkxYTYxOWJmZWNlZWFmYmNlYTBkZDQ0MzA1MTU.
>>>>>> CSeq: 1 REGISTER
>>>>>> WWW-Authenticate: Digest realm="192.168.0.161",
>>>>>>
>> nonce="46d39c43db6d2e9d3b891ae987789153c2c37444"
>>>>>> Server: OpenSER (1.2.2-notls (i386/linux))
>>>>>> Content-Length: 0
>>>>>>
>>>>>> REGISTER sip:192.168.0.161 SIP/2.0
>>>>>> Via: SIP/2.0/UDP
>>>>>>
>>>>>
>>>>
>>>
>>
> 192.168.0.170:5160;branch=z9hG4bK-d8754z-19afb1b33ad600e9-1---
>>>>>
>>>>>> d8754z-;rport
>>>>>> Max-Forwards: 70
>>>>>> Contact:
>>>>>>
>>>>>
>>>>
>>>
>>
> <sip:789 at 192.168.0.170:5160;rinstance=385a6960bf7c71df>
>>>>>> To: <sip:789 at 192.168.0.161>
>>>>>> From: <sip:789 at 192.168.0.161>;tag=6cf8ed5b
>>>>>> Call-ID:
>>>>> NzAyMjkxYTYxOWJmZWNlZWFmYmNlYTBkZDQ0MzA1MTU.
>>>>>> CSeq: 2 REGISTER
>>>>>> Expires: 3600
>>
> === message truncated ===
>
>
>
>        
> ______________________________________________________________________ 
> ______________
> Shape Yahoo! in your own image.  Join our Network Research Panel  
> today!   http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
>
>