[asterisk-bugs] [Asterisk 0012498]: ChanSpy doesn't correctly move to the next channel when * is pressed

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12498 
====================================================================== 
Reported By:                jsmith
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12498
Category:                   Applications/app_chanspy
Reproducibility:            always
Severity:                   minor
Priority:                   high
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 114551 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-22-2008 16:52 CDT
Last Modified:              04-23-2008 14:03 CDT
====================================================================== 
Summary:                    ChanSpy doesn't correctly move to the next channel
when * is pressed
Description: 
According to the ChanSpy documentation, when the spying caller presses the
* key, ChanSpy should stop spying on the current channel and move to the
next channel in the list.  In my testing, ChanSpy doesn't do this.  It
seems to get stuck on one channel and won't continue on to any other
channels.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012497 [patch] ChanSpy and ExtenSpy applicatio...
====================================================================== 

---------------------------------------------------------------------- 
 jsmith - 04-23-08 14:03  
---------------------------------------------------------------------- 
I'm attaching a patch that fixes this problem.  The elimination of the line
that sets waitms back to 5000 is a tad bit worrysome, but I can't find any
reason it was being set to 5000 in the first place.

Oh, and my patch is probably a bit verbose (just to explain what I'm
doing)... I'm not sure if the comments need to make their way into the
Asterisk code, or if this could be a simple patch that deletes the two
lines in question. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-23-08 14:03  jsmith         Note Added: 0085905                          
======================================================================