[asterisk-bugs] [Asterisk 0009785]: [patch] Add 'e' extension to handle application errors

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9785 
====================================================================== 
Reported By:                mnicholson
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9785
Category:                   Core/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 65675 
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             05-23-2007 14:10 CDT
Last Modified:              10-03-2007 15:03 CDT
====================================================================== 
Summary:                    [patch] Add 'e' extension to handle application
errors
Description: 
Currently when an application encounters an error asterisk hangs up the
channel.  This patch adds a special 'e' extension (like the 'i' extension)
to gracefully handle these errors instead of hanging up the channel.

This patch defines three new macros: AST_PBX_HANGUP (-1), AST_PBX_OK (0),
and AST_PBX_ERROR (1).  If an application returns AST_PBX_ERROR then the
'e' extension is triggered.

If an application executing on the 'e' exten encounters an error, the call
is terminated similar to how errors are handled now.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 10-03-07 15:03  
---------------------------------------------------------------------- 
I would suggest just using the RaiseException app (or the underlying public
function that I put in my code:  pbx_builtin_setexception). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-03-07 15:03  Corydon76      Note Added: 0071414                          
======================================================================