Summary:	ASTERISK-05879: MixMonitor outputing recording of zero file size
Reporter:	vortex_0_o (vortex_0_o)	Labels:
Date Opened:	2005-12-21 06:29:38.000-0600	Date Closed:	2006-02-13 21:38:02.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	- recording of zero file size is produced - only occurs when bridged option is specified - occurs in approx 4-5% of calls show version files app_mixmonitor.c Revision 7221 example: ... exten => _0[1-9].,4,MixMonitor(${CALLFILE}.gsm|bv(0)V(0)) ... exten => _0[1-9].,8,Dial(SIP/44${EXTEN:1}@somwehere)
Comments:	By: BJ Weschke (bweschke) 2005-12-21 13:06:02.000-0600 Please provide a full call trace with debug enabled for a call where you think a file should have been produced and was not. By: vortex_0_o (vortex_0_o) 2005-12-22 06:52:38.000-0600 just so i have a place to note this: - issue 1 - option b zero file size (4% of calls) - issue 2 - testing without option b smaller file than expected (0.3% of calls) (i.e. first few seconds of recording) will try and trace / debug over xmas when call rate is reduced. By: Clod Patry (junky) 2006-01-03 20:38:13.000-0600 Do you have something now? By: Matt O'Gorman (mogorman) 2006-02-01 14:35:57.000-0600 any updates vortex? By: vortex_0_o (vortex_0_o) 2006-02-03 07:22:39.000-0600 Hi difficult to trace atm - I don't have a test box I can use and have reverted back to monitor. What i was doing to get the issues was comparing the expected file size from "billsec" field in the cdr and comparing it to the actual file produced , with a manual spot check. Noticed I am not the only one that had this issue with incomplete recordings though: http://www.voip-info.org/wiki/index.php?comment_page=1&page_id=2755 By: jalsot (jalsot) 2006-02-11 12:13:04.000-0600 Related to ASTERISK-6396457 ? Seems to be... By: BJ Weschke (bweschke) 2006-02-13 21:38:01.000-0600 pls reopen when there is new data available. Thx.