[asterisk-bugs] [Asterisk-GUI 0016562]: Error parsing format= parameter in voicemail.conf

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16562 
====================================================================== 
Reported By:                bsexton
Assigned To:                
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   16562
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk GUI Version:       I did not set the version :( 
Asterisk Version:           1.6.2.0 
JIRA:                        
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-06 17:55 CST
Last Modified:              2010-01-06 17:59 CST
====================================================================== 
Summary:                    Error parsing format= parameter in voicemail.conf
Description: 
There appears to be a possible bug in the parsing of the format= line in
voicemail.conf. It seems to work OK so long as I specifiy one, two, or four
formats but does not work as expected with three formats.

format=wav49|ulaw works as expected with this result:

    -- Recording the message
    -- x=0, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/gYyxx3 format: wav49,
0x2c0c798
    -- x=1, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/gYyxx3 format: ulaw,
0x2c72de8

format=wav49|ulaw|g729 does not work as expected and has the following
result:

    -- Recording the message
    -- x=0, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/SYUeVb format: wav49,
0x2c0c798
    -- x=1, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/SYUeVb format: ulaw,
0x2c72de8

format=wav49|ulaw|g729|g723sf works with the following result:

    -- Recording the message
    -- x=0, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/R7XOJH format: wav49,
0x2c0c798
    -- x=1, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/R7XOJH format: ulaw,
0x2c08a28
    -- x=2, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/R7XOJH format: g729,
0x27aa068
    -- x=3, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/R7XOJH format: g723sf,
0x2c735b8

format=wav49|ulaw|g723sf does not work as expected and has the following
result:

    -- Recording the message
    -- x=0, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/Kkg3XC format: wav49,
0x2c0c798
    -- x=1, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/Kkg3XC format: ulaw,
0x2c72f48
[Jan  6 18:50:51] WARNING[14307]: file.c:1160 ast_writefile: No such
format 'g'
    -- x=2, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/Kkg3XC format: g, (nil)
[Jan  6 18:50:51] WARNING[14307]: app.c:868 __ast_play_and_record: Error
creating writestream
'/var/spool/asterisk/voicemail/default/6000/tmp/Kkg3XC', format 'g'

format=wav49|g729|ulaw|ulaw generates my desired result, but only by
specifying ulaw twice, and has the following result:

    -- Recording the message
    -- x=0, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/2nPMtT format: wav49,
0x2c0c798
    -- x=1, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/2nPMtT format: g729,
0x27aa068
    -- x=2, open writing: 
/var/spool/asterisk/voicemail/default/6000/tmp/2nPMtT format: ulaw,
0x2c556d8

====================================================================== 

---------------------------------------------------------------------- 
 (0116181) bsexton (reporter) - 2010-01-06 17:59
 https://issues.asterisk.org/view.php?id=16562#c116181 
---------------------------------------------------------------------- 
This report is in the wrong place. It should be under Asterisk and not
Asterisk-GUI. I am sorry. Can someone who has the abililty to do so please
move the report to the appropriate area? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-06 17:59 bsexton        Note Added: 0116181                          
======================================================================