[asterisk-bugs] [Asterisk 0012462]: [patch] Value of AGISTATUS is set to SUCCESS even though the agi program could not be executed

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Apr 16 20:53:28 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12462 
====================================================================== 
Reported By:                fmueller
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12462
Category:                   Resources/res_agi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 114184 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-16-2008 17:04 CDT
Last Modified:              04-16-2008 20:53 CDT
====================================================================== 
Summary:                    [patch] Value of AGISTATUS is set to SUCCESS even
though the agi program could not be executed
Description: 
This is the context:

[default]
exten => 69,1,Answer()
exten => 69,2,AGI(this-does-not-exist)
exten => 69,3,Noop(${AGISTATUS})
exten => 69,4,Hangup()

The called AGI-program does not exist so I expect AGISTATUS to be set to
FAILURE. But it is set to SUCCESS.

*CLI>     -- Executing [69 at default:1] Answer("SIP/111-081fb288", "") in
new stack
    -- Executing [69 at default:2] AGI("SIP/111-081fb288",
"this-does-not-exist") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/this-does-not-exist
AGI Tx >> agi_request: this-does-not-exist
AGI Tx >> agi_channel: SIP/111-081fb288
AGI Tx >> agi_language: en
AGI Tx >> agi_type: SIP
AGI Tx >> agi_uniqueid: 1208383260.0
AGI Tx >> agi_callerid: 111
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 0
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 0
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: 69
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: default
AGI Tx >> agi_extension: 69
AGI Tx >> agi_priority: 2
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode: 
AGI Tx >> 
AGI Rx << verbose "Failed to execute
'/var/lib/asterisk/agi-bin/this-does-not-exist': No such file or directory"
2
  ==  this-does-not-exist: Failed to execute
'/var/lib/asterisk/agi-bin/this-does-not-exist': No such file or directory
AGI Tx >> 200 result=1
    -- AGI Script this-does-not-exist completed, returning 0
    -- Executing [69 at default:3] NoOp("SIP/111-081fb288", "SUCCESS") in new
stack
    -- Executing [69 at default:4] Hangup("SIP/111-081fb288", "") in new
stack
  == Spawn extension (default, 69, 4) exited non-zero on
'SIP/111-081fb288'

*CLI> 

Thanks for your feedback.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 04-16-08 20:53  
---------------------------------------------------------------------- 
The main reason I wouldn't do it that way is that there are other reasons
for why an execute might fail, other than the file not existing, which is
all that the trunk version does.  The file might not be in an executable
format, for example.  And there's no easy way to know that, other than
attempting to execute it and failing. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-16-08 20:53  Corydon76      Note Added: 0085591                          
======================================================================




More information about the asterisk-bugs mailing list