< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Authentication failed


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@xxxxxxxxxxxxx:5160;rinstance=385a6960bf7c71df>
To: <sip:789@xxxxxxxxxxxxx>
From: <sip:789@xxxxxxxxxxxxx>;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@xxxxxxxxxxxxx>;tag=329cfeaa6ded039da25ff8cbb8668bd2.b17d
From: <sip:789@xxxxxxxxxxxxx>;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@xxxxxxxxxxxxx:5160;rinstance=385a6960bf7c71df>
To: <sip:789@xxxxxxxxxxxxx>
From: <sip:789@xxxxxxxxxxxxx>;tag=6cf8ed5b
Call-ID: NzAyMjkxYTYxOWJmZWNlZWFmYmNlYTBkZDQ0MzA1MTU.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY
User-Agent: vosip
Authorization: Digest
username="test1",realm="192.168.0.161",nonce="46d39c43db6d2e9d3b891ae987789153c2c37444",uri="sip:192.168.0.161",response="2541aca7d2519bf160078c2b5f913e88",algorithm=MD5
Content-Length: 0

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
192.168.0.170:5160;branch=z9hG4bK-d8754z-19afb1b33ad600e9-1---d8754z-;rport=5160
To:
<sip:789@xxxxxxxxxxxxx>;tag=329cfeaa6ded039da25ff8cbb8668bd2.6ace
From: <sip:789@xxxxxxxxxxxxx>;tag=6cf8ed5b
Call-ID: NzAyMjkxYTYxOWJmZWNlZWFmYmNlYTBkZDQ0MzA1MTU.
CSeq: 2 REGISTER
WWW-Authenticate: Digest realm="192.168.0.161",
nonce="46d39c43db6d2e9d3b891ae987789153c2c37444"
Server: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0



--- Sean <yunjnz@xxxxxxxxx> wrote:

> Greetings,
> 
> I'm developing a UA on Resiprocate and I meet a
> problem on authentication,
> I've configured openser with mysql as the server of
> UA,
> the authentication method is www_authorize.
> but there is a problem, even after the UA responds
> with the authentication information calculated by
> the
> Resiprocate,
> the server still responds with 401 unauthorized
> message,
> and another UA, which is a mature product, is OK for
> the authentication.
> 
> can anyone help me on this problem?
> Thanks a lot.
> Sean.
> 
> 
>        
>
____________________________________________________________________________________
> Got a little couch potato? 
> Check out fun summer activities for kids.
>
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
>
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
> 



       
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo! 
FareChase.
http://farechase.yahoo.com/