[asterisk-bugs] [Asterisk 0017547]: REGISTER attempts with stale nonce

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17547 
====================================================================== 
Reported By:                dtryba
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17547
Category:                   Channels/chan_sip/Registration
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.7 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-23 05:29 CDT
Last Modified:              2010-06-25 11:43 CDT
====================================================================== 
Summary:                    REGISTER attempts with stale nonce
Description: 
Reregistration fails, resulting in new calls getting a 403 Forbidden.
Problem gets solved by issuing "sip reload" on the client. 

This issue occurs on a 1.6.2.6 (tcp) and a 1.6.2.7 (udp) asterisk client
connection to a 1.6.2.6 asterisk server.

tcpdump/sip debug is from the 1.6.2.6 client, still waiting for the
1.6.2.7 to fail.

Don't see anything related to this in the 1.6.2.9 Changelog.
====================================================================== 

---------------------------------------------------------------------- 
 (0123896) dtryba (reporter) - 2010-06-25 11:43
 https://issues.asterisk.org/view.php?id=17547#c123896 
---------------------------------------------------------------------- 
There is no log from the other side. This bug report contains 2 completely
different causes for call rejections. The only common factor is that the
server had it's registration from these peers expired.

The Forbidden is completely correct IMHO since the client has gone away
(registration expired/failed), the only usefull stuff logged by the server
is:
[Jun 25 13:50:29] VERBOSE[24242] chan_sip.c: No matching peer for
'0402938661' from '88.159.8.123:37115'
[Jun 25 13:50:29] NOTICE[24242] chan_sip.c: Failed to authenticate device
"0402938661" <sip:0402938661 at 88.159.8.123>;tag=as0975824e

This problem only appeared after upgrading from 1.4 to 1.6.2. All 1.4
clients are running just fine and only 2 of the 1.6.2 misbehave (so far).

According to the RFC a 403 means the receiver should not retry. One could
argue that the server might sent a 401 instead since in the past a peer was
registered at this ip/port pair. And after a successful registration this
ip/port pair is still used. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-25 11:43 dtryba         Note Added: 0123896                          
======================================================================