Summary: | ASTERISK-13554: app_dial with the g flag doesn't continue on to the next priority | ||
Reporter: | David Van Ginneken (davevg) | Labels: | |
Date Opened: | 2009-02-10 08:57:37.000-0600 | Date Closed: | 2011-06-07 14:07:57 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_dial |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) Asterisk_Dialplan.txt ( 1) Asterisk_Log.txt | |
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. ****** ADDITIONAL INFORMATION ****** [Feb 9 16:39:11] DEBUG[10264] app_dial.c: Exiting with DIALSTATUS=CANCEL. [Feb 9 16:39:11] DEBUG[10264] pbx.c: Spawn extension (ngtoutdialer,s,6) exited non-zero on 'Local/s@ngtoutdialer-efce,2' [Feb 9 16:39:11] VERBOSE[10264] logger.c: == Spawn extension (ngtoutdialer, s, 6) exited non-zero on 'Local/s@ngtoutdialer-efce,2' [Feb 9 16:39:11] DEBUG[10264] channel.c: Soft-Hanging up channel 'Local/s@ngtoutdialer-efce,2' [Feb 9 16:39:11] DEBUG[10264] channel.c: Hanging up channel 'Local/s@ngtoutdialer-efce,2' | ||
Comments: | By: David Van Ginneken (davevg) 2009-02-10 13:53:02.000-0600 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. By: Mark Michelson (mmichelson) 2009-02-10 14:22:34.000-0600 Closing at Dave's request. |