<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 02/07/2012 01:07 PM, Sammy Govind wrote:
<blockquote
cite="mid:CAJUJwtgy0f4b0LiEVg-v3MQ3M1=uUaceErHCD288O-+CLO_jLg@mail.gmail.com"
type="cite">Hello,
<div><br>
</div>
<div>I've been managing multiple call centres, almost all of them
having their calls recorded one way or other. Even in PBX
environments with MixMonitor and call recordings I haven't came
across the situation where I discovered that I can't chanspy a
call because its recorded !</div>
<div>Which version of asterisk you are using ! can you paste the
CLI logs which show a complete call with a failed attempt to
Chanspy ?</div>
</blockquote>
<br>
Using Asterisk 1.6.2.22.<br>
<br>
The fact that ChanSpy can not be used with MixMonitor is something I
read on the wiki :<br>
<br>
<h3>Attention</h3>
<ul>
<li> Up to and including Asterisk 1.4.17 ChanSpy can cause a <strong>crash/segfault</strong>
if used together with <a title="Asterisk cmd Monitor"
href="http://www.voip-info.org/wiki/view/Asterisk+cmd+Monitor">Monitor</a>
or <a title="MixMonitor"
href="http://www.voip-info.org/wiki/view/MixMonitor">MixMonitor</a>
at the same time. 1.4.18 is supposed to attack this issue by
using "audiohooks" that replaces the current ChanSpy approach.</li>
</ul>
<br>
</body>
</html>