[asterisk-bugs] [Asterisk 0015716]: [patch] chan_sip fails to destroy channels in INVITE when no response received

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15716 
====================================================================== 
Reported By:                dant
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15716
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                        
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-13 19:15 CDT
Last Modified:              2009-09-28 09:51 CDT
====================================================================== 
Summary:                    [patch] chan_sip fails to destroy channels in INVITE
when no response received
Description: 
In the event that a call is made to a device that is not responding INVITE
packets are reliably transmitted to the device, if the call is hungup the
channel lives forever. 

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015627 [patch] Asterisk runs out of sockets
====================================================================== 

---------------------------------------------------------------------- 
 (0111432) kresike (reporter) - 2009-09-28 09:51
 https://issues.asterisk.org/view.php?id=15716#c111432 
---------------------------------------------------------------------- 
I have also noticed this problem after upgrading to * version 1.4.26.
I tend to agree with mmichelson's second solution, (no offence dant).
Is there any progress on that ? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-28 09:51 kresike        Note Added: 0111432                          
======================================================================