Asterisk
  1. Asterisk
  2. ASTERISK-19994

app_voicemail should be able to decide on storage engines at runtime

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Severity: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.8.12.1
    • Target Release Version/s: None
    • Security Level: None
    • Labels:
      None

      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.

        Activity

        Hide
        Matt Jordan added a comment -

        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.

        Show
        Matt Jordan added a comment - 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.

          People

          • Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development