[asterisk-bugs] [Asterisk 0010989]: Add fractional timeouts and default timeout variable values to Read

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10989 
====================================================================== 
Reported By:                michael-fig
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10989
Category:                   Applications/app_read
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.12.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-15-2007 20:47 CDT
Last Modified:              10-16-2007 09:17 CDT
====================================================================== 
Summary:                    Add fractional timeouts and default timeout variable
values to Read
Description: 
The Read application currently has no way to distinguish between when the
user pressed '#' (the variable is set to a zero-length string), or if the
Read application times out.

The attached patch adds a new option 'd' to Read that allows the dial plan
to set the variable, and leave its value unchanged on timeout.

The fractional read timeout is used to allow playing a single message
while polling for a key, then immediately advancing to a second message. 
This is useful when the messages are built out of fragments instead of one
big message that can be provided as the second argument to Read.
====================================================================== 

---------------------------------------------------------------------- 
 jsmith - 10-16-07 09:17  
---------------------------------------------------------------------- 
Let me throw out an idea here... why not simply have the application set a
channel variable named READSTATUS, as many of the other applications
already save their status to a channel variable.  This gives the user
greater flexibility, and doesn't require another option to the
application.

Thoughts? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-16-07 09:17  jsmith         Note Added: 0072083                          
======================================================================