Experiencing a problem when users attempt to forward a voicemail from within VoiceMailMain(Option 8) I see the console message: Couldn't not find mailbox XXX in context default As why are running in a multi-tenant environment voicemail.conf has been separated into individual contexts. The users retrieve their email by dialing an extension which calls VoiceMailMail(XXX at VMContext) so how do I instruct Asterisk to use that context when forwarding voicemails ? -- Thanks, Phil
Is that user trying to forward to xxx in the same context? On Fri, Dec 17, 2010 at 5:57 AM, --[ UxBoD ]-- <uxbod at splatnix.net> wrote:> Experiencing a problem when users attempt to forward a voicemail from within VoiceMailMain(Option 8) I see the console message: > > Couldn't not find mailbox XXX in context default > > As why are running in a multi-tenant environment voicemail.conf has been separated into individual contexts. ?The users retrieve their email by dialing an extension which calls VoiceMailMail(XXX at VMContext) so how do I instruct Asterisk to use that context when forwarding voicemails ? > -- > Thanks, Phil > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > ? ? ? ? ? ? ? http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > ? http://lists.digium.com/mailman/listinfo/asterisk-users >
----- Original Message -----> --[ UxBoD ]-- wrote: > > ----- Original Message ----- > > > >> > > Yes exactly that indeed. Though Asterisk appears to ignore which > > context the user is in and selects default instead. Beginning to > > think that it is a bug. > > > > I got it figured out. > > In your voicemail.conf, search for the option > > searchcontexts=yes > > And enable it. > > Doug >Sorry for the late reply! While that does allow it to work it is not appropriate in a multi-tenant environment where the same extension could exist in different contexts. Will file a bug for this and the configuration we are using looks correct. -- Thanks, Phil