Ok looks like the token is not used at all in digest auth.  This is the first time I have seen a device send back something other than auth or auth-int.

/b

On Feb 14, 2010, at 11:09 PM, Mark Campbell-Smith wrote:

A little more testing.    I noticed that the Authorization field
differs when TCP or UDP:

UDP (fails)
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\"

TCP (works)
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\"

Is qop = 1fffcc9f valid in SIP?  Does a cnonce need to be included also?

FS sends qop=auth in the Unauthorized response.

Thanks