[asterisk-bugs] [Asterisk 0013909]: Recordings with Mixmonitor still ou of sync

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13909 
====================================================================== 
Reported By:                edugs15
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13909
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-11-17 06:34 CST
Last Modified:              2009-01-26 15:41 CST
====================================================================== 
Summary:                    Recordings with Mixmonitor still ou of sync
Description: 
Recordings wirh Mixmonitor are still out of sync, with Asterisk 1.4.22 or
Asterisk 1.4.23-rc1.

This problem is always happening, no matter incoming or outgoing calls, no
matter short or long calls, no matter using chanspy or no.

One leg of the call is delayed.


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

---------------------------------------------------------------------- 
 (0098794) file (administrator) - 2009-01-26 15:41
 http://bugs.digium.com/view.php?id=13909#c98794 
---------------------------------------------------------------------- 
edugs15: I see you are using a channel driver that is not part of the
official tree. I need you to confirm this issue *without* using it. It may
be the way that channel driver sends frames into the core that is causing
this issue to creep up. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-26 15:41 file           Note Added: 0098794                          
======================================================================