[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:                     acknowledged
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-26 01:58 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
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015233 MixMonitor stops after transfer from queue
====================================================================== 

---------------------------------------------------------------------- 
 (0107014) motto (reporter) - 2009-06-26 01:58
 https://issues.asterisk.org/view.php?id=14971#c107014 
---------------------------------------------------------------------- 
I also noticed after moving from Zap to DAHDI my server started crushing
almost each day.

kernel: Uhhuh. NMI received for unknown reason 25 on CPU 0.
kernel: Do you have a strange power saving mode enabled?
kernel: Dazed and confused, but trying to continue
kernel: Clocksource tsc unstable (delta = 2729277052 ns)
kernel: Time: jiffies clocksource has been installed.
syslogd 1.4.2: restart. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-26 01:58 motto          Note Added: 0107014                          
======================================================================