[asterisk-bugs] [Asterisk 0011657]: app_followme broken in /trunk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11657 
====================================================================== 
Reported By:                davevg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11657
Category:                   Applications/app_followme
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 95313 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-31-2007 12:05 CST
Last Modified:              01-07-2008 11:46 CST
====================================================================== 
Summary:                    app_followme broken in /trunk
Description: 
In /trunk app_followme does not work, 1.4 works fine.  When it dials out to
the followme numbers it never detects the answer on the lines it is
connecting to.  I have traced it back to winner = ast_waitfor_n(watchers,
pos, &to);  It always returns the 1st element in the array.  With this
f->frametype is 4 and f->subclass is 2.  If you make the caller channel the
last element, it will connect and playback the prompts correctly, but not
see any changes on the caller channel. Ie. If you hang up the caller
channel, it continues the call flow.
====================================================================== 

---------------------------------------------------------------------- 
 davevg - 01-07-08 11:46  
---------------------------------------------------------------------- 
It does not fix it, It now processes frames on both channels, which it
didn't before, but it is not detecting dtmf on the outbound channel. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-07-08 11:46  davevg         Note Added: 0076421                          
======================================================================