[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 10:50 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0095547) davidw (reporter) - 2008-11-26 10:50
 http://bugs.digium.com/view.php?id=13764#c95547 
---------------------------------------------------------------------- 
Looks OK now, although I only know how to push it down the branch that was
causing our problem.

I tried with the redirect valid and answered, and note that almost no PBX
data appeared in the final outgoing channel (optimised out local channel) -
normally you get a pseuod application for the other side of a bridge.  I
don't know if this is considered a problem:

 --   PBX   --
        Context: internal
      Extension: 
       Priority: 1
     Call Group: 0
   Pickup Group: 0
    Application: (N/A)
           Data: (None)
    Blocking in: ast_waitfor_nandfds
      Variables: 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-26 10:50 davidw         Note Added: 0095547                          
======================================================================