[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-07-01 10:26 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0124156) dtryba (reporter) - 2010-07-01 10:26
 https://issues.asterisk.org/view.php?id=17547#c124156 
---------------------------------------------------------------------- 
Didn't see any stale nonce registers so far. All Forbidden messages are due
to expired registers. Summary/subject should be changed (or closing this
bug in favour of a new one about missing registers).

Asterisk clients just don't make any attempts to register:
register 11:11:30
register 11:13:15
invite   11:16:44 (response Forbidden from server)
register 11:16:47
register 11:18:32
register 11:20:17

It's very obvious a register attempt should have happened at 11:15:00
since the requested expires is 120s and the client makes a note to refresh
in 105s:

[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  0 [ 14]: SIP/2.0 200
OK
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  1 [ 91]: Via:
SIP/2.0/TCP
88.159.8.123:5060;branch=z9hG4bK45519b91;received=88.159.8.123;rport=37115
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  2 [ 56]: From:
<sip:officevoiptrunk at voip.pocos.nl>;tag=as654e4560
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  3 [ 54]: To:
<sip:officevoiptrunk at voip.pocos.nl>;tag=as6435c1ab
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  4 [ 51]: Call-ID:
6bb4064737243c9b23c372371340e514 at 127.0.1.1
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  5 [ 19]: CSeq: 1351
REGISTER
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  6 [ 30]: Server:
Asterisk PBX 1.6.2.6-1
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  7 [ 72]: Allow:
INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  8 [ 26]: Supported:
replaces, timer
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header  9 [ 12]: Expires: 120
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header 10 [ 63]: Contact:
<sip:voiptrunk at 88.159.8.123;transport=TCP>;expires=120
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header 11 [ 35]: Date: Wed, 30
Jun 2010 09:13:15 GMT
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header 12 [ 17]:
Content-Length: 0
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c:  Header 13 [  0]: 
[Jun 30 11:13:15] VERBOSE[18340] chan_sip.c: --- (13 headers 0 lines) ---
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c: Registration successful
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c: Cancelling timeout 2793039
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c: SIP Registry voip.pocos.nl:
refcount now 2
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c: SIP Registry voip.pocos.nl:
refcount now 1
[Jun 30 11:13:15] VERBOSE[18340] chan_sip.c: Scheduling destruction of SIP
dialog '6bb4064737243c9b23c372371340e514 at 127.0.1.1' in 32000 ms (Method:
REGISTER)
[Jun 30 11:13:15] NOTICE[18340] chan_sip.c: Outbound Registration: Expiry
for voip.pocos.nl is 120 sec (Scheduling reregistration in 105 s)
[Jun 30 11:13:15] DEBUG[18340] chan_sip.c: SIP Registry voip.pocos.nl:
refcount now 2

When the next register will happen is random, between 3m and 30m was
observed.

Things the 2 bad behaving clients have common:
-32bit Linux: 2.6.26-2-686/2.6.18-194.3.1.el5PAE
-no dahdi hardware, using res_timing_pthread.so/res_timing_dahdi.so

The correctly behaving 1.6.2.6 clients are running 64bit versions and have
Digium PRI cards. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-01 10:26 dtryba         Note Added: 0124156                          
======================================================================