[asterisk-users] why is nonce="584760da" used in sip packets?

[Watkins, Bradley]

You have on your hands a broken UA, since it is not responding to the
changing nonce value.

- Brad
 
________________________________

	From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Rizwan
Hisham
	Sent: Wednesday, August 15, 2007 7:52 AM
	To: Asterisk Users Mailing List - Non-Commercial Discussion
	Subject: Re: [asterisk-users] why is nonce="584760da" used in
sip packets?
	
	
	<--- Transmitting (NAT) to 208.120.167.146:80 --->
	SIP/2.0 401 Unauthorized 
	Via: SIP/2.0/UDP
208.120.167.146:80;branch=z9hG4bK722c974c;received=208.120.167.146 
	From: <sip:bernart48 at magnum.axvoice.com>;tag=as1acc7245
	To: <sip:bernart48 at magnum.axvoice.com>;tag=as1d329593
	Call-ID: 48f3a8b426c375a161dc1f4479bba956 at 127.0.0.1
	CSeq: 19710 REGISTER 
	User-Agent: Asterisk PBX
	Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE,
NOTIFY 
	Supported: replaces
	WWW-Authenticate: Digest algorithm=MD5, realm="asterisk",
nonce="4f90fab4", stale=true
	Content-Length: 0
	
	this stale=true field causes the asterisk server to display the
following NOTICE on the cli 
	
	NOTICE[8380]: chan_sip.c:8151 check_auth: Correct auth, but
based on stale nonce received from '<sip:bernart48 at magnum.axvoice.com
<mailto:sip:bernart48 at magnum.axvoice.com> >'
	
	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.