[asterisk-bugs] [Asterisk 0015540]: [patch] chan_sip behaves like crazy if there is not route to destination

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15540 
====================================================================== 
Reported By:                nmav
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15540
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.25.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-21 03:55 CDT
Last Modified:              2009-09-04 04:38 CDT
====================================================================== 
Summary:                    [patch] chan_sip behaves like crazy if there is not
route to destination
Description: 
If the host asterisk is running has no routes to the registration server I
get continuous messages like below. In addition after ten minutes the
machine crashes due to no memory available (asterisk takes it all).

[Apr  1 04:10:39] WARNING[916]: chan_sip.c:1804 __sip_xmit: sip_xmit of
0x15cb44
 (len 403) to 192.168.240.34:5060 returned -2: Unknown error 101
[Apr  1 04:10:39] NOTICE[916]: chan_sip.c:8144 sip_reg_timeout:    --
Registrati
on for 'nmav2 at 192.168.240.34' timed out, trying again (Attempt
https://issues.asterisk.org/view.php?id=622)
[Apr  1 04:10:39] WARNING[916]: acl.c:548 ast_ouraddrfor: Cannot connect
REGISTER attempt 623 to nmav2 at 192.168.240.34
[Apr  1 04:10:39] WARNING[916]: chan_sip.c:1804 __sip_xmit: sip_xmit of
0x8f9f4c
 (len 403) to 192.168.240.34:5060 returned -2: Unknown error 101
[Apr  1 04:10:39] NOTICE[916]: chan_sip.c:8144 sip_reg_timeout:    --
Registrati
on for 'nmav1 at 192.168.240.34' timed out, trying again (Attempt
https://issues.asterisk.org/view.php?id=614)
[Apr  1 04:10:39] WARNING[916]: acl.c:548 ast_ouraddrfor: Cannot connect
REGISTER attempt 615 to nmav1 at 192.168.240.34


====================================================================== 

---------------------------------------------------------------------- 
 (0110223) oej (manager) - 2009-09-04 04:38
 https://issues.asterisk.org/view.php?id=15540#c110223 
---------------------------------------------------------------------- 
I question that part of the code. If we have one of the failure above, why
should we try again after one millisecond? That's seems wrong to me... This
requires some further digging to find out when and why that code came into
existance. There are SIP timers and stuff that handle that outside of this
function. We should not have a special case for REGISTER requests, that
messes up the hole excuse we have for transaction retransmit support. 

grrrrrr. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-04 04:38 oej            Note Added: 0110223                          
======================================================================