MWI issue on 3300

[Curtin_BPW]

Mitel 3300 MXe-III
8.0 SP3 PR2
14.0.3.37

Customer initially had a SX-200 that we swapped out for a freshly configured 3300. MWI light is not working on both the analog guest room phones as well as the 5312/5340e admin phones. Admin IP phones are in Service in Fail Over Resgistration state. Not sure if that would cause the issue. Below are all the settings regarding MWI.

SIP Device Capabilities Number 1
-Allow MWI Notifications without Subscription - Yes

Call Coverage Services
-Voice Mail Number 7900

Hunt Group
7900 - Circular Voicemail (Members 7901-7920)
7950 - Terminal Rad (Members 7917-7918)

VM Ports
7901-7920

VM Port Capacity
20

COS Options for Voicemail ports
-COV/ONS/E&M Voicemail Port - Yes
-ONS VMail-Delay Dial Tone Timer - 5
-Message Waiting - Yes
-Message Waiting - Disable Ringing Lamp Notification - No
-Message Waiting Audible Tone Notification  - No
-Message Waiting Deactivate On Off-Hook - No
-Message Waiting Inquire - Yes
-Message Waiting Ringing Start Time Hour  - Blank
-Message Waiting Ringing Start Time Minute  - Blank 
-Message Waiting Ringing Stop Time Hour  - Blank 
-Message Waiting Ringing Stop Time Minute  - Blank 
-Multiline Set Voice Mail Callback Message Erasure Allowed - No
-ONS CLASS/CLIP: Message Waiting Activate/Deactivate - Yes
-Voice Mail Softkey - Yes

COS Options for Analog Guest Room Phones
-COV/ONS/E&M Voicemail Port - No
-ONS VMail-Delay Dial Tone Timer - 5
-Message Waiting - Yes
-Message Waiting - Disable Ringing Lamp Notification - No
-Message Waiting Audible Tone Notification  - No
-Message Waiting Deactivate On Off-Hook - Yes
-Message Waiting Inquire - Yes
-Message Waiting Ringing Start Time Hour  - Blank
-Message Waiting Ringing Start Time Minute  - Blank 
-Message Waiting Ringing Stop Time Hour  - Blank 
-Message Waiting Ringing Stop Time Minute  - Blank 
-Multiline Set Voice Mail Callback Message Erasure Allowed - No
-ONS CLASS/CLIP: Message Waiting Activate/Deactivate - Yes
-Voice Mail Softkey - No

COS Options for 5300 SIP Phones
-COV/ONS/E&M Voicemail Port - No
-ONS VMail-Delay Dial Tone Timer - 5
-Message Waiting - Yes
-Message Waiting - Disable Ringing Lamp Notification - No
-Message Waiting Audible Tone Notification  - No
-Message Waiting Deactivate On Off-Hook - No
-Message Waiting Inquire - Yes
-Message Waiting Ringing Start Time Hour  - Blank
-Message Waiting Ringing Start Time Minute  - Blank 
-Message Waiting Ringing Stop Time Hour  - Blank 
-Message Waiting Ringing Stop Time Minute  - Blank 
-Multiline Set Voice Mail Callback Message Erasure Allowed - No
-ONS CLASS/CLIP: Message Waiting Activate/Deactivate - Yes
-Voice Mail Softkey - Yes

[ZuluAlpha]

Do you use integrated or NuPoint for voicemail?

[ZuluAlpha]

Do you use integrated or NuPoint for voicemail?

I skimmed over the integrated VM Port info you posted. My bad.

[acejavelin]

Did you build an HCI Reroute Hunt Group?

[Curtin_BPW]

Did you build an HCI Reroute Hunt Group?

I only have the 2x hunt groups listed above.

[BlackSunshine]

Are you using embedded VM or Nupoint? If Nupoint you need HCI Reroute like the other have posted. Are you using SIP devices? You don’t need to set SIP settings unless you are using SIP

[Curtin_BPW]

Are you using embedded VM or Nupoint? If Nupoint you need HCI Reroute like the other have posted. Are you using SIP devices? You don’t need to set SIP settings unless you are using SIP

Yes we are using the embedded voicemail and they are 5312 and 5340e phone sets. What is the easiest way to tell if they are communicating via MiNet or SIP? I was told we always use SIP.

[ZuluAlpha]

Hunt Group
7900 - Circular Voicemail (Members 7901-7920)
7950 - Terminal Rad (Members 7917-7918)

You should remove 7917-7920 from the Circular Voicemail Hunt Group. VM Ports 7917 and 7918 are members of the RAD and VM Hunt group which will cause some issues. Keep 7920 open for administrative access.

[ZuluAlpha]

- Deleted double post -

[acejavelin]

You need to make sure you have unique feature access codes defined for Message Waiting Activate, Deactivate, and Inquire. Dial them manually to test.

You should also have an HCI Reroute Hunt Group, no members, no COS defined, and then Call Reroute Always to main Voicemail Hunt Group.

And as ZuluAlpha said, remove any members of the RAD HG from the main VM HG.

Never use the first or last (two) embedded VM ports for RADs. Msg Wt is sent on the last two VM ports using the FACs you defined above. Pretty sure it sends that the message is from the HCI Reroute Hunt Group.

Probably just a few pieces your missing.

Sent from my Moto G (5) Plus using Tapatalk

[Curtin_BPW]

You should remove 7917-7920 from the Circular Voicemail Hunt Group. VM Ports 7917 and 7918 are members of the RAD and VM Hunt group which will cause some issues. Keep 7920 open for administrative access.

Would I leave 7917-7920 in the "VM Ports" section. I have tried removing 7917 and 7918 from the Hunt Group before and it did not make a difference.

[ZuluAlpha]

You should remove 7917-7920 from the Circular Voicemail Hunt Group. VM Ports 7917 and 7918 are members of the RAD and VM Hunt group which will cause some issues. Keep 7920 open for administrative access.

Would I leave 7917-7920 in the "VM Ports" section. I have tried removing 7917 and 7918 from the Hunt Group before and it did not make a difference.

Yes, leave the VM Ports programmed in that form. Even if it doesn't fix the lights those ports either need be assigned to VM or RAD, not both. If the VM Hunt group sends a call that should go to voicemail to a port set as a RAD you will hear that instead of going to VM.

You may also want to refer to acjavelin's comment about about making sure you have the HCI Reroute Hunt Group set up and you are able to activate the lights via feature access codes. If the FAC's aren't working there is something else at play.

[sarond]

Did you build an HCI Reroute Hunt Group?

I believe HCI Reroute Hunt Group is only required for NuPoint.

I've never programmed it on embedded VM and never had issues.

[acejavelin]

Did you build an HCI Reroute Hunt Group?

I believe HCI Reroute Hunt Group is only required for NuPoint.

I've never programmed it on embedded VM and never had issues.

Force of habit, always build it... Wonder if the Config Wizard builds one?

Still, I think the problem is simple, missing Feature Access Code or something.

Sent from my Moto G (5) Plus using Tapatalk