[asterisk-bugs] [JIRA] Feedback Requested: (ASTERISK-17198) Forwarding voicemail generate error in multi-tenant configuration

[Brent Eagles (JIRA)]

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

Brent Eagles updated ASTERISK-17198:
------------------------------------

    Assignee: SplatNIX
      Status: Waiting for Feedback  (was: Open)

Please provide the additional information:
- Are you using Realtime for configuration? If so, can you provide some details regarding how the database is configured?
- Are you using IMAP storage? Database? If so, can you provide some details as to how this is configured, e.g.:
  - server type
  - non-default ODBC configuration information (other than security credentials of course)
  - if using IMAP, any details about folders, etc.
- Are you using any external password authentication programs, etc.?


> Forwarding voicemail generate error in multi-tenant configuration
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-17198
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17198
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_voicemail
>    Affects Versions: 1.8.8.0
>            Reporter: SplatNIX
>            Assignee: SplatNIX
>
> A client reported that they were unable to forward a voicemail from themselves to a colleague. We tested ourselves and received the following error on the console:
> Couldn't not find mailbox XXX in context default
> The users retrieve their VMs by dialing an extension which calls VoiceMailMail(XXX at VMContext) so why is Asterisk scanning the default context when we have supplied the correct one ?
> As a test I enabled searchcontexts=yes and then the VM could be forwarded; but as we are multi-tenant that had to be backed out as the same extension exists in different contexts.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira