02-14-2010 09:18 PM - edited 03-21-2019 09:23 AM
Hi!
I'm having problems where the device fails registration using UDP but works with TCP. The response from the server is FORBIDDEN when I use UDP.
I am only changing the transport, so I know the password is correct.
The difference I see is that the Authorization messages are different between the two:
For UDP (fails):
From server to SPA3102
SIP/2.0 401 Unauthorized
Digest realm=\"mydns.dyndns.org\", nonce=\"e5f119c6-19e9-11df-bd09-773b7a755f78\", algorithm=MD5, qop=\"auth\"
From SPA3102 to Server:
REGISTER sip:mydns.dyndns.org:5060 SIP/2.0
Digest username=\"2010\", realm=\"mydns.dyndns.org\", nonce=\"e5f119c6-19e9-11df-bd09-773b7a755f78\", uri=\"sip:mydns.dyndns.org:5060\", response=\"e37be3e49c159d4f98e8bd04b36f2bd7\", algorithm=MD5, qop=\"1fffcc9f\"
Then Forbidden is received
For TCP
From server to SPA3102
SIP/2.0 401 Unauthorized
Digest realm=\"mydns.dyndns.org\", nonce=\"5da673bc-19ea-11df-bd0c-773b7a755f78\", algorithm=MD5, qop=\"auth\"
From SPA3102 to Server:
REGISTER sip:mydns.dyndns.org:5060 SIP/2.0
Digest username=\"2010\",realm=\"mydns.dyndns.org\",nonce=\"5d9e75c2-19ea-11df-bd0b-773b7a755f78\",uri=\"sip:mydns.dyndns.org:5060\",algorithm=MD5,response=\"45ba55d3fbafcbf2bc2aa6418656ecc2\",qop=auth,nc=00000001,cnonce=\"3a650454\"
Thenk OK is received
I'm not sure how authentication works, but
1. Is qop = 1fffcc9f valid in SIP, as seen in the UDP REGISTER message?
2. Does a cnonce need to be included if qop is included? (According to RFC 2617 CNONCE MUST be specified if a qop directive is sent.)
Any other idea why this would be failing?
Thanks
02-17-2010 03:19 PM
Please send the ethereal trace of the TCP and UDP registrations. I will have dev look at this. Thanks.
02-17-2010 03:36 PM
Hi there,
Do you have an email address I can send the pcap traces to?
Thanks!
02-17-2010 03:37 PM
My username at cisco.com
02-17-2010 03:58 PM
Thanks. Email Sent.
02-04-2012 12:57 AM
I just registered to enquire about the progress of this bug? I have spent about 4 hours attempting to resolve this and finally ended up on this thread, where using TCP instead of UDP fixed the: SIP/2.0 401 Unauthorized issue.
Daniel Sokolowski
Thank you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: