[asterisk-bugs] [Asterisk 0013764]: 302 Redirect (forward no answer) to bad extension causes channel to be left up (Ringing)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13764 
====================================================================== 
Reported By:                davidw
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13764
Category:                   Applications/app_dial
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-22 10:35 CDT
Last Modified:              2008-11-26 09:32 CST
====================================================================== 
Summary:                    302 Redirect (forward no answer)  to bad extension
causes channel to be left up (Ringing)
Description: 
When testing something, we accidentally used a phone that had been
configured to call forward no-answer to a bad extension.  It took us a
while to realise, so we made several calls.  Subsequent core/sip show
channels show that all of these attempts are still ringing on the attempted
correct number, even though the SIP ones show the ACK to the 302 as the
last thing sent.
====================================================================== 

---------------------------------------------------------------------- 
 (0095541) putnopvut (administrator) - 2008-11-26 09:32
 http://bugs.digium.com/view.php?id=13764#c95541 
---------------------------------------------------------------------- 
Ah I see. I pretty much solved the opposite problem that you have. In my
case, the Local channel was being created properly, but ast_call was
failing. In that case, the original destination was hung up, but not the
newly created Local channel.

It seems that now the problem is that if the Local channel is not created
properly, then the original destination is not hung up properly. I'm going
to take a look at chan_local.c to see if I can spot an easy way to make
local_request fail so that I can get my test case correct. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-26 09:32 putnopvut      Note Added: 0095541                          
======================================================================