[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:                   major
Priority:                   normal
Status:                     feedback
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-05-20 06:33 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
====================================================================== 

---------------------------------------------------------------------- 
 (0105062) destiny6628 (reporter) - 2009-05-20 06:33
 https://issues.asterisk.org/view.php?id=14971#c105062 
---------------------------------------------------------------------- 
I am extremely sorry for the delay in giving feedback.
Yes, correct we are using Local Channel for dialing but after going
through your feedback we stopped using Local Channel and instead have
started dialing directly on ZAP.

After dialing directly on ZAP as well,we are facing recording issue.

ACTUAL Call was for longer duration but recording we had for only 6 sec.

I am attaching the logs below which will clearly shows same and also
please fine the attached recording.

[May 20 11:28:16] VERBOSE[994] logger.c:     -- Executing [143 at default:1]
NoOp("Zap/7-1", "9119999100816-66220300-20090520-112805") in new stack
[May 20 11:28:16] VERBOSE[994] logger.c:     -- Executing [143 at default:2]
Monitor("Zap/7-1",
"wav|/var/spool/asterisk/monitor/ORIG/20090520/9119999100816-66220300-20090520-112805")
in new stack
[May 20 11:28:16] VERBOSE[994] logger.c:     -- Executing [143 at default:3]
Dial("Zap/7-1", "SIP/143") in new stack
[May 20 11:28:16] VERBOSE[994] logger.c:     -- Called 143
[May 20 11:28:16] VERBOSE[994] logger.c:     -- SIP/143-0927c5b0 is
ringing
[May 20 11:28:19] VERBOSE[994] logger.c:     -- SIP/143-0927c5b0 answered
Zap/7-1
[May 20 11:48:13] VERBOSE[994] logger.c:   == Spawn extension (default,
143, 3) exited non-zero on 'Zap/7-1' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-20 06:33 destiny6628    Note Added: 0105062                          
======================================================================