Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: kwahodi on April 07, 2013, 07:15:23 PM

Title: Voicemail Prime Directory number
Post by: kwahodi on April 07, 2013, 07:15:23 PM

Hi All,

I've got a CXi-II, 4.1 sp1 I'm working on. I have 16 ports in the "VM port capacity" form. In the "VM Ports" form, I can see port ID 1-16, however, only ports 1-6 have prime directory numbers. I have allocated afew more ports numbers as I want to use them for RAD's. I have also given them the right COS for this. With the VM COS - when I dial the VM directory number directly, I get "out of service". With the RAD COS - when I dial the VM directory number directly, I just get dial tone.

Do I have to reboot the controller after allocating directory numbers to VM ports? Whats else could I be doing wrong?

Appreciate your assistance.

Thanks

Steve

Title: Re: Voicemail Prime Directory number
Post by: matthew on April 07, 2013, 07:23:15 PM

From the top of my head, yes, after you allocate the ports and assign DNs, you need to reboot. You can used the SCHEDULED REBOOT command and have it happen overnight so you don't have to disrupt your customer during business hours.

Title: Re: Voicemail Prime Directory number
Post by: kwahodi on April 07, 2013, 07:32:26 PM

Hi Matthew,

Thanks for your response.


The ports were already allocated but with no DNs. All I did was assign DNs. Does this require a reboot as well?

Thanks.
Steve

Title: Re: Voicemail Prime Directory number
Post by: acejavelin on April 07, 2013, 11:32:57 PM

Yes, a reboot is required. Read the help in programming voice mail, it will explain exactly where you need to reboot. Basically ports are not "allocated" until you assign them a DN, once you do you need to reboot.

Title: Re: Voicemail Prime Directory number
Post by: kwahodi on April 08, 2013, 01:50:09 AM

Ok...thanks. Will do so tonight.

Much appreciated.

Steve

Title: Re: Voicemail Prime Directory number
Post by: kwahodi on April 08, 2013, 06:28:49 PM

Thanks guys....a reboot fixed the problem.

Steve.