| Summary: | ASTERISK-14706: MONITOR_FILENAME fails if directory doesnt exist. | ||
| Reporter: | generalhan (generalhan) | Labels: | |
| Date Opened: | 2009-08-24 13:49:53 | Date Closed: | 2009-08-31 08:55:46 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_mixmonitor |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | when using Set(MONITOR_FILENAME="/foo/bar/filename") to have queue calls monitored/recorded, asterisk cannot complete the mixmonitor/recording if the directory does not exist. This issue really comes into effect when trying to set the directory structure using ^{MEMBERINTERFACE} as a directory in the filename path-- since this is not a vairable that is assigned before the queue call is answered, you cannot simply add a System() command to create this directory. This is an Asterisk-wide issue, not limited to a specific operating system, but for the sake of being complete, my setup is running Asterisk 1.4.26.1 with DADHI Linux 2.2.0.2 on CentOS 5.3 ****** ADDITIONAL INFORMATION ****** maybe with an option/flag to have the directory created if it doesnt exist, or a patch that just uses this logic by default?! | ||
| Comments: | By: Leif Madsen (lmadsen) 2009-08-31 08:55:46 I'm closing this issue as a feature request, because really I wouldn't expect Asterisk to just start creating directories willy-nilly -- that is really an administrator issue. Additionally, there is the STAT() function which you can use to check to see if the directory exists prior to using it. If it doesn't exist, you can easily create it yourself. | ||