Re: [reSIProcate] Authentication failed

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	That is certainly a possibility; the md5 code relies on preprocessor  
macros to determine the endianness of the platform. What preprocessor  
macro does your platform use to indicate that it is big endian? Right  
now we're checking __BIG_ENDIAN__ (OS X), _BIG_ENDIAN (Solaris), and  
WORDS_BIGENDIAN (looks like GNU/linux).

Best regards,
Byron Campen

> Thanks for your help,
> I found that the result isn't the same for each time,
> by the way, I'm not using PC but on a MIPS 64 bit
> processor, which is Big-Endian,
> are there any relations with this environment?
>
> Best regards,
> Sean
>
>
>
> --- Byron Campen <bcampen@xxxxxxxxxxxx> wrote:
>
> >         Ok, so the response that Helper::makeResponseMD5()
> > is getting on my
> > laptop is 7b70dcbc4795e691151532dffe0b2c3b. This is
> > correct as far as
> > I can tell (I have checked by hand). Is this
> > consistent with what
> > you're seeing?
> >
> > Best regards,
> > Byron Campen
> >
> >
> > > I've applied the patch you provided,
> > > and the following is the output:
> > >
> > > ClientAuthManager::RealmState::addAuthentication
> > > user="test1"
> > > password="test1"
> > > realm="192.168.0.161"
> > > method="REGISTER"
> > > uri="sip:192.168.0.161"
> > > nonce="46fc6185e2820d8645d037bec59f942b1ecc747d"
> > > qop=""
> > > cnonce=""
> > > cnonceCount=""
> > > ClientAuthManager::RealmState::addAuthentication
> > > user="test1"
> > > password="test1"
> > > realm="192.168.0.161"
> > > method="REGISTER"
> > > uri="sip:192.168.0.161"
> > > nonce="46fc6185e2820d8645d037bec59f942b1ecc747d"
> > > qop=""
> > > cnonce=""
> > > cnonceCount=""
> > > ClientAuthManager::RealmState::addAuthentication
> > > user="test1"
> > > password="test1"
> > > realm="192.168.0.161"
> > > method="REGISTER"
> > > uri="sip:192.168.0.161"
> > > nonce="46fc6186593cb8809361b4cca006d0be0a15e5d8"
> > > qop=""
> > > cnonce=""
> > > cnonceCount=""
> > > ClientAuthManager::RealmState::addAuthentication
> > > user="test1"
> > > password="test1"
> > > realm="192.168.0.161"
> > > method="REGISTER"
> > > uri="sip:192.168.0.161"
> > > nonce="46fc6186593cb8809361b4cca006d0be0a15e5d8"
> > > qop=""
> > > cnonce=""
> > > cnonceCount=""
> > > UserAgent:;onFailure: Register 401
> > > UserAgent:;onFailure: Register 401
> > >
> > > Thank you and best regards,
> > > Sean.
> > >
> > >
> > >
> > >
> > >
> > > --- Byron Campen <bcampen@xxxxxxxxxxxx> wrote:
> > >
> > > >         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
> > > >
> > > > >
> > > >
> > > > > The password is the same, that is: test1
> > > > >
> > > > > Thanks a lot.
> > > > > Sean.
> > > > >
> > > > >
> > > > > --- Byron Campen <bcampen@xxxxxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxxxx;user=phone>;tag=6E3D02005F254009004E48F4
> > > > > > > > To:<sip:721@xxxxxxxxxxxxx;user=phone>
> > > > > > > > Contact:<sip:192.168.0.50>
> > > > > > > > Expires:3600
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2@xxxxxxxxxxxx
> > > > > > > > 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@xxxxxxxxxxxxx;user=phone>;tag=6E3D02005F254009004E48F4
> > > > > > > >
> > > > > > > To:<sip:
> 721@xxxxxxxxxxxxx;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.5e5
> > > > > > > 3
> > > > > > > >
> Call-ID:1ACF86B077442073D5FE973BC1DF0CF2@xxxxxxxxxxxx
> > > > > > > > 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@xxxxxxxxxxxxx;user=phone>;tag=6E3D02005F254009004E48F4
> > > > > > > > To:<sip:721@xxxxxxxxxxxxx;user=phone>
> > > > > > > > Contact:<sip:192.168.0.50>
> > > > > > > > Expires:3600
> > > > > > > > Authorization:Digest
> === message truncated ===
>
>
>
>        
> ______________________________________________________________________ 
> ______________
> Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s  
> user panel and lay it on us. http://surveylink.yahoo.com/gmrs/ 
> yahoo_panel_invite.asp?a=7