| Summary: | ASTERISK-05308: Read() falls through if ResponseTimeout() is reached but fails to land in 't' (timed out) | ||
| Reporter: | Timothy (icebrkr) | Labels: | |
| Date Opened: | 2005-10-18 09:13:11 | Date Closed: | 2011-06-07 14:10:23 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_read |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Read() exits after ResponseTimeout() and falls through to next priority. Shouldn't Read() land in 't'imeout if it's reacting on ResponseTimeout()? If this isn't a bug, please update the Wiki on how to handle Timeous with app_read | ||
| Comments: | By: BJ Weschke (bweschke) 2005-10-26 21:05:26 It's not really reacting on ResponseTimeout in the traditional sense of the word. It may use that value as a default if you didn't explicitly supply it with one, but the concept of timing out waiting for a string of digits in app_read is not the same as a ResponseTimeout waiting for digits to match an extension in the given context. You get no unique notification from app_read that it timed out while waiting for input. If you want to reach 't' after waiting the specified time for digits, you may want to look into the use of WaitExten instead of Read. By: Mark Spencer (markster) 2005-10-30 02:18:45.000-0600 This behavior is correct. | ||