[asterisk-bugs] [Asterisk 0013745]: Recordings out of sync when using chanspy

Fri Nov 21 15:23:37 CST 2008

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13745 
====================================================================== 
Reported By:                geoffs
Assigned To:                bweschke
====================================================================== 
Project:                    Asterisk
Issue ID:                   13745
Category:                   Applications/app_mixmonitor
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-20 09:31 CDT
Last Modified:              2008-11-21 15:23 CST
====================================================================== 
Summary:                    Recordings out of sync when using chanspy
Description: 
Inbound and outbound tracks will get out of sync by several seconds when a
call is monitored using chanspy.  
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012837 [patch] Chanspy audio is delayed or lost
====================================================================== 

---------------------------------------------------------------------- 
 (0095302) martins (reporter) - 2008-11-21 15:23
 http://bugs.digium.com/view.php?id=13745#c95302 
---------------------------------------------------------------------- 
Check out http://bugs.digium.com/view.php?id=11945 too, folks, Geoffs saw
the sync issue when upgrading from 1.4.17, and 11945 saw the issue appear
in 1.4.18 but it was 'fixed' -- could this be that 11945 has regressed? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-21 15:23 martins        Note Added: 0095302                          
======================================================================