[asterisk-bugs] [Asterisk 0014971]: Monitor in Asterisk does not record all calls and also recordings are not complete according to the complete actual duration

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14971 
====================================================================== 
Reported By:                destiny6628
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14971
Category:                   Resources/res_monitor
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Target Version:             1.4.27
Asterisk Version:           1.4.19 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-25 05:29 CDT
Last Modified:              2009-06-09 08:48 CDT
====================================================================== 
Summary:                    Monitor in Asterisk does not record all calls and
also recordings are not complete according to the complete actual duration
Description: 
e are using Monitor command for recording calls.

Issue which we are facing is are 

1)Recording does not even start happening even when Monitor command
issued.
2)Even if recording is started then also calls are half recorded.

Logs are attached both of same.

This is a bit critical issue as complete recordings are required for all
the Calls is mandatory
====================================================================== 

---------------------------------------------------------------------- 
 (0106157) lmadsen (administrator) - 2009-06-09 08:48
 https://issues.asterisk.org/view.php?id=14971#c106157 
---------------------------------------------------------------------- 
I'm seeing the two reporters mentioning Zaptel, and I'm curious if
upgrading to DAHDI would cause these issues to go away? Does this *only*
happen on hardware channels? (chan_zap?)

If that is the case, it could very well be the problem exists in chan_zap,
and upgrading to chan_dahdi may cause the problem to be resolved. Since
chan_zap is no longer maintained, but chan_dahdi is, I'd suggest you give
that a shot to see if resolves the issue.

Thanks!
Leif. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-09 08:48 lmadsen        Note Added: 0106157                          
======================================================================