Summary:	ASTERISK-24028: testsuite: Write a test that verifies the MixMonitor AMI action
Reporter:	Matt Jordan (mjordan)	Labels:
Date Opened:	2014-07-11 12:45:24	Date Closed:	2014-08-14 15:19:15
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Tests/testsuite
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Write tests for the following: h3. Test One - AMI MixMonitor * Spawns a Local channel. Answer the Local channel and begin playback of a sufficiently long file (tt-monkeys, or something similar) * Upon the Local channel being answered, use an AMIEventInstance callback to call into python. Use the AMI [MixMonitor|https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+ManagerAction_MixMonitor] action to start recording the channel. * When the Local channel finishes recording, use the new sound file recording pluggable module to verify that a sound file was recorded (has energy), and that it is of an approximate size that we would expect. h3. Test Two - AMI MixMonitor + StopMixMonitor * Do the same thing as the MixMonitor test, *except*: * After 4 seconds, use the [StopMixMonitor|https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+ManagerAction_StopMixMonitor] AMI action to stop the recording * Verify that a sound file is left, has energy, and is of the correct approximate size h3. Test Three - AMI MixMonitor + MixMonitorMute * Do the same thing as the MixMonitor test, *except*: * Immediately use the [MixMonitorMute|https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+ManagerAction_MixMonitorMute] AMI action to kill all audio going to the mix monitor * Verify that a file exists, but has no energy in it
Comments:	By: Matt Jordan (mjordan) 2014-08-29 14:24:54.106-0500 Note that the start/stop mix monitor tests were on this review: https://reviewboard.asterisk.org/r/3858/ Given some of the race conditions and size check problems that are being seen with the basic test, I've discarded that review until we can dig into those issues further.