<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <B>On Behalf Of </B>Rizwan
Hisham<BR><B>Sent:</B> Wednesday, August 15, 2007 7:52 AM<BR><B>To:</B>
Asterisk Users Mailing List - Non-Commercial Discussion<BR><B>Subject:</B> Re:
[asterisk-users] why is nonce="584760da" used in sip
packets?<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=Arial color=#0000ff size=2></FONT>
<DIV><BR>This causes the asterisk server to send another unauthorisation
response with an additional parameter stale in WWW-Authenticate section as
shown below <BR><BR><SPAN style="COLOR: rgb(0,153,0)"><--- Transmitting
(NAT) to <A href="http://208.120.167.146:80">208.120.167.146:80</A>
---></SPAN><BR style="COLOR: rgb(0,153,0)"><SPAN
style="COLOR: rgb(0,153,0)">SIP/2.0 401 Unauthorized </SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">Via: SIP/2.0/UDP
<A
href="http://208.120.167.146:80">208.120.167.146:80</A>;branch=z9hG4bK722c974c;received=<A
href="http://208.120.167.146">208.120.167.146 </A></SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">From: <<A
href="mailto:sip:bernart48@magnum.axvoice.com">sip:bernart48@magnum.axvoice.com</A>>;tag=as1acc7245</SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">To: <<A
href="mailto:sip:bernart48@magnum.axvoice.com">sip:bernart48@magnum.axvoice.com</A>>;tag=as1d329593</SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">Call-ID: <A
href="mailto:48f3a8b426c375a161dc1f4479bba956@127.0.0.1">48f3a8b426c375a161dc1f4479bba956@127.0.0.1</A></SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">CSeq: 19710
REGISTER</SPAN> <BR style="COLOR: rgb(0,153,0)"><SPAN
style="COLOR: rgb(0,153,0)">User-Agent: Asterisk PBX</SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">Allow: INVITE,
ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY </SPAN><BR
style="COLOR: rgb(0,153,0)"><SPAN style="COLOR: rgb(0,153,0)">Supported:
replaces</SPAN><BR style="COLOR: rgb(0,153,0)"><SPAN
style="COLOR: rgb(0,153,0)">WWW-Authenticate: Digest algorithm=MD5,
realm="asterisk", <SPAN style="COLOR: rgb(204,0,0)">nonce="4f90fab4",
stale=true</SPAN></SPAN><BR style="COLOR: rgb(0,153,0)"><SPAN
style="COLOR: rgb(0,153,0)">Content-Length: 0</SPAN><BR><BR>this stale=true
field causes the asterisk server to display the following NOTICE on the cli
<BR><BR><SPAN style="COLOR: rgb(0,153,0)">NOTICE[8380]: chan_sip.c:8151
check_auth: Correct auth, but based on stale nonce received from '<<A
href="mailto:sip:bernart48@magnum.axvoice.com">sip:bernart48@magnum.axvoice.com
</A>>'</SPAN><BR style="COLOR: rgb(0,153,0)"><BR>and this will continue
happening unless the next register request uses the nonce field recieved in
latest unauthorisation response from server, and untill then the user agent
will not be able to register with the server. This will cause problems in our
services. <BR><BR><SPAN class=853310312-15082007><FONT face=Arial
color=#0000ff size=2> </FONT></SPAN><SPAN
class=853310312-15082007> </SPAN></DIV></BLOCKQUOTE></BODY></HTML>