[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:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15716
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for review
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-17 09:53 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
====================================================================== 

---------------------------------------------------------------------- 
 (0109115) mmichelson (administrator) - 2009-08-17 09:53
 https://issues.asterisk.org/view.php?id=15716#c109115 
---------------------------------------------------------------------- 
I'm a bit confused here. I'm having a hard time seeing why this is
necessary.

We have logic built in so that if we are getting no response to the INVITE
at all, we will stop retransmitting after a certain period. You'll see a
message like "Maximum retries exceeded on..." When that happens, the
channel should get hung up. If it is not, then there is some other bug that
should be handled a different way.

And of course, if we have gotten a response, the logic in the sip_hangup
function should cause a CANCEL to be sent out.

It would be helpful to see a console log to determine what is happening
here. I have no doubt that your patch has fixed the problem, but it
shouldn't be necessary since this is something that should be taken care of
already in the code. I'm thinking that there must have been a regression to
have caused this, and it would be great to figure out what that is and get
it fixed instead of adding new code to work around the broken code.

Also, sorry to have to do this, but I am so bogged down with things I'm
going to have to unassign this from myself. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-17 09:53 mmichelson     Note Added: 0109115                          
======================================================================