No subject


Fri Sep 2 03:59:05 CDT 2011


{quote}{noformat}
$ext->add($context, $exten, '', new ext_set('MEETME_RECORDINGFILE','${IF($[${LEN(${MIXMON_DIR})}]?${MIXMON_DIR}:${ASTSPOOLDIR}/monitor/)}${YEAR}/${MONTH}/${DAY}/${CALLFILENAME}')); $ext->add($context, $exten, '', new ext_set('MEETME_RECORDINGFORMAT','${MIXMON_FORMAT}'));
{noformat}{quote}

So this is coming in from MEETME_RECORDINGFILE.  We should use {{filename_parse}} in MeetMe to make sure the directory structure gets created.
                
      was (Author: mjordan):
    From Tony:

{quote}
$ext->add($context, $exten, '', new ext_set('MEETME_RECORDINGFILE','${IF($[${LEN(${MIXMON_DIR})}]?${MIXMON_DIR}:${ASTSPOOLDIR}/monitor/)}${YEAR}/${MONTH}/${DAY}/${CALLFILENAME}')); $ext->add($context, $exten, '', new ext_set('MEETME_RECORDINGFORMAT','${MIXMON_FORMAT}'));
{quote}

So this is coming in from MEETME_RECORDINGFILE.  We should use {{filename_parse}} in MeetMe to make sure the directory structure gets created.
                  
> meetme - Error writing file for recording
> -----------------------------------------
>
>                 Key: ASTERISK-19986
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19986
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 1.8.10.1
>         Environment: AsteriskNow 2.0
>            Reporter: Reid Canavan
>            Severity: Minor
>
> Conference recording will error if the directory structure is not already available with error:
> [2012-06-12 12:36:44] WARNING[25297] file.c: Unable to open file /var/spool/asterisk/monitor/2012/06/12/conf-2887-2887-20120612-123642-1339519002.179349.WAV: No such file or directory
> This error is not presented if the directory is available.  Typically this directory is created for call recording ( works fine ).  This was found when the conference started before any calls were recorded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list