Re: [reSIProcate-users] Authentication problem
Thanks, do you mean the SIP messages transmitted?
Please read the following messages transmitted between
the registrar server and the Resiprocate UA:
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
--- Byron Campen <bcampen@xxxxxxxxxxxx> wrote:
> Can you provide traces of this? If the stack is
> retransmitting the
> REGISTER, the 401 must not be making it intact.
>
> Best regards,
> Byron Campen
>
> > Greetings,
> >
> > I'm developing a UA on Resiprocate, now I meet a
> > problem,
> > when my UA trying to register to the server (SER),
> the
> > server replies 401 unauthorized,
> > but it seems that sometimes the onFailure function
> > isn't called,
> > and after catching the packets I find that the
> > Resiprocate automatically re-send the REGISTER
> request
> > after receiving the 401 response message,
> > but it didn't ACK the message.
> > after the automatically re-sent REGISTER message,
> the
> > server replies 500 Internal error.
> > can anyone help me on this problem?
> >
> > Thanks a lot.
> > Sean
> >
> >
> >
> >
> >
> >
>
______________________________________________________________________
>
> > ______________
> > Building a website is a piece of cake. Yahoo!
> Small Business gives
> > you all the tools to get online.
> > http://smallbusiness.yahoo.com/webhosting
> > _______________________________________________
> > resiprocate-users mailing list
> > resiprocate-users@xxxxxxxxxxxxxxxxxxxx
> > List Archive:
>
http://list.resiprocate.org/archive/resiprocate-users/
>
>
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/