[asterisk-bugs] [Asterisk 0012122]: Why Asterisk replies with "486 Busy Here" if it receives a "603 Decline"?

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12122 
====================================================================== 
Reported By:                ibc
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   12122
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 101278 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             03-03-2008 06:13 CST
Last Modified:              03-05-2008 11:49 CST
====================================================================== 
Summary:                    Why Asterisk replies with "486 Busy Here" if it
receives a "603 Decline"?
Description: 
If Asterisk calls a phone and receives a "603 Decline" from it, it replies
a "486 Busy Here" to the caller, why?

It makes more sense to reply with a "480 Temporary Unavailable".
Also there is a draft about this issue to propose a new response code:
  441: Decline
(instead of a global "603: Decline"):
  http://tools.ietf.org/html/draft-worley-6xx-considered-harmful

I've tryed and in version 1.4.15, Asterisk replies with "403 Forbidden" if
it receives a "603 Decline" from a phone. Afortunatelly this terrible error
seems to be "semi"-solved in later versions ;)
====================================================================== 

---------------------------------------------------------------------- 
 file - 03-05-08 11:49  
---------------------------------------------------------------------- 
This is a dialplan configuration issue. It is falling through and
signalling back busy, as that is what app_dial returns in DIALSTATUS. If
you want to pass back a more accurate cause use the Hangup application with
a specific cause code. To get the cause code returned by the dial device
use ${HANGUPCAUSE}. If you want to see what the values map to it is
documented above hangup_cause2sip. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-05-08 11:49  file           Note Added: 0083459                          
======================================================================