[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 
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-08-18 23:26 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
====================================================================== 

---------------------------------------------------------------------- 
 (0109262) dant (reporter) - 2009-08-18 23:26
 https://issues.asterisk.org/view.php?id=15716#c109262 
---------------------------------------------------------------------- 
Sorry for not being too clear...

I'd not considered termination due to maximum retries, though this would
likely produce the same effect... the vector that I was targetting was when
a call setup was terminated prior to maximum retries being reached... i.e.
call a non-responding peer and hangup before receiving a response and
before having reached maximum retries...

I suspect that modifying retrans_pkt wouldn't correct the behaviour in
this situation as the dialog would be scheduled for destruction outside of
retrans_pkt and as such the packet will still be there and sched will still
be triggering __sip_autodestruct, but, I'll have a look and see if there's
somewhere else this could be put... I originally went with this approach as
the logic seemed to be that it would only actually kill off the dialog if a
CANCEL or BYE had been sent, whereas another valid final method is INVITE
if there has been no response as we shouldn't send a CANCEL in that
situation. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-18 23:26 dant           Note Added: 0109262                          
======================================================================