Summary: | ASTERISK-19994: app_voicemail should be able to decide on storage engines at runtime | ||
Reporter: | Jaco Kroon (jkroon) | Labels: | |
Date Opened: | 2012-06-13 18:49:26 | Date Closed: | 2012-06-14 08:12:50 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_voicemail |
Versions: | 1.8.12.1 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Currently whether you use FILE_STORAGE, IMAP_STORAGE or ODBC_STORAGE needs to be selected at compile time. This is not ideal, in my opinion a better solution would be to split the storage of files (potentially even audio clips/sounds files) out into a separate engine and to just link those engines from app_voicemail. That way it even becomes possible to store the voicemail for one user in IMAP, whereas a different user could be stored using FILE storage, or even ODBC. | ||
Comments: | By: Matt Jordan (mjordan) 2012-06-14 08:12:43.703-0500 Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals. [1] http://www.asterisk.org/support/mailing-lists We're well aware of this limitation, and this is something that has been discussed in depth many times. Achieving this would take a substantial effort in app_voicemail (and in other places in the codebase), and - to avoid loss of functionality or regression in behavior - would take a substantial amount of time. That isn't to say we don't think its a good idea, but there's no point in opening an issue about it in JIRA without a lot of work to back it up. |