[asterisk-bugs] [Asterisk 0014695]: [patch] Add Hangupcause to manager action Hangup

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14695 
====================================================================== 
Reported By:                mneuhauser
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14695
Category:                   Core/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 182952 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-18 11:33 CDT
Last Modified:              2009-03-31 19:30 CDT
====================================================================== 
Summary:                    [patch] Add Hangupcause to manager action Hangup
Description: 
Unlike the application counterpart, the 'Hangup' manager action does not
allow the hangupcause to be specified. The attached patch (for 1.4) fixes
this. I've named the new header 'Cause' to match the hangup manager event. 
====================================================================== 

---------------------------------------------------------------------- 
 (0102513) mmichelson (administrator) - 2009-03-31 19:30
 http://bugs.digium.com/view.php?id=14695#c102513 
---------------------------------------------------------------------- 
This is a great idea. Since this encompasses new functionality, this will
only go into Asterisk trunk, though, and not into 1.4 or any of the current
1.6.X branches.

You've done a great job here. You've followed the coding guidelines,
commented well, and everything is logically sound. The only change I'm
going to make is to change the NOTICE message you print to a WARNING
instead since it is pointing out a problem in the user's input.

I'll get this committed ASAP. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-31 19:30 mmichelson     Note Added: 0102513                          
======================================================================