[asterisk-bugs] [Asterisk 0012448]: Soft Hangup un called channel of Dial() returns NO ANSWER

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12448 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12448
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-15-2008 08:47 CDT
Last Modified:              04-15-2008 21:29 CDT
====================================================================== 
Summary:                    Soft Hangup un called channel of Dial() returns NO
ANSWER
Description: 
Dial from SIP/90133 to SIP/90086, creates child channel SIP/90086-008a9700
and sets it to Ringing state. If "soft hangup SIP/90086-008a9700" is
executed while it's still ringing, Dial() returns "NO ANSWER" in
DIALSTATUS. From current return values, CANCEL seams to be most reasonable,
but anything else should be ok too. NO ANSWER is least describing response
for this situation.


====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 04-15-08 21:29  
---------------------------------------------------------------------- 
Since this is not technically a bug, but rather a suggested change, it
needs to be discussed on the asterisk-dev list, not on the issue tracker. 
I am therefore suspending this issue.  Please send an email to the
asterisk-dev list, describing what you think Asterisk should do, and we can
reopen this issue in a week's time, following discussion as to what course
of action we should take.  However, I am uncomfortable with making a
behavior change such as this in 1.4, as this is not strictly a bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-15-08 21:29  Corydon76      Note Added: 0085533                          
======================================================================