SPA3102 registration failure using UDP/works with TCP

[mcampbellsmith]

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

[nseto]

Please send the ethereal trace of the TCP and UDP registrations.  I will have dev look at this.  Thanks.

[mcampbellsmith]

Hi there,

Do you have an email address I can send the pcap traces to?

Thanks!

[nseto]

My username at cisco.com

[mcampbellsmith]

Thanks. Email Sent.

[danols951]

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.