Summary:	ASTERISK-19680: Monitor application docs are missing/incorrect
Reporter:	Tim Osman (obeliks)	Labels:
Date Opened:	2012-04-09 13:37:32	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Resources/res_monitor
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	According to http://www.asterisk.org/docs/asterisk/trunk/applications/monitor the syntax is: Monitor([file_format(file_format[:urlbase])[,fname_base[,options]]]) 1. What is urlbase ? 2. Why is file_format repeated twice ? 3. How do I find the list of possible file_formats ? (core show file formats, look in the second column called Name)
Comments:	By: Matt Jordan (mjordan) 2012-04-09 16:25:21.712-0500 The current documentation, pulled from the source code, is located on https://wiki.asterisk.org. https://wiki.asterisk.org/wiki/display/AST/Application_Monitor The documentation on the page you linked is most likely out of date.  That being said, there are still some improvements to the documentation that could be made, based on your questions. 1. urlbase - the base path to store the file in.  Note that this isn't defined on the wiki page either - we'll treat this info request as a bug report to that added. 2. It shouldn't be. 3. Its whatever file formats are currently supported by your installation of Asterisk.  In general, 'module show like format' would show you what audio/video/text/image formats are available. In general, the issue tracker is not used for information requests, even though that issue type exists.  You are typically better off seeking information from the asterisk users mailing list, or the #asterisk IRC channel. By: Tim Osman (obeliks) 2012-04-09 18:21:16.934-0500 1. Based on my testing urlbase is ignored 3. module show like format does not tell you how to specify the format for the Monitor() application. My recipe is better (core show file formats, look in the second column called Name), but it still inconclusive. Note there is a stupid "feature" of the format spec: "WAV" is not the same "wav". The first one produces 13Kbps/GSM 6.10 file, the second 128Kbps/PCM. 4. The syntax specified on the wiki page suggests the function could be called with no arguments, but Monitor() produces an error: "Monitor requires an argument". The minimum set of arguments is Monitor(,). By: Matt Jordan (mjordan) 2012-04-10 09:38:04.685-0500 1. If urlbase is being ignored, please attach a DEBUG log illustrating that. 2. That's because WAV is not the same as wav.  As you noted, WAV is recorded in GSM; wav as 8kHz SLIN.  You'll note that they each have their own format definitions in Asterisk.  If you feel there is a better way of determining file formats, feel free to use it. 3. Noted.  We'll take a look at that as well.