[asterisk-bugs] [Asterisk 0018565]: ChanSpy leaves channel in Up state behind, warnings

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18565 
====================================================================== 
Reported By:                kkm
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18565
Category:                   Applications/app_chanspy
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.1.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-12-31 00:38 CST
Last Modified:              2010-12-31 00:53 CST
====================================================================== 
Summary:                    ChanSpy leaves channel in Up state behind, warnings
Description: 
ChanSpy leaves a channel behind after every time the spying phone hangs up,
provided it has spied on at least one conversation.

pbx6*CLI> core show channels
Channel              Location             State   Application(Data)
SIP/250-00000006     s at app-chanspy:4      Up      ChanSpy(SIP/,s)
SIP/250-0000000d     s at app-chanspy:4      Up      ChanSpy(SIP/,s)
2 active channels
2 active calls
====================================================================== 

---------------------------------------------------------------------- 
 (0130070) kkm (reporter) - 2010-12-31 00:53
 https://issues.asterisk.org/view.php?id=18565#c130070 
---------------------------------------------------------------------- 
Addendum. That happens always on one particular trunk. This is a private
trunk to one of our customers over a VPN, otherwise nothing special. Worst
of all, I cannot reproduce the problem with an exact copy of that trunk and
a lab copy of customer's PBX (Avaya IPO). But on the real trunk it happens
every single time. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-31 00:53 kkm            Note Added: 0130070                          
======================================================================