[asterisk-bugs] [Asterisk 0014450]: app_dial with the g flag doesn't continue on to the next priority

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14450 
====================================================================== 
Reported By:                davevg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14450
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-10 08:57 CST
Last Modified:              2009-02-10 13:53 CST
====================================================================== 
Summary:                    app_dial with the g flag doesn't continue on to the
next priority
Description: 
Asterisk 1.4.23.1, When dialing through local channels (for failover) we
have seen some cases where it does not continue on in the dialplan. 
Asterisk Verbose/Debug logs are attached and the dialplan it is going
through.  (This is just dialing an internal server for load testing, in
production the failover peer will be different)

I added the g recently to see if it would force it to continue when it
gets this error, previously only had the timeout flag.
====================================================================== 

---------------------------------------------------------------------- 
 (0099834) davevg (reporter) - 2009-02-10 13:53
 http://bugs.digium.com/view.php?id=14450#c99834 
---------------------------------------------------------------------- 
Sorry this can be closed.  I'm being dumb.  The originate command that
initiated the local channel had a timeout of 60 seconds which is the same
as the timeout of the 1st dial.  So it never had a chance to go onto the
next priority. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-10 13:53 davevg         Note Added: 0099834                          
======================================================================