[asterisk-bugs] [Asterisk 0017652]: [patch] Add CHANNEL(checkhangup) function

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17652 
====================================================================== 
Reported By:                kobaz
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17652
Category:                   Channels/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-1860 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 276729 
Request Review:              
====================================================================== 
Date Submitted:             2010-07-15 11:46 CDT
Last Modified:              2010-07-19 16:15 CDT
====================================================================== 
Summary:                    [patch] Add CHANNEL(checkhangup) function
Description: 
Currently there's no good way to check if your channel is being hung up on
you from within AGI.

Sometimes you'll get responses from AGI like 'HANGUP200', but that's not
always the case when the channel is being ripped away.

Patch for trunk attached
====================================================================== 

---------------------------------------------------------------------- 
 (0124729) kobaz (reporter) - 2010-07-19 16:15
 https://issues.asterisk.org/view.php?id=17652#c124729 
---------------------------------------------------------------------- 
I really like having checkhangup in my own personal branch, but that would
indeed be an issue if some things don't set hangupcause.

Personally, I like the idea of having an 'official' way to check for
things via a function. Rather than having to rely on checking obscure
variables for obscure values.  This of course can be argued that the hangup
causes are documented in the headers and etc... but even if hangupcause was
set in all possible cases where it should be, it seems like it's a hacky
way to check. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-19 16:15 kobaz          Note Added: 0124729                          
======================================================================