Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: august on April 16, 2013, 10:04:55 PM

Title: MLAA problem
Post by: august on April 16, 2013, 10:04:55 PM

I have the following problem:

I have mcd 4.2 and I try to create a MLAA with menu node 2 and 3. I forgot that if I use MLAA I cannot transfer to extension that begin with the same number as the menu node. The problem is that all my extension begin with 3XXX. I delete the mailbox 2 and 3, but I still cannot dial the extension. With the 9999 mailbox, I press 1 to reset the voicemail, but again same problem. There is now only the mailbox 0 and 9999, but again, I cannot dial all the extension that begin with 2 or 3.

I have look with ftp in the VMAIL directory, and I don't see nothing with mailbox 2 or 3. Do you have an idea for me? Maybe a reboot of the controller would fix the problem....

Title: Re: MLAA problem
Post by: johnp on April 17, 2013, 12:03:04 AM

Why do you need MLAA? Could you not just make a mailbox 1 and 2 and handle the task that way?

Title: Re: MLAA problem
Post by: august on April 17, 2013, 06:46:09 AM

When I realise the problem, I decide to used something else then the MLAA, but now even if the MLAA is delete, the embedded vm react the same way as when it was create.

Title: Re: MLAA problem
Post by: Mattmayn on April 17, 2013, 08:41:55 AM

Have you checked the VM options to see if you are restricting transfers to numbers that begin with 2 or 3? Or to see if you are allowing transfers for any number?

I think that would be where to look if I am understanding your problem correctly.

Title: Re: MLAA problem
Post by: ralph on April 17, 2013, 10:09:12 AM

Are you working from the main level or from a AA mailbox?

Ralph

Title: Re: MLAA problem
Post by: august on April 17, 2013, 07:30:47 PM

Working from the main level, and I'm not restricting any number except 9.

I will try a reboot.

Title: Re: MLAA problem
Post by: august on May 02, 2013, 06:24:43 AM

I upgrade to 6.0 and it fix my problem.  Probably just a reboot would have fix it.