| Summary: | ASTERISK-02978: autofallthrough is incompatible with IVR menus; should default to "no" | ||
| Reporter: | Kevin P. Fleming (kpfleming) | Labels: | |
| Date Opened: | 2004-12-13 12:49:01.000-0600 | Date Closed: | 2011-06-07 14:10:46 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | The CVS HEAD extensions.conf.sample has "autofallthrough=yes", and strongly suggests leaving it that way. However, most of the examples of doing IVR menus with Asterisk use fallthrough with ResponseTimeout to allow the use to select a menu option (extension). With autofallthrough set to yes, this no longer works, Asterisk hangs up the channel or reports busy. If autofallthrough is set to yes, IVR menus have to be built using WaitExten. If this is going to be the default, then this will need to be documented for users, especially those upgrading from older releases. | ||
| Comments: | By: Tilghman Lesher (tilghman) 2004-12-13 12:59:07.000-0600 I agree here. Whatever happened to the Principle of Least Surprise? By: Brian West (bkw918) 2004-12-13 13:16:33.000-0600 How about a patch for the docs eh? bkw By: Mark Spencer (markster) 2004-12-13 14:26:07.000-0600 The example configurations are, to the best of my knowledge, already updated with WaitExten. "autofallthrough" is only the default in new configuration files and so obviously it won't affect anyone already running an Asterisk setup who upgrades. All *new* installs should use WaitExten. If you feel there are errors in extensions.conf where WaitExten is not used and should be, please open a new report with the specific example or examples to be modified. | ||