[asterisk-bugs] [JIRA] (ASTERISK-22192) [patch] Allow voicemail forwards with ODBC backend when format differs from attachfmt column

[cmaj (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

cmaj updated ASTERISK-22192:
----------------------------

    Description: 
Specifying multiple file formats in voicemail.conf breaks forwarding of previously recorded voicemails stored in ODBC if the attachfmt column is not equal to the filetype of the actual recording.

For example, in voicemail.conf:
format = gsm|wav

In voicemail_users table:
attachfmt = wav

The above breaks because messages are stored in the database in the first file format from the list -- in this case, as gsm files. But when attempting to forward the message to another user, the generated email tries to send a wav file. A sox conversion is required to convert the gsm to wav.

The advantage of storing gsm in the database is that it takes less space, but sending an email wav attachment is easier for end users to playback.

The reason this works during initial voicemail delivery and not during forwarding later on is because all formats specified in the voicemail.conf format line are recorded into the file system as you leave your voicemail message, but only the first format is stored in the database for later retrieval/forwarding.

Originally fixed on Asterisk 1.8.4.4, but patch updated to work with 11.5.0


  was:
Specifying multiple file formats in voicemail.conf breaks forwarding of previously recorded voicemails stored in ODBC if the attachfmt column is not equal to the filetype of the actual recording.

For example, in voicemail.conf:
format = gsm|wav

In voicemail_messages table:
attachfmt = wav

The above breaks because messages are stored in the database in the first file format from the list -- in this case, as gsm files. But when attempting to forward the message to another user, the generated email tries to send a wav file. A sox conversion is required to convert the gsm to wav.

The advantage of storing gsm in the database is that it takes less space, but sending an email wav attachment is easier for end users to playback.

The reason this works during initial voicemail delivery and not during forwarding later on is because all formats specified in the voicemail.conf format line are recorded into the file system as you leave your voicemail message, but only the first format is stored in the database for later retrieval/forwarding.

Originally fixed on Asterisk 1.8.4.4, but patch updated to work with 11.5.0


    
> [patch] Allow voicemail forwards with ODBC backend when format differs from attachfmt column
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22192
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22192
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_voicemail/ODBC
>    Affects Versions: 11.5.0
>         Environment: Debian, PostgreSQL, orig Asterisk version 1.8.4.4
>            Reporter: cmaj
>            Severity: Minor
>         Attachments: patch-11.5.0-app_voicemail-odbc-msg-fwd-file-formats.diff.txt
>
>
> Specifying multiple file formats in voicemail.conf breaks forwarding of previously recorded voicemails stored in ODBC if the attachfmt column is not equal to the filetype of the actual recording.
> For example, in voicemail.conf:
> format = gsm|wav
> In voicemail_users table:
> attachfmt = wav
> The above breaks because messages are stored in the database in the first file format from the list -- in this case, as gsm files. But when attempting to forward the message to another user, the generated email tries to send a wav file. A sox conversion is required to convert the gsm to wav.
> The advantage of storing gsm in the database is that it takes less space, but sending an email wav attachment is easier for end users to playback.
> The reason this works during initial voicemail delivery and not during forwarding later on is because all formats specified in the voicemail.conf format line are recorded into the file system as you leave your voicemail message, but only the first format is stored in the database for later retrieval/forwarding.
> Originally fixed on Asterisk 1.8.4.4, but patch updated to work with 11.5.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira