RE: [reSIProcate] REGISTER and authentication
I'd like to retract the debug statement that showed "SI" instead of "SIP/2.0
401 Unauthorized" - I actually pasted the debug statement in error. I
re-checked the debug output, and indeed, the offending line should read:
DEBUG | 20051206-181533.242 | c:\Test.exe | RESIP:TRANSACTION | 3660 |
TransactionState.cxx:1535 | Send to TU: TU: DialogUsageManager
size=0 SIP/2.0 401 Unauthorized
So, I guess the problem is not with header corruption. Is there some other
function that I need to call to use the Digest authentication (besides
setDigestCredential in my profile)?
I believe that the REGISTER message that I send should not contain any
authentication information in the header, am I right? If I do, then please
just *hint* on how I would do that.
Chee
-----Original Message-----
From: Yong, Chee Yeew [mailto:Chee-Yeew.Yong@xxxxxxxxxxxxxxx]
Sent: 07 December 2005 09:13
To: 'Byron Campen'
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] REGISTER and authentication
Hi all,
Below is the reply from Byron on my question. Guess he forgot to CC to the
list.
My reply is:
The resip version I am using is 0.9.0-5019.
Where is the best place to start debugging the code to find where the
corruption takes place?
I have also used Ethereal to snoop on the messages, Ethereal seems to be
parsing the SIP message fine - it can tell that it is "401 Unauthorized".
Chee
-----Original Message-----
From: Byron Campen [mailto:bcampen@xxxxxxxxxxxx]
Sent: 06 December 2005 19:04
To: Yong, Chee Yeew
Subject: Re: [reSIProcate] REGISTER and authentication
Looks like your request line is getting corrupted. Your message
should begin with something like
SIP/2.0 401 Unauthorized
but it looks like you're just getting
SI
Now, what bothers me is that this should be getting dropped on the
floor by the stack, but it is making it up to the TU (dum in this
case). What version of resip are you working with?
It is possible that this is some sort of abbreviation, but I haven't
seen it happen before. Anyone on the list have some insight?
Best regards,
Byron Campen
> Hello all,
>
> With help from posters for my previous post(s), I managed to send
> out a
> REGISTER message properly. However, I have come up with a problem with
> authenticating the REGISTER message.
> I send the REGISTER message, and I get a 401 Unauthorized from my
> SIP server
> (SER). This, I believe, is to challenge the client (UAC).
> I have set the digest information using setDigestCredential (under
> DUM), but
> I don't see any reply from the DUM to the 401 challenge. My
> application just
> 'hangs', with the last few debug messages of:
>
> =========== start of debug snippet ======================
>
> DEBUG | 20051206-181533.222 | c:\Test.exe | RESIP:TRANSPORT | 3660 |
> Transport.cxx:209 |
> incoming from: [ V4 192.168.200.1:5060 UDP received on:
> DP connectionId=0 ] connectionId=0 ]
> DEBUG | 20051206-181533.242 | c:\Test.exe | RESIP:TRANSACTION | 3660 |
> TransactionState.cxx:1535 | Send to TU: TU: DialogUsageManager
> size=0 SI
> To: <sip:user@xxxxxxxxx>;tag=a546667ff0304408d6cbea9f94abe364.bf9c
> From: <sip:user@xxxxxxxxx>;tag=4f403032
> Via: SIP/2.0/UDP
> 192.168.200.5:5060;branch=z9hG4bK-d87543-8451c1677735d827-1--
> d87543-;rport=5060
> Call-ID: fa6b8c1243056f5d@xxxxxxxxxxxx
> CSeq: 1 REGISTER
> Server: Sip EXpress router (0.10.99-dev0 (i386/linux))
> Warning: 392 192.168.200.1:5060 "Noisy feedback tells: pid=6048
> req_src_ip=192.168.200.5
> req_src_port=5060 in_uri=sip:192.168.200.1 out_uri=sip:
> 192.168.200.1
> via_cnt==1"
> WWW-Authenticate: Digest realm="mylab.com",
> nonce="4395d5390c9d4c91b0b724bfb102a2e4befa956f"
> Content-Length: 0
>
> DEBUG | 20051206-181533.262 | c:\Test.exe | RESIP:TRANSACTION | 3660 |
> TimerQueue.cxx:85 |
> Adding timer: Timer K tid=8451c1677735d827 ms=5000
>
> =========== end of debug snippet ======================
>
> Hope someone can help. Thanks!
> Chee
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel