2010/6/2 Moloud Mousavi <[email protected]>: > Hi, > The Cnonce definition in RFC 3261 is confusing. This is what I found: > > cnonce = "cnonce" EQUAL cnonce-value > cnonce-value = nonce-value > > while a bit up an example shows the value of cnonce different than nonce: > > nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093", > uri="sip:[email protected]", > qop=auth, > nc=00000001, > cnonce="0a4f113b", > response="6629fae49393a05397450978507c4ef1",
Why do "you" think that cnonce and nonce are different? just because the different lenght in *your* example? the BNF for nonce-value field doesn't mandate a strict length for nonce-value, in fact it's just a queted string: nonce-value = quoted-string > I need to calculate the challenge response. I don’t know where to get this > cnonce from? Read RFC 2617. > One more thing: Why are there many names for the same parameter??? Like this > one: nonce-count = "nc" EQUAL nc-value Please, read RFC 2617 and 3261 before asking such questions. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications.
