[asterisk-bugs] [Asterisk 0018391]: Mixmonitor does not parse file path proper if it contain a . (period)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18391 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18391
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-2663 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 295870 
Request Review:              
====================================================================== 
Date Submitted:             2010-11-27 15:48 CST
Last Modified:              2011-03-07 09:13 CST
====================================================================== 
Summary:                    Mixmonitor does not parse file path proper if it
contain a . (period)
Description: 
Using:

/home/pabelanger/digium/asterisk/testing/trunk.295870/testsuite.localhost/tests/mixmonitor/testaudio1

as the filename to record, mixmonitor will assume anything after the
period is the extension.

[Nov 27 16:38:12] WARNING[22696] file.c: No such format
'localhost/tests/mixmonitor/testaudio1'
====================================================================== 

---------------------------------------------------------------------- 
 (0132693) jrose (reporter) - 2011-03-07 09:13
 https://issues.asterisk.org/view.php?id=18391#c132693 
---------------------------------------------------------------------- 
Ok, turns out the problem isn't because looking for the last period from
the end.  The user didn't specify a file type, so the default in that case
is supposed to be raw, but since there are periods in the file name, it
assumes everything after the last period is the extension.

So what I really have to do is make sure the last period takes place after
the last slash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-07 09:13 jrose          Note Added: 0132693                          
======================================================================