[asterisk-bugs] [Asterisk 0013764]: 302 Redirect (forward no answer) to bad extension causes channel to be left up (Ringing)
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Nov 26 13:57:17 CST 2008
The following issue has been RESOLVED.
======================================================================
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: resolved
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:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2008-10-22 10:35 CDT
Last Modified: 2008-11-26 13:57 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2008-11-26 13:57 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list