MWI not working

[JCCDM]

Hi All,

I have an issue since upgrading to the latest version of MiCollab and one of my controllers to the latest version on MiVB. the controller upgraded is the resilient controller, the primary has been held off due to issues that occurred on the first upgrade until they are confident it won't happen again.

Users are reporting that the message wait indicator is either stuck on and there are no messages or it is stuck off even when messages are coming through.

For the users that have the light on, I have supplied the FAC and that turns the light off successfully but it won't come back when a new message is left.

I believe they use mitai messaging for the MWI through Nupoint. is there any way I can reset all the MWI's or anything I should be checking for since the systems have upgraded.

I understand the best next step would be to upgrade the remaining controller and I am pushing for that but am hoping there may be a fix in the meantime.

MiCollab - 8.0.0.103
Upgraded Controller - 8.0 SP2
Old Controller - 7.2

Thanks,
JCCDM

 

[augustD2]

In MiCollab setting, MiVoice Business Network Element Field

HCI Reroute Hunt Group Number for MiTai MWI
Enter the hunt group number for the HCI Reroute Hunt Group. (This hunt group is used to enable MWI lamp on stations with mailboxes via the MiTAI application interface.)

 

[jpruder]

Sounds like an issue with the MiCollab network element that should have Nupoint integrated. As you say there were issues, this might also be one of them.

 

[JCCDM]

Thanks for the notes, I can confirm that the HCI hunt group number is entered correctly into the network element field for the controller that is hosting it.

I believe the issue will be because MiCollab and Nupoint have been upgraded and because the primary controller (which is still 7.2) hasn't been upgraded, I haven't been allowed to start the sharing between the network elements again yet.

Any other bits to check, happy to have a look.

Thanks guys.
JCCDM

 

[kwbMitel]

Use the console on micollab and log in as root
[ul]
[li]At the root prompt, type console[/li]
[li]At the menu prompt type S for System Maintenance, then O for ?Other Options?[/li]
[li]Then L for lights test[/li]
[li]Enter an extension or range of extensions to test the lamps on[/li]
[li]Select 0 (Off), 1 (On), or 2 (Existing)[/li]
[li]At message waiting type leave blank to use type configured in MB[/li]
[/ul]

Once you've figured out your issue, use the 2 option for the entire range of extensions to reset the lamps to their proper values.


**********************************************
What's most important is that you realise ... There is no spoon.

 

[JCCDM]

Thanks kwbMitel, I will log onto the console tonight after hours and do that test. Post results tomorrow.

Cheers,
JCCDM

 

[JCCDM]

I have had multiple users test this for me after logging into the console and making changes and still saying that the lights are not working.

Anything else worth checking, i'm open to ideas.

Cheers,
JCCDM

 

[Wishforall]

Hey,

I had this problem as I was setting up a system in the lab ready to install on a customer site. I spent a lot of time with test voicemails and could not get the problem resolved in the office. I had to the go to site to deply the system. Once a phone was plugged back in the MWI was working. That’s on lamp and on a key. I have since seen this happen over and over again on the recent versions of MiVB I useing NuPoint. So all I have to do is restart the phone.

Hope this helps, please let me know.

Wishforall

 

[JCCDM]

Hi all,

Old system has been upgraded and data sharing has been re-established but the MWI is still not activating. I have run the reconcile wizard on MiCollab and still no luck.

Even the Console options from kwbMitel on only my extension doesn't change.

Any ideas you guys might have?

Cheers,
JCCDM

 

[kwbMitel]

I would set a phone to the same COS as a voicemail port, activate DND and put it in the VM hunt group.

Then I would dial the Message Waiting Activation code and observe the results.

I feel there is something more fundamentally wrong and this might reveal what. e.g. The COS is no longer programmed correctly.

**********************************************
What's most important is that you realise ... There is no spoon.