I have a need to store voicemail in ODBC (MySQL to be specific but that's actually irrelevant). This decision is (and IMHO a crappy design decision) made at compile time of which storage backend to use (although it does on a VERY rudementary check of the code look like a fallback to filesystem might be happening). There are three storage engines available: FILE_STORAGE - the default and trusted one ODBC_STORAGE - the one I'm after IMAP_STORAGE - useful to integrate with mail setups I guess (can link with IMAP mail storage I guess ...) The flag that needs to be modified in menuselect.makeopts is this one: MENUSELECT_OPTS_app_voicemail=FILE_STORAGE A very "clean" solution would be one like the APACHE_MPMS where you can (and must) select exactly one. We can then also need to force USE=odbc if the ODBC vm storage is selected. I've manually set the MENUSELECT_OPTS_app_voicemail=ODBC_STORAGE after manual "ebuild $(equery which asterisk) clean configure", and this worked for me. Some way of doing this via ebuild would be particularly useful. Reproducible: Always
Created attachment 315235 [details, diff] vm_storage_use_expand.diff First variant - this requires VOICEMAIL_STORAGE to be added to the USE_EXPAND list - seemingly unlikely to happen. Patch applies cleanly to 1.8.12.1 version, should apply to 10.X too.
Created attachment 315237 [details, diff] vm_storage_normal_use.diff Tony, If you can get the USE_EXPAND through I'd recommend that, alternatively this patch will also work, but probably not quite a clean in terms of clarity.
Tony, As promised, bug filed against asterisk upstream: https://issues.asterisk.org/jira/browse/ASTERISK-19994
Tony, any progress here? I've got a pending feature that depends on this that I'd like to start pushing out, and my clustered asterisk implementation depends heavily on this.
+*asterisk-1.8.13.0-r1 (22 Jun 2012) + + 22 Jun 2012; Tony Vroon <chainsaw@gentoo.org> +asterisk-1.8.13.0-r1.ebuild: + Voicemail storage backends are now configurable. Work by Jaco Kroon, closes + bug #421037.
