[asterisk-bugs] [Asterisk 0012461]: app_chanspy group broken in 1.4.19

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12461 
====================================================================== 
Reported By:                stever28
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12461
Category:                   Applications/app_chanspy
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-16-2008 16:52 CDT
Last Modified:              04-17-2008 12:06 CDT
====================================================================== 
Summary:                    app_chanspy group broken in 1.4.19
Description: 
CentOS 4.4, Asterisk 1.4.19, Zaptel 1.4.10, libpri 1.4.3, asterisk-addons
1.4.6.
Since I upgraded from Asterisk 1.4.18.1 to 1.4.19 an active call with
spygroup=2000 cannot be spied on with the dialplan as below, worked fine on
1.4.18.1.  To try and prove chanspy is working at all, I have tried 'exten
=> 596,n,ChanSpy(|b)', this works but spies on all active calls which is
not what is required when using spygroup.  I've recompiled 1.4.19 with
app_chanspy.c from 1.4.18.1 and I can now spy on active calls with
spygroup=2000, I can step through active calls with * and new calls with
spygroup=2000 become available. The dialplan has not changed between
asterisk versions.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 04-17-08 12:06  
---------------------------------------------------------------------- 
Okay, I found the source of the problem, and that is that part of the
changes that were meant to prevent crashes involved setting a pointer to
NULL. Setting this to NULL essentially made iterating through the list of
channels useless because instead of moving on to the next channel, we would
always get the first channel in the list. I'll have a fix for this soon. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-17-08 12:06  putnopvut      Note Added: 0085643                          
======================================================================