[Asterisk-bugs] [Asterisk 0010195]: ChanSpy doesn't work fine for Zap channels from 1 to 9 however works fine for zap channels > 9

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10195 
====================================================================== 
Reported By:                galeras
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   10195
Category:                   Applications/app_chanspy
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            1.2.20  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             07-12-2007 16:23 CDT
Last Modified:              07-13-2007 08:37 CDT
====================================================================== 
Summary:                    ChanSpy doesn't work fine for Zap channels from 1 to
9 however works fine for zap channels > 9
Description: 
Chanspy is not working properly when try to monitor one-digit channel like
zap/3 by dialing the digit followed by #, however it works fine for 2 and 3
digits channels like zap/123

my extensions.conf looks like:

exten => s,1,ChanSpy(Zap/1)

====================================================================== 

---------------------------------------------------------------------- 
 file - 07-13-07 08:37  
---------------------------------------------------------------------- 
This is a configuration issue. The Zap/1 acts a prefix, so only channels
starting with Zap/1 will be searched. If you enter 23 it will search for
Zap/123. The solution is to use a prefix of Zap/ 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-13-07 08:37  file           Status                   new => resolved     
07-13-07 08:37  file           Resolution               open => no change
required
07-13-07 08:37  file           Assigned To               => file            
07-13-07 08:37  file           Note Added: 0067341                          
======================================================================