[asterisk-bugs] [Asterisk 0016824]: [patch] 603 Declined when call torn down

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16824 
====================================================================== 
Reported By:                tensai
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16824
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 246623 
Request Review:              
====================================================================== 
Date Submitted:             2010-02-12 21:10 CST
Last Modified:              2010-02-15 02:40 CST
====================================================================== 
Summary:                    [patch] 603 Declined when call torn down
Description: 
Per the discussion at
http://lists.digium.com/pipermail/asterisk-users/2010-January/243939.html a
consensus seems to have been reached that 603 Declined should be replaced
by 487 Request Terminated. Here is a patch to make that change. 
====================================================================== 

---------------------------------------------------------------------- 
 (0118070) oej (manager) - 2010-02-15 02:40
 https://issues.asterisk.org/view.php?id=16824#c118070 
---------------------------------------------------------------------- 
That wasn't the consensus really. If Asterisk is authorative for the
domain, we should use a 6xx error class, if not a 4xx error. This applies
to many error codes and we need some more work to be able to configure
whether we are authorative or not per domain. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-15 02:40 oej            Note Added: 0118070                          
======================================================================