[asterisk-bugs] [Asterisk 0014279]: [patch] Pressing only # when app_read is playing multiple prompts does not act as expected

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14279 
====================================================================== 
Reported By:                Marquis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14279
Category:                   Applications/app_read
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 169329 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-19 13:10 CST
Last Modified:              2009-01-19 13:14 CST
====================================================================== 
Summary:                    [patch] Pressing only # when app_read is playing
multiple prompts does not act as expected
Description: 
When multiple ampersand-delimited prompts are passed to app_read, pressing
# (without pressing other DTMF keys) merely cycles through the prompts
until it reaches the last one.  Then it will *finally* skip that prompt and
return to the dialplan.
====================================================================== 

---------------------------------------------------------------------- 
 (0098135) Marquis (reporter) - 2009-01-19 13:14
 http://bugs.digium.com/view.php?id=14279#c98135 
---------------------------------------------------------------------- 
The attached patch is a proposed solution.  It doesn't include any
(possible) changes to other calls of ast_readstring that may be required to
avoid breakage.

If this way of going about it is ok, I'll create a new patch with all the
other uses of it changed if necessary.

A cursory glance through the source seemed to me that many existing uses
would not have to be altered, though some would. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-19 13:14 Marquis        Note Added: 0098135                          
======================================================================