reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate] Authentication failed

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
username="test1",realm="192.168.0.161",nonce="46d619bf3cbdd395f431c451 52d54c98d1de88ed",uri="sip: 192.168.0.161",response="968582fa56dc59346550d18425adbafa" 


Call-ID:1ACF86B077442073D5FE973BC1DF0CF2@xxxxxxxxxxxx

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@xxxxxxxxxxxxx;user=phone>;tag=6E3D02005F254009004E48F4
To:<sip: 721@xxxxxxxxxxxxx;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.2a6 6 


Call-ID:1ACF86B077442073D5FE973BC1DF0CF2@xxxxxxxxxxxx

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@xxxxxxxxxxxx> 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@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="46d39c43db6d2e9d3b891ae9



87789153c2c37444",uri="sip:






192.168.0.161",response="2541aca7d2519bf160078c2b5f913e88",algorithm=M



D5
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.




=== message truncated ===
______________________________________________________________________ ______________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. 
http://farechase.yahoo.com/
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel